Slide Three: Accessibility for Ontarians with Disabilities Act (AODA)
Part 2: Web Content Accessibility Guidelines (WCAG)
Common Design Flaws
About 96% of all digital communication errors detected fall into six categories.- Low contrast text 83.6%
- Missing alternative text for images 58.2%
- Empty links 50.1%
- Missing form input labels 45.9%
- Empty buttons 27.5%
- Missing document language 18.6%
- WebAIM: The 2023 report on the accessibility of the top 1,000,000 home pages
WCAG Principles
Information and user interface components must be presentable to users in ways they can perceive. This means that users must be able to perceive the information being presented. User agents, like screen readers, require clearly defined HTML elements within a structured web page. The Banner, Navigation panel, Main section, and Footer are visually perceivable on a standard computer screen, but not necessarily on a screen reader device.
- The intent of WCAG 1.1 Text Alternatives Success Criterion is to make information conveyed by non-text content, such as images, accessible through the use of a text alternative. Text alternatives make information accessible because they can be rendered through any sensory modality; Such as visual, auditory or tactile to match the needs of the user.
- The intent of WCAG 1.2 Time Based Media Success Criterion is to make information conveyed by prerecorded audio-only and prerecorded video-only content available to all users.
- The intent of WCAG 1.3 Adaptable Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes.
- The intent of WCAG 1.4 Distinguishable Success Criterion is to ensure that all users can access information that is conveyed by colour differences.
- Perceivable
User interface components and navigation must be operable. All web page elements must be operable by a keyboard, speech input, and other non-mouse devices. Some of the Java scripts may not be keyboard accessible, and preventing non-mouse users from performing some functions.
- The intent of WCAG 2.1 keyboard Accessible Success Criterion is to ensure that, wherever possible, content can be operated through a keyboard or keyboard interface, so an alternate keyboard can be used.
- The intent of WCAG 2.2 Enough Time Success Criterion is to ensure that users with disabilities are given adequate time to interact with web content whenever possible.
- The intent of WCAG 2.3 Seizures and Physical Reactions Success Criterion is to allow users to access the full content of a site without inducing seizures due to photosensitivity.
- The intent of WCAG 2.4 Navigable Success Criteria is to provide ways to help users navigate, find content, and determine where they are.
- The intent of WCAG 2.5 Input Modalities Success Criterion is to ensure that content can be controlled with a range of pointing devices, abilities, and assistive technologies.
- Operable
Information and the operation of user interface must be understandable. This means that users must be able to understand the information as well as the operation of the user interface.
- The intent of WCAG 3.1 Readable Success Criteria is to define the language of the page. This will ensure that content developers provide information in the web page that user agents need to present text and other linguistic content correctly.
- The intent of WCAG 3.2 success criteria is to make web pages appear and operate in predictable ways.
- The intent of WCAG 3.3 Input Assistance Success Criteria is to ensure that users are aware that an error has occurred and can determine what is wrong.
- Understandable
The intent of this Success Criterion is to ensure that user agents, including assistive technologies, can accurately interpret and parse content.
- Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, like browsers and assistive technologies.
- This means that users must be able to access the content as technologies advance. Meeting this requirement helps maximize compatibility with current and future user agents, like screen readers. In particular, it enables assistive technologies to process the content reliably, and to present or to operate it in different ways.
- This includes non-standard buttons, input fields, and other controls. To deliver a desirable user experience, there must be a separation between web page design and user content. The web page may not render as expected in all browsers, and will not perform as expected in differing screen readers.
- Robustable