Body
- User agents are web browsers, media players, and assistive technologies that the users use to interact with the site.
- Web browsers, media players, assistive technologies, and other user agents should support accessibility features.
- If one part or “component” of the site is inaccessible, other components can compensate for further accessibility.
- This takes much more effort and is still less accessible.
- Text alternatives (alt text) are required for non-text content like images, buttons, charts, and audio and video files.
- Audio and video files require captions or text transcripts. If visuals are important in a video then audio descriptions are required to describe visual details in videos.
- You could also include sign language interpretations of videos.
- Text transcripts must contain the correct order of information from both the audio and the visuals of videos.
- Users must be able to pause and adjust the volume of audio on a website.
- Background audio is low or can be turned off to avoid distraction.
- Content must be distinguishable, meaning it's easier to see or hear.
- Color cannot be the only way of conveying information, differentiating content, or identifying content.
- Foreground, background, text, and button colors must have proper contrast. This can by checked using the WebAIM Color Contrast Analyzer.
- Information must not be lost if a user resizes the text up to 400% or changes text spacing.
- Text must reflow into smaller windows (viewports) when text size is increased
- Be wary of using content that flashes and warn users before flashing content is presented.
- This is due to certain rates or patterns of flashes causing seizures or other physical reactions.
- Provide ways to switch off animations or provide alternatives.
- All functionality that is available with a mouse must also be able to be done with a keyboard.
- Web browsers, authorizing tools, and other tools must provide keyboard support.
- This must also work for users using alternative keyboards or using voice recognition.
- Keyboard focus (where the keyboard is navigating) is visible and follows a meaningful and logical sequence.
- Keyboard focus should not get trapped in any part of the content.
- Users should be able to easily orient themselves and navigate the webpage.
- Pages must have clear titles that are different from any other page titles on the site.
- There must be more than one way for users to find relevant pages on the site.
- Users must be able to know what page they are currently on.
- Pages must be organized and use descriptive headings.
- Headings, lists, tables, input fields, and content structures must be marked correctly.
- Give users enough time to read content by stopping, extending, or adjusting time limits and re-authenticating when a session expires without losing data.
- Buttons, links, and other active components are large enough to be easily activated through touch.
- Components should be designed to avoid accidental activation and provide the ability to undo actions.
- Labels presented to users match object names in the code to support voice activation.
- Functionality should not only take keyboard and voice activation into account but also take use on mobile devices and laptops / desktops into consideration.
- Text must be easy to read and understand to a broad audience.
- Provide definitions for unusual words, phrases, idioms, or abbreviations.
- Use clear and simple language when possible or provide simple explanations for more complicated concepts.
- Content must appear and operate in predicable and logical ways.
- Inconsistent appearance or behavior of interfaces can be distracting, confusing, and disorienting.
- Navigation mechanisms should be repeated on each page and have the same navigation labels every time.
Interactable parts of a webpage should have descriptive instructions, error messages, and correction suggestions as well as the ability to review, edit, and reverse submissions if needed.