Using AI for accessibility and 508 Compliance evaluation

We’re all different

It is very easy to design webpages or applications and only consider how you see the screens. How often do you watch someone else who is new to the screen approach it in the “wrong way,” i.e. not how you intended it to be used when you built it? And that is before we start considering access for people with disabilities. This is why the Web Content Accessibility Standards (WCAG) was created. The quick reference gives guidelines on how to make web pages more accessible. 

It is a good idea to follow these standards, but there is no requirement unless you work for a federal department or agency.

Federally mandated: 508

Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), requires all federal departments and agencies to ensure that their information and communications technology (ICT) is accessible to people with disabilities. The law adopted the Web Content Accessibility Standards (WCAG) as the required standards for compliance.

So it would be great if we could use AI to evaluate webpages and applications.  Whilst AI cannot check every aspect of 508 compliance, it can do a lot for us.

Prompt

Here is the prompt.  Take a screenshot of the application or website page and use this prompt in ChatGPT. You can also use this as a basis for your own prompts. So feel free to copy it and evolve it for your own use cases.

Please evaluate the attached screenshot against the following criteria. The output should be an evaluation of each point.

1. Provide text alternatives for non-text content such as audio files, images, and videos.

2. Provide transcripts for audio-only content, such as podcasts. Video-only content should have either a descriptive transcript or audio description.

3. Ensure a high contrast between text sections and their backgrounds. Ensure proper contrast between text (or images of text) and its background, with a contrast ratio of at least 4.5:1. When using bold or large text (18pt or larger), a 3:1 ratio is sufficient. Contrast restrictions do not apply to logos and brand names. Define a page’s language.

4. Ensure all website functionality is operable via the keyboard.

5. When visitors are met with time limitations within your website, ensure the time limit can be adjusted.

6. Minimize distractions and allow website visitors to turn off or postpone interruptions. People should also be able to postpone or suppress interruptions, updates, and alerts on your website, except in an emergency.

7. Ensure your website has no flashing content that can induce seizures. Web pages should not contain anything that flashes more than three times in one second. Ensure that any single-character key shortcuts are adjustable.

8. Ensure that if a website visitor commits an error, the error is identified and described in text, and announced by screen readers.

9. Ensure that labels and instructions are descriptive and clear for all website visitors. Elements such as buttons, search boxes, and any other interactive elements should be clearly labeled.

10. Ensure that your website has a clear and concise heading structure. Headings should be clear, concise, and organized hierarchically. Ensure that content placement and functionality are predictable.

11. Ensure page titles are clear and helpful. Be sure that website visitors can easily find content and determine where they are on a given web page.

12. Ensure that functionality requiring gestures can be performed by website visitors with limited mobility. Ensure that all links have text that accurately conveys the purpose of the link. When an image is the only content of a link, the alt text for the image is sufficient to describe its purpose.

13. Ensure that electronic documents are accessible and can be read by assistive technologies.

Final word

AI can help us understand where we need to improve the experience for people with disabilities. This is yet another example of a simple “checklist style” prompt, doing a great job of consistency checking.