A common failure is a recurring implementation pattern that causes content to fail a particular WCAG success criterion. Common failures belong to WCAG’s informative guidance; techniques are not mandatory for conformance. section 1.5.1
Table 1.1 List of WCAG techniques and failure code prefixes, including a description and an example. The prefix identifies the category (technology or failure), while the number identifies each technique or failure within that category.
|
Code
|
Description
|
Example
|
|
G
|
General techniques that apply across content types and technologies
|
G1: Adding a link at the top of each page that goes directly to the main content area
|
|
H
|
HTML techniques
|
H42: Using h1-h6 to identify headings
|
|
C
|
CSS techniques
|
C40: Creating a two-color focus indicator to ensure sufficient contrast with all components
|
|
SCR
|
Client-side scripting techniques
|
SCR16: Providing a script that warns the user a time limit is about to expire
|
|
SVR
|
Server-side scripting techniques
|
SVR5: Specifying the default language in the HTTP header
|
|
ARIA
|
Techniques for adding accessibility information when native HTML is not enough
|
ARIA25: Using an ARIA live region to convey the status of a progress bar
|
|
PDF
|
Techniques to create an accessible PDF document
|
PDF9: Providing headings by marking content with heading tags in PDF documents
|
|
SM
|
Synchronized Multimedia Integration Language (SMIL) techniques.
|
SM12: Providing captions through synchronized text streams in SMIL 2.0
|
|
T
|
Techniques to make plain-text content accessible
|
T1: Using standard text formatting conventions for paragraphs
|
|
F
|
Common failures
|
F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers
|
Use the code-prefix table to distinguish failure codes from technology-specific technique codes. section 1.5.1
