After reading the selections on evaluating the accessibility of web-based technologies, I chose to evaluate Microsoft Teams as it is an integral part of my classroom and teaching. All assignments and handouts are uploaded to Teams in an effort to increase students’ access to class materials. It is the LMS of choice for many districts around British Columbia. Prior to this, I had never thought about the quality of accessibility of the program. Using the Web Content Accessibility Guidelines and Hyatt’s breakdown of the POUR Principles, I challenged myself to evaluate Teams from both sides, educator (admin) and student.
Perceivable: users must be able to perceive the information being presented
- Teams is primarily a visual medium, but there is a customizable Immersive Reader for individual posts, but not for the pages or tabs. This may be different if the user has a comprehensive Immersive Reader, but for the purpose of this assessment, I have stuck with what Teams has within it. The Immersive Reader does not go beyond what is on the page.
- Each post is presented in its own box which is clearly defined. the perimeter of the boxes changes colour when they are selected, as do the solid boxes. This is especially important when tabbing through the page as opposed to utilizing a mouse.
- Links are differentiated by text colour. The Immersive Reader does not read out web addresses.
- Images do not have captions unless placed there by the poster.
Operable: users must be able to operate the interface
- Update alerts are an aspect of Teams that, and my students, have been trying to customize to our preferences since September. As an educator, I do not receive a notification when an assignment is handed in early or on time, only when it is handed in late. This has caused no shortage of frustration in my classroom. There have also been occasions when the assignment listing is not updated accordingly.
- There is no evidence of a ‘skip navigation’ option.
- All external links, aside from pdf documents, are the same colour, regardless of their format. This has led to confusion when students attempt to find a specific link within the platform.
- Headings are clear and concise.
Understandable: users must be able to understand the information as well as the operation of the user interface
- Immersive Reader settings can be customized to a user’s preference. This includes the speed of the voice, how the written text is presented (breaking it down into parts of speech which are indicated by colour), the text’s size, the screen’s colour, the contrast, and translation settings.
- Navigating the tabs within the Team is not intuitive and some structured instruction is necessary for new users.
Robust: users must be able to access the content as technologies advance
- Teams is accessible on Apple products, as well as mobile devices.
- According to student’s who access Teams on their phones, there is no difference.
Microsoft Teams is a program that I am still learning how to navigate effectively and efficiently. While it does have its good points, I dislike the reliance on text rather than images for navigation. Images could reach more students, especially those with low literacy or different language fluencies. The platform does allow some flexibility in how individuals want to share information, but it is not fully customizable. I also dislike how a student’s access to a Teams resource is gone if they are removed from the group. It makes sense for students graduating, but the ability to access previous assignments and resources throughout the grades is a valuable asset.
References
Introduction to understanding WCAG. Introduction to Understanding WCAG | WAI | W3C. (2022, December 24). Retrieved January 29, 2023, from https://www.w3.org/WAI/WCAG21/Understanding/intro#understanding-the-four-principles-of-accessibility
Hyatt, G. W. (2012, January 3). The POUR principles: The starting point for creating accessible blogs. Blog Accessibility.
http://blogaccessibility.com/the-pour-principles-the-starting-point-for-creating-accessible-blogs/
January 30, 2023 at 12:49 am
Teams has always had an uneven reach of features, particularly when talking about accessiblity or fit for UDL. I know that they are trying to offer adaptations (or skins) for Teams that will make it more suitable for different users and purposes (particularly education) but they don’t seem to be able to move past the majority view of business users.