Web Content Accessibility Guidelines: Best Practices
The WCAG are standards designed to make web content accessible to people with disabilities. We aim to ensure our websites are perceivable, operable, and understandable, for all users, including those with visual, auditory, physical, and cognitive impairments. Here are the full set of guidelines for reference.
WCAG Principles | 13 Guidelines |
---|---|
Perceivable | 1.1 Text alternative 1.2 Time-based media 1.3 Adaptable 1.4 Distinguishable |
Operable | 2.1 Keyboard accessible 2.2 Enough time 2.3 Seizures and Physical Reactions 2.4 Navigable 2.5 Input Modalities |
Understandable | 3.1 Readable 3.2 Predictable 3.3 Input Assistant |
Robust | 4.1 Compatible |
Different levels of conformance
The WCAG guidelines are organized into three levels of conformance: A, AA, and AAA. These levels represent different degrees of accessibility.
Level A (Must do)
The bare minimum of accessibility.Level AA (Should do)
Everything in A plus a few additional requirements.Level AAA (Can do)
Everything in A and AA plus a few additional requirements.
Guidelines and Success Criteria Checklist
1. Text
1.4.1 Check Contrast Ratio (AA)
https://webaim.org/resources/contrastchecker/
1.4.4 Text Size (AA)
em
or %
).2. Color
1.3.2 Color Independence (A)
1.4.11 Non-text Contrast (AA)
3. Images, Videos and other media
1.1.1 Text Alternatives for Non-Text Content (A)
(Text alternatives must convey the same information and purpose as the non-text content.)
1.2 Synchronized Alternative for Multimedia (A)
1.4.2 Background noise (AA)
4. Navigation
2.1.1 Keyboard Navigation (A)
1.3.3 Sequence of Information (A)
3.2.3 Multiple ways of navigation (AA)
For example, a homepage with links to all pages, search functionality, site map, table of contents, Primary and secondary navigation menus, Repetition of important links in footer etc.
3.2.3 Predictable Navigation (AA)
For eg, ensuring consistent placement of elements like buttons, navigation bar, search bar, help options, and contact options across all web pages.
5. Input Form
Mistake correction
1.3.5 Identify Input Purpose (AA)
Code example, <input type=”text” autocomplete=”street-address”>
6. Interactive components and Animation
2.3.1 Seizures and Physical Response (A)
2.5.5 Target size (AA)
1.4.11 Non-text Contrast (AA)
7. Web pages
1.3.4 Orientation (AA)
Structure and Semantics (AA)
code example <main>The main content of the page goes here.</main>
\
1.4.10 Responsive Design (AA)
Accessibility Feedback (AA)
8. Useful Resources and tools
IBM Equal Access toolkit- Add on to the inspect section, gives a comprehensive audit, and possible code changes.
Stark Accessibility Checker- Useful for checking how the website will look to people with different visual impairments.