Simplified and easy to use guide on using WCAG-Web Content Accessibility Guidelines in your day-to-day projects.
Each article has design guidance for Web, IOS and Android along with links to resources.
WCAG Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Guideline 1.1: Text Alternatives
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.
- 1.1.1 Non-Text Content (A)
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for controls and input, time-based media, test, sensory experience, CAPTCHA and decoration.
Guideline 1.2: Time-Based Media
Provide alternatives for time-based media. Time-based media includes various forms of media like video, audio, slides, computer simulations, or any other media that has duration as a property and is presented over time.
- 1.2.1 Audio-Only and Video-Only (A)
For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as an alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content (Prerecorded Audio-only) or either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content (Prerecorded Video-only).
- 1.2.2 Captions (Prerecorded) (A)
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labelled as such.
- 1.2.3 Audio Description or Media Alternative (A)
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labelled as such.
- 1.2.4 Captions (Live) (AA)
Captions are provided for all live audio content in synchronized media.
- 1.2.5 Audio Description (Pre-Recorded) (AA)
Audio description is provided for all prerecorded video content in synchronized media.
Guideline 1.3: Adaptable
Create content that can be presented in different ways without losing information or structure (e.g., a simpler layout).
- 1.3.1 Info and Relationships (A)
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- 1.3.2 Meaningful Sequence (A)
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
- 1.3.3 Sensory Characteristics (A)
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
- 1.3.4 Orientation (AA)
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
- 1.3.5 Identify Input Purpose (AA)
The purpose of each input field collecting information about the user can be programmatically determined when – the input field serves a purpose identified in the Input Purposes for User Interface Components section and when the content is implemented using technologies with support for identifying the expected meaning for form input data.
Guideline 1.4: Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
- 1.4.1 Use of Color (A)
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
- 1.4.2 Audio Control (A)
If any audio on a web page plays automatically for more than three (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.
- 1.4.3 Contrast Minimum (AA)
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following – 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) and Logotypes (Text that is part of a logo or brand name has no contrast requirement).
- 1.4.4 Resize Text (AA)
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
- 1.4.5 Images of Text (AA)
If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following- The image of text can be visually customized to the user’s requirements (Customizable) and a particular presentation of text is essential to the information being conveyed (Essential).
- 1.4.10 Reflow (AA)
Content can be presented without loss of information or functionality and without requiring scrolling in two dimensions for the following – Vertical scrolling content at a width equivalent to 320 CSS pixels and horizontal scrolling content at a height equivalent to 256 CSS pixels. The above applies except for parts of the content that require two-dimensional layout for usage or meaning.
- 1.4.11 Non-Text Contrast (AA)
The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent colour(s)-
- User Interface Components (Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author) and Graphical Objects (Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed).
- 1.4.12 Text Spacing (AA)
In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property- Line height (line spacing) to at least 1.5 times the font size ; spacing following paragraphs to at least 2 times the font size ; letter spacing (tracking) to at least 0.12 times the font size and word spacing to at least 0.16 times the font size.
- 1.4.13 Content on Hover or Focus (AA)
Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
- Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
- Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
WCAG Principle 2: Operable
User interface components and navigation must be operable.
Guideline 2.1: Keyboard Accessible
User interface components and navigation must be operable.
- 2.1.1 Keyboard (A)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.
- 2.1.2 No keyboard Trap (A)
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can 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, the user is advised of the method for moving focus away.
- 2.1.4 Character Key Shortcuts (A)
If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case), punctuation, number, or symbol characters, then at least one of the following is true:
- Turn off: A mechanism is available to turn the shortcut off.
- Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g., Ctrl, Alt, etc).
- Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
Guideline 2.2 Enough Time
Provide users enough time to read and use content.
- 2.2.1 Timing Adjustable (A)
For each time limit that is set by the content, the user should be allowed to turn off the time limit or adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting or the user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times. The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or the time limit is essential and extending it would invalidate the activity or the time limit is longer than 20 hours.
- 2.2.2 Pause, Stop, Hide (A)
For any moving, blinking, or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there should be a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential Similarly, for any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there should be a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Guideline 2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
- 2.3.1 Three Flashes or Below (A)
Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Guideline 2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
- 2.4.1 Bypass Blocks (A)
A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
- 2.4.2 Page Titled (A)
Web pages have titles that describe topic or purpose.
- 2.4.3 Focus Order (A)
If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
- 2.4.4 Link Purpose (In Context) (A)
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
- 2.4.5 Multiple Ways (AA)
More than one way is available to locate a web page within a set of web pages, except where the web page is the result of, or a step in, a process.
- 2.4.6 Headings and Labels (AA)
Headings and labels describe topic or purpose.
- 2.4.7 Focus Visible (AA)
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Guideline 2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
- 2.5.1 Pointer Gestures (A)
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
- 2.5.2 Pointer Cancellation (A)
For functionality that can be operated using a single pointer, the down-event of the pointer is not used to execute any part of the function; completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; the up-event reverses any outcome of the preceding down-event and completing the function on the down-event is essential.
- 2.5.3 Label in Name (A)
For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
- 2.5.4 Motion Actuation (A)
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when the motion is used to operate functionality through an accessibility supported interface (Supported Interface) and the motion is essential for the function and doing so would invalidate the activity (Essential).
WCAG Principle 3: Understandable
Information and the operation of user interface must be understandable.
Guideline 3.1 : Readable
Make text content readable and understandable.
- 3.1.1 Language of Page (A)
The default human language of each web page can be programmatically determined.
- 3.1.2 Language of Parts (AA)
The human language of each passage or phrase in the content can be programmatically determined, except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
Guideline 3.2 Predictable
Make web pages appear and operate in predictable ways.
- 3.2.1 On Focus (A)
When any user interface component receives focus, it does not initiate a change of context.
- 3.2.2 On Input (A)
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component.
- 3.2.3 Consistent Navigation (AA)
Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
- 3.2.4 Consistent Identification (AA)
Components that have the same functionality within a set of web pages are identified consistently.
Guideline 3.3: Input Assistance
Help users avoid and correct mistakes.
- 3.3.1 Error Identification (A)
If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
- 3.3.2 Labels or Instructions (A)
Labels or instructions are provided when content requires user input.
- 3.3.3 Error Suggestion (AA)
If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
- 3.3.4 Error Prevention (Legal, Financial, Data) (AA)
For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, submissions should be reversible, data entered by the user can be checked for input errors and the user is provided an opportunity to correct them and a mechanism should be available for reviewing, confirming, and correcting information before finalizing the submission.
WCAG Principle 4: Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 4.1: Compatible
Maximize compatibility with current and future user agents, including assistive technologies.
- 4.1.1 Parsing (A)
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.
- 4.1.2 Name, Role, Value (A)
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.
- 4.1.3 Status Messages (AA)
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.