Name: Bertie Lou
Choose edit to go back and change your answers or continue submit your entries.
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
For example: The below above would be read by a screen reader as "An adorable kitten climbing on a pile of logs"
Images that are purely decorative and may disrupt the readability of the content or that reiterate content already displayed as text should contain minor alt text.Go to the Text Alternatives Section of the WAI Checklist for more in depth coverage
This is important only if the information in the media is available only in said media and not a video/audio repetition of information already provided in the content of the site via text.
It will be important to provide a description for the above media because the information it provides is not located anywhere else on the page. This can be done by providing a transcript of an audio only presentation or linking to textual information that provides comparable information (e.g., for a traffic Webcam, a municipality could provide a link to the text traffic report.)Go to the Time-based Media Section of the WAI Checklist for more in depth coverage of captioning and audio descriptions.
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Make it easier for users to see and hear content including separating foreground from background
Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
This is not ok**EVER. At any size.
If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A). If this were not already an accessibility requirement I would add it in. Seriously.
Make all functionality available from a keyboard.
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus must be able to be moved away from that component using only a keyboard interface. If it requires more than unmodified arrow or tab keys or other standard exit methods to navigate away from the element, the user must be advised of the method for moving focus away.
Provide users enough time to read and use content.
A user must be able to adjust or disable a time limit set by the content of the page. This applies to any process that happens after a set time without user initiation (such as auto updating content, or changing a slide in a carousel).Read about exceptions and further examples on the W3C site.
Anything that auto-updates, auto-scrolls, or moves must have a mechanism to pause, stop or completely hide it
The above carousel should have a way to pause, stop, or hide. The slides go by much too quickly to be read. This is not accessible. It also has no fallback for browsers that do not support CSS3 transitions. This is also not accessible. Please see the section on compatibility to learn more about ensuring accessibility through proper coding techniques.Skip to the Compatible Section of this page to learn more.
Do not design content in a way that is known to cause seizures
Web pages do not contain anything that flashes more than three times in any one second period. (Level A)
Obviously it's not a good idea to show a wrong example of this one. Just be careful about animations and things that might flash in some way.
Make text content readable and understandable.
Make Web pages appear and operate in predictable ways.
When any component receives focus, it does not initiate a change of context.
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. This Success Criterion helps users with disabilities by making interactive content more predictable. Unexpected changes of context can be so disorienting for users with visual disabilities or cognitive limitations that they are unable to use the content. Individuals who are unable to detect changes of context are less likely to become disoriented while navigating a site.
Help users avoid and correct mistakes
Maximize compatibility with current and future user agents, including assistive technologies.
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)
Always use valid and semantic markup as much as possible and validate pages to ensure correct markup has been used.W3C Markup Validation Service
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
If using script or code to re-purpose a standard user interface component in a markup language:
Exposing the names and roles, allowing user-settable properties to be directly set, and providing notification of changes using one of the following techniques:
ARIA16: Using aria-labelledby to provide a name for user interface controls (ARIA)