This document is in beta. Help us by reporting issues via Github or email.

v0.8.0. See the latest version.

Accessibility Guidelines Summary

This document provided by Kin + Carta Create will help you quickly get up to speed with the Web Content Accessibility Guidelines (WCAG) 2.1, and avoid common accessibility mistakes.

It only covers Level A and Level AA requirements, which are referenced in public sector procurement laws in the UK, US public sector procurement laws, EU public sector procurement laws and public sector procurement laws around the world.

These guidelines apply to both native apps and web-based apps, except for three which are labelled Web only.

This summary is a simplification. If you're not sure how a guideline applies, check the official WCAG 2.1.

1. Easy to perceive

Your website/app must present information in ways that people can recognise and use, no matter how they consume content (for example if they have low vision, or use assistive technologies like screen readers).

1.1. Provide text alternatives for images

1.2. Provide alternatives for audio content, videos and presentations

1.3. Create content that can be presented in different ways

1.4. Make content easy for people to see and hear

2. Easy to operate

Your website/app must be easy to navigate and use, no matter how someone interacts with it.

For example people who do not use a mouse may use their voice, or press the 'Tab' key to move their keyboard's focus to interactive controls.

2.1. Make all functionality work with a keyboard

2.2. Give people enough time to read and use content

2.3. Make sure it won't trigger seizures

2.4. Help people navigate and find content

2.5. Make it work with other input methods beyond keyboard

2.6. Make it work in touchscreens

3. Easy to understand

Your website/app must make it easy for people to understand information and how to complete tasks.

3.1. Make text easy to understand

3.2. Make things appear and behave in consistent, predictable ways

3.3. Help people avoid and correct mistakes

4. Robust and compatible

Your website/app must work with different web browsers and/or assistive technologies.