Understand and Apply WCAG Standards
The Web Content Accessibility Guidelines (WCAG) are the recognized international standard for digital accessibility. Federal and state law use these criteria to determine if our digital content is accessible.
You can create successful digital experiences by understanding the four foundational WCAG principles:
- Perceivable
- Operable
- Understandable
- Robust
Thirteen specific guidelines support these principles to help you revise and create accessible content.
Perceivable Principle
Make Your Content Perceivable
Users must be able to perceive information and interface components, regardless of sensory impairments.
- Provide Text Alternatives: You must include text alternatives for all non-text content, such as images and audio files. If an image acts as instructions, add alternative text with those instructions to the file or place it adjacent to the image. If your system uses sound to indicate a correct answer, integrate a visual cue, such as a checkbox.
- Include Alternatives for Time-Based Media: You must provide alternative presentations for time-based media, such as video and audio. Add captions, audio descriptions, or transcripts for prerecorded media. For live media, offer real-time captions or hire an ASL interpreter.
- Create Adaptable Content: Present your content so that it can be transformed in different ways without losing meaning or structure. Create accessible tables using proper semantic HTML instead of uploading a screenshot of a data table. Avoid using color as the sole visual cue to convey information; add patterns to graphs so users with colorblindness can distinguish the data.
- Keep Elements Distinguishable: Make it easy for users to separate foreground content from the background. Standard text needs a minimum color contrast ratio of 4.5:1, while large text requires a 3:1 ratio. Ensure users can resize all text up to 200 percent without losing functionality. We recommend using a standard font size of at least 13.5 point (18 px).
Operable Principle
Keep Your Website Operable
Present your website's navigation and user interface components so users can operate them easily using a variety of assistive technologies.
- Ensure Keyboard Accessibility: Build your website so users can navigate menus, click buttons, and fill out forms using only a keyboard. If a pop-up window appears, ensure users can exit it using keyboard commands.
- Give Users Enough Time: Provide users with enough time to read and use your content. If a page times out, display a pop-up warning at least 20 seconds before the timeout and allow the user to easily extend the timeout limit. Let users pause, stop, or hide moving content, such as image carousels.
- Prevent Seizures and Physical Reactions: Never present digital content in ways that trigger seizures or physical reactions. Do not use media that flashes more than three times in one second, and avoid any transitions that contain a saturated red flash. Ensure users can easily disable motion-animated elements.
- Make Navigation Easy: Help users find content and determine their location on your site. Use clear, descriptive headings instead of vague labels to help screen reader users find specific information. Include a breadcrumb structure, so users have a clear pathway to access prior content.
- Support Various Input Modalities: Ensure users can operate your website using a mouse, touch, keyboard, and speech inputs. Make buttons at least 24 by 24 pixels, though 44 by 44 pixels is ideal. Add space between buttons and provide point-and-click alternatives for drag-and-drop actions to help users with fine motor challenges.
Understandable Principle
Write Understandable Content
Users should be able to easily understand your information and how to use your interface.
- Keep It Readable: Avoid unnecessary jargon, idioms, and advanced vocabulary. Aim for a 7th-8th reading level for general text. Define acronyms at first use, or include a glossary so beginners can understand the material.
- Build Predictable Pages: Ensure your webpages operate consistently. Keep your navigation menus and search boxes in the exact same location across all pages. Never redirect a webpage simply because a user moved their focus to a new element.
- Provide Input Assistance: Help your users avoid and correct mistakes. Provide detailed instructions in form fields upfront, such as explicitly stating password requirements before the user clicks submit.
Robust Principle
Build Robust Digital Space
You must ensure your content is robust enough to be interpreted by current and future user agents, including assistive technologies.
- Keep Code Compatible: Default HTML elements are typically already accessible, so avoid making changes whenever possible. Developers can use ARIA (Accessible Rich Internet Applications) attributes for complex interfaces. Assign a name, role, and value to all interactive elements so screen readers can accurately convey meaning. Include status messages in your code to alert visually impaired users when they successfully submit an application or form.