Meeting the ADA Title II Digital Accessibility Requirements

Web accessibility audits involve the use of both automated and manual testing tools. These tools evaluate the level to which your website meets the updated ADA Title II standards (i.e., WCAG 2.1), ensuring access for all users, not just those with disabilities. They also improve your website's search engine optimization (SEO) and make it easier for individuals to access your website using a mobile device.

The automated process includes the use of testing tools that "crawl" your website looking for accessibility issues (e.g., missing alt text, poor hyperlink text, color contrast issues, etc.). These web governance solutions typically provide an initial assessment of your website, highlight any accessibility issues, and pinpoints the location of those issues. Automated scans, however, will only catch issues with your HTML, CSS, and/or javascript code. These issues, while important, are only a part of the overall picture. These tools are UNABLE to test against issues that are more subjective (e.g., the quality of an image's alternative text description). For this reason, it is very important to include manual testing as a part of your auditing plan.

Manual testing is completed using assistive technologies like screen reading applications, screen enlarging software, voice recognition software, and other alternative keyboard and mouse options. Unlike automated tools that scan several pages at a time, manual reviews are conducted one page at a time. This process can more accurately identify how accessibility issues effect the usability of your website (e.g., quality of video captions).

DubBot is a web-governance solution that can assist with determining how accessible your public-facing websites are. Additionally, it enables units to monitor their websites for broken links, spelling errors, and readability, enhancing engagement from members of the George Mason community.

See below for information on how to use this resource:

• To have your website(s) added to DubBot, Schedule a web accessibility consultation. In addition to adding your website(s) to the platform and granting user access, ATI staff will provide an overview of the DubBot dashboard and guidance on how to get started auditing and correcting accessibility issues on your website(s).
• Additional resources below:
  • Beginner's Guide to Using DubBot opens a new window
  • Quick Wins Panel opens a new window
  • Sorting Accessibility Issues opens a new window

The ATI recommends the following resources for manually identifying issues on your website(s):

• WAVE by WebAIM - WAVE opens a new window is a tool for web developers to help evaluate the accessibility of website within any browser. Simply type in the web address after opening the WAVE web page and press the Enter key. WAVE will provide a summary of the results as well as display findings directly on the webpage through easy-to-read colored icons. WAVE also provides information on the standards tested and how to fix the errors.

• ANDI - Like WAVE, ANDI opens a new window is a browser-based tool that helps end users manually evaluate the accessibility of their websites. ANDI breaks up the accessibility testing process into manageable subtasks, allowing you to focus on specific issues (e.g., color contrast, alternative text descriptions, reading order, etc.).

Check out the resources below for more information on using the WAVE and ANDI tools:

• VIDEO: Introduction to WAVE (11:20) opens a new window
• ANDI Video Training Series (section508.gov) opens a new window

For testing color contrast, the ATI recommends units use either TPGI's free Colour Contrast Analyser (CCA) or WebAIM's Contrast Checker. Both tools will ensure email communications, documents, social media, etc. meet the latest ADA Title II standards governing contrast between foreground text and background colors (i.e., WCAG Success Criterion 1.4.3 opens a new window). Furthermore, they will assist you with ensuring your digital content is optimized for individuals with color-blindness and/or low vision. See below for a video demonstration of both tools on YouTube opens a new window (6:44):

See below for information on how to use these resources:

• WebAIM Contrast Checker opens a new window
• TPGI Colour Contrast Analyser opens a new window
• Understanding WCAG 2 Contrast and Color Accessibility (WebAIM) opens a new window

See below for some of the most common accessibility issues found on web pages:

• Missing alternative text descriptions (or alt text)
• Missing navigational mechanisms (i.e., skip navigation links, headings, visual focus indicators, etc.)
• Missing table headers
• Poor hyperlink text
• Improperly labeled form fields
• Color contrast issues

For more information on these issues and how to fix them on your website, visit the ATI's ICT Accessibility Standards opens a new window.

The following resources will assist you with identifying the documents hosted on your course site:

• Panorama (RECOMMENDED): Panorama uses accessibility score icons to indicate if your document meets accessibility standards. Visit Alternative Format Options in Panorama on the ATI's Panorama (by Yuja) opens a new window page to learn more.
• Microsoft 365: Use the Accessibility Checker in Microsoft 365 to identify any accessibility issues in your Word and/or PowerPoint documents. This tool will not provide an accessibility "score"; it will, however, highlight all of the issues in your document(s).
• Acrobat Pro DC: Use the Acrobat Pro DC Accessibility Checker to identify any accessibility issues in your PDF documents. Similar to Microsoft 365, this tool will highlight all of the issues in your document(s). It will not provide an accessibility "score".

The following resources and frequently asked questions will provide guidance on some of the most common accessibility issues in documents:

• Missing alternative text descriptions (or alt text) - Alt text provides textual descriptions for images, multimedia, and other types of non-text content. Screen reading applications announce this information to blind and/or low vision users who are unable to see the images or other non-text content in a document. Without this, screen reader users would be unable to interpret visual content. To learn more about alt text, visit What is the purpose of alternative text (section508.gov) opens a new window.
• Documents without structure (i.e., headings) - Using structured headings in Word and PDF documents improves navigation for screen reader users and organizes content for easier understanding, supporting individuals with cognitive and/or visual impairments. Proper headings also help readers quickly find information and makes documents more usable on various platforms. They also enhance searchability and allow for better document reflow, making the content accessible to a wider audience. To learn more about use a proper heading structure in your documents, visit Using Headings in Word Documents (WebAIM) opens a new window.
• Missing table headers (i.e., headings) - It is important to ensure column and row headers are properly identified in data tables. This aids screen reader users with making associations between the content in data cells and the column and row headers. To learn more about making tables accessible in your Word documents, visit Create accessible tables (Microsoft) opens a new window.
• Poor hyperlink text - Hyperlink text provides information on where the user will be taken if they open the link. When hyperlinks are not labeled appropriately, they can be an accessibility barrier for individuals with disabilities, especially those using screen readers. To learn more about creating accessible hyperlinks, visit Create accessible hyperlinks (harvard.edu) opens a new window.
• Poor color contrast - Good color contrast ensures your digital content is optimized for individuals with disabilities, especially those who are color-blind and/or have low vision. To learn more about creating good color contrast, visit Understanding WCAG 2 Color and Contrast Accessibility (WebAIM) opens a new window.
• Using color alone to convey important information - Avoid using color alone to convey important information or prompt a response. This could negatively impact access for individuals with visual impairments (i.e., low vision, colorblindness). To learn more about this topic, visit Use of Color (section508.gov) opens a new window.

Determining how accessible or inaccessible your audio and/or video content may be is a manual process. Consider these factors when determining if your content is compliant with the updated ADA Title II accessibility standards:

• Audio-only content (e.g., podcasts) - Audio-only content like podcasts or mp3 files should include an accurate text transcripts.
• Video-only content (e.g., videos with no dialogue) - Video-only content with no dialogue should include either an audio track or a text description providing context for users who cannot see the video.
• Captions - All videos with dialogue should include accurate, synchronized captions. Text transcripts are not required but strongly recommended.
• Audio Descriptions - All videos with dialogue should include audio descriptions. Audio descriptions provide context for key visual elements in media (i.e., film, course video, theater production, etc.). Please note that it may not be necessary to provide audio descriptions for every video. There are other strategies that could work toward ensuring visual content is accurately described (e.g., instructors can include description while recording their lectures). Please consult with the ATI Office if you have questions about your specific situation.
  
  To learn more about audio descriptions, check out the video below:
• Keyboard Navigable - All audio and video content should be hosted on platforms that can be accessed via keyboard and mouse. Additionally, all form elements (i.e., buttons, labels, etc.) should be accessible to assistive technologies (i.e., screen readers) and easily identified when read aloud.

Right now, there are no specific recommendations for audio-only content platforms. If units have questions or concerns about the accessibility of their audio-only content, please consult the ATI Office.

As for video platforms, the three most commonly used at Mason are Kaltura, YouTube, and Vimeo. At the present date, all these platforms are accessible from the standpoint that they support closed captions, transcripts, separate tracks for audio description, and they can be navigated by individuals using assistive technologies (i.e., keyboard-only access, screen readers). See below for more resources:

• Kaltura Player Accessibility opens a new window
• YouTube Accessibility opens a new window
• Video Accessibility at Vimeo opens a new window
• ITS Services (Kaltura) opens a new window

The table below provides GMU faculty/staff with clear guidance on when to use automatic captions, professional-level captions, and/or audio descriptions for their videos:

ADA Title II Subpart H §35.200 opens a new window defines the following requirements for web content and mobile apps:

1. Web content that a public entity provides or makes available, directly or through contractual, licensing, or other arrangements; and
2. Mobile apps that a public entity provides or makes available, directly or through contractual, licensing, or other arrangements.

There are also multiple references in the updated ADA Title II guidelines stating that while there are exceptions (e.g., unconventional electronic documents, social media posts, etc.) to the new guidelines, public entities still need to ensure their digital platforms are fully compliant with the WCAG 2.1 AA standards.

Thinking more broadly, this covers many of the digital applications that we purchase, acquire, and/or develop at Mason. This includes, but is not limited to, the following:

• Content management systems (i.e., Drupal, WordPress),
• Learning management systems (i.e., Canvas),
• Apps used in Mason classrooms (i.e., apps used for grading, polling, discussions, etc.),
• Mason websites,
• Mason mobile apps,
• Library databases,
• Productivity tools (i.e., Microsoft 365),
• Chat applications (i.e., MS Teams)
• Video hosting platforms (i.e., Kaltura),
• Web conferencing solutions (i.e., MS Teams, Zoom)
• and so on...

The Architectural Standards Review Board (ASRB) opens a new window is responsible for reviewing, verifying compliance, and providing recommendations for new and upgrade software and hardware procurement projects. The purpose of the ASRB process is to communicate business needs to ITS and other stakeholders. The university and ITS may already have supported software or hardware available that may be used. Additionally, the university and ITS may have existing contacts with various vendors that can expedite the procurement process.

How is the ASRB involved in this effort?

The ASRB keeps an updated list of the apps and tools that have undergone reviews. While this report is not publicly available yet, it can be accessed by those on the ASRB, members of the ATI team, and other select individuals within ITS and the academic units. To determine if your supplemental apps have already been reviewed by the ASRB, email the ATI Office, [email protected].

The Supplemental Application Decision Tree was created to assist you with making determining which of your supplemental applications should be reviewed by the ASRB. See below for guidance:

On January 15^th, Judith Risch (Grand River Solutions), in partnership with Mason's Assistive Technology Initiative, led a kickoff session on the upcoming ADA Title II updates and practical steps that higher education institutions like George Mason should be taking to comply with the new standards. The ATI introduced their Digital Content Accessibility Action Plan and highlighted the tools and resources currently in place to support faculty and staff with any digital accessibility-related needs.

To view the videos and access copies of the session presentations, use the links below:

• Session 1: ADA Title II Updates with Judith Risch [PDF] opens a new window, Keynote Video opens a new window
• Session 2: ATI's Digital Content Accessibility Action Plan [PPTX] opens a new window, DCAAP Kickoff Video (Jan 2025) opens a new window

The following quick guides highlight best practices for creating accessible digital resources (i.e., websites, documents, videos, etc.):

• Top Tips for Creating Accessible Instructional Content  |  Download PDF
• Top Tips for Creating Accessible Websites  |  Download PDF
• NCVLC Accessible Math Guide v8.1 - Fall 2022  |  This resource was developed by the North Carolina Virtual Learning Community and highlights techniques, workflows, and tools to support the development of accessible math content. Download Word File

The ATI offers self-paced, web-based digital accessibility training courses to assist members of the Mason community with learning how to create accessible documents and websites. To learn more about these offerings, visit the Document Accessibility Fundamentals (DAF) course opens a new window and Trusted Tester for Web Fundamentals (TTW) course opens a new window.

If you are looking for more general training on digital accessibility, creating accessible documents/websites, adding captions to your videos, or just on the resources available to assist with remediating inaccessible content, Schedule a consultation. ATI staff will work with you to design a session that works for your unit.