Resources • Open data
WCAG 2.2 success criteria as data: CSV, Excel and JSON
Reviewed by Khushwant Parihar, CPACC
Updated
All 86WCAG 2.2 success criteria, one row each, with W3C's exact wording, levels, guidelines, the version each one arrived in and links to the Recommendation, Understanding and How to Meet pages. Built from W3C's official machine-readable file and checked row by row against our own criteria data.
Source: W3C wcag.json, retrieved .WCAG 2.2 is a W3C Recommendation 12 December 2024. Page reviewed .
Download the data
The three files hold the same 86 rows and the same 14 columns. Free, no account needed.
CSV
UTF-8 with a byte order mark, comma separated, RFC 4180 quoting, one header row. Multi-line criterion text is quoted, so use a real CSV parser rather than splitting on line breaks.
Download wcag-2.2.csv(CSV, 65 KB)Excel (.xlsx)
A "WCAG 2.2" sheet with the data, a filter on the header row and every cell stored as text, plus an "About" sheet with the W3C attribution, licence and column notes.
Download wcag-2.2.xlsx(Excel, 60 KB)JSON
A metadata object (source, retrieval date, licence, attribution, counts, column dictionary) followed by a criteria array. Served with open CORS, so scripts can fetch it directly.
Download wcag-2.2.json(JSON, 101 KB)
What is in the files
- WCAG 2.2 success criteria, one row each
- 86W3C wcag.json,
- Level A, AA and AAA criteria
- 31 / 24 / 31W3C wcag.json,
- Criteria new in WCAG 2.2; 17 arrived in 2.1 and 60 date from 2.0
- 9W3C wcag.json, versions field,
Column dictionary
Columns marked W3C are copied without change from W3C's file. URLs marked as built from the W3C id follow W3C's own URL patterns. The two Accessibility.build columns are ours and are not WCAG text. The examples are the row for 1.4.3 Contrast (Minimum).
| Column | Source | Meaning | Example |
|---|---|---|---|
| ref | W3C | Success criterion number. Stored as text, so 1.4.10 never turns into a number or a date. | 1.4.3 |
| title | W3C | Short name of the success criterion (the W3C handle), verbatim. | Contrast (Minimum) |
| level | W3C | Conformance level: A, AA or AAA. | AA |
| principle | W3C | Principle number and name. | 1 Perceivable |
| guideline | W3C | Guideline number and name. | 1.4 Distinguishable |
| w3c_id | W3C | W3C's identifier for the criterion, used in its URLs and in wcag.json. | contrast-minimum |
| introduced_in | W3C | The WCAG version that first included the criterion: 2.0, 2.1 or 2.2. | 2.0 |
| new_in_2_2 | W3C | true when the criterion was introduced in WCAG 2.2, derived from introduced_in. | false |
| w3c_text | W3C | Full normative text of the criterion, verbatim: the lead sentence, then each listed condition or exception on its own line starting with "- ", then any notes. HTML tags are removed; the words are unchanged. | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: ... |
| w3c_spec_url | Built from W3C id | Link to the criterion in the WCAG 2.2 Recommendation. | https://www.w3.org/TR/WCAG22/#contrast-minimum |
| understanding_url | Built from W3C id | W3C's Understanding document for the criterion (intent, examples, techniques). | https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html |
| how_to_meet_url | Built from W3C id | The criterion in W3C's How to Meet WCAG 2.2 quick reference. | https://www.w3.org/WAI/WCAG22/quickref/#contrast-minimum |
| accessibility_build_url | Accessibility.build | Our guide page for the criterion. | https://accessibility.build/wcag/1-4-3 |
| accessibility_build_summary | Accessibility.build | A one-sentence plain-language summary written by Accessibility.build. It is not WCAG text, is not endorsed by W3C, and must not be quoted as the success criterion. | Text has a contrast ratio of at least 4.5:1 (3:1 for large text). |
Preview: the first 3 rows
A selection of columns from the top of the file. The criterion text is shown exactly as it appears in the downloads, with listed conditions and notes on their own lines.
| ref | title | level | introduced_in | w3c_text (W3C, verbatim) | accessibility_build_summary (ours) |
|---|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | 2.0 | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. - Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.) - Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) - Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content. - Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content. - CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. - Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. | All non-text content has appropriate text alternatives that serve the equivalent purpose. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | 2.0 | 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 labeled as such: - Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. - Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content. | Provide alternatives for prerecorded audio-only and video-only content. |
| 1.2.2 | Captions (Prerecorded) | A | 2.0 | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Captions are provided for all prerecorded audio content in synchronized media. |
Attribution and licence
The WCAG text belongs to W3C. It is published under the W3C Document License, and the README for W3C's JSON files sets the terms for this data specifically. Together they ask for three things:
- Attribute and link.Name the WCAG source and link to it. The Document License also asks every copy to carry W3C's copyright notice and the document's status.
- Do not change the content. W3C text is reused word for word. The Document License grants no right to modify it.
- Keep additions separate. Anything you add must be clearly distinguishable from what came from the WCAG documents.
These files follow all three. Every W3C column is copied without change, and every row links to the criterion in the Recommendation. The full attribution travels inside the JSON file (in its metadata) and the Excel file (on its About sheet). A CSV has no place for a notice without breaking parsers, so if you pass the CSV on, put this text alongside it:
The success criterion numbers, titles, levels, principles, guidelines, identifiers, versions and text in this file are copied without change from Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation 12 December 2024, https://www.w3.org/TR/WCAG22/ (dated version https://www.w3.org/TR/2024/REC-WCAG22-20241212/), using W3C's machine-readable file https://www.w3.org/WAI/WCAG22/wcag.json. Copyright © 2020-2024 World Wide Web Consortium. W3C® liability, trademark and document use rules apply. https://www.w3.org/copyright/document-license-2023/ The accessibility_build_url and accessibility_build_summary columns are added by Accessibility.build. They are not WCAG text and are not endorsed by W3C.
Our columns are ours. accessibility_build_summary and accessibility_build_url are written by Accessibility.build. The summaries are short paraphrases for scanning a list; they are not WCAG text, they are not covered by the W3C licence and they are not endorsed by W3C. Never present a summary as the success criterion.
W3C's names and trademarks may not be used in advertising without W3C's permission. This section is our reading of W3C's published terms, not legal advice; the Using WAI Material page is W3C's own guide.
How this differs from W3C's wcag.json
W3C has published WCAG 2 as machine-readable JSON since October 2025. It is the authoritative source and these files are built from it. The differences are all about shape, not wording:
- Filtered to WCAG 2.2.W3C's 2.2 file still lists 4.1.1 Parsing (Obsolete and removed), which belongs to WCAG 2.0 and 2.1 only. We keep the 86 criteria whose versions include 2.2.
- Flattened. W3C nests criteria inside guidelines inside principles and stores the text as HTML with glossary links. Here each criterion is one row, with its principle and guideline repeated on the row and its text as plain text.
- CSV and Excel as well as JSON. W3C offers JSON only. Spreadsheets need no code to open.
- Links added.Each row carries the Recommendation, Understanding and How to Meet URLs, built from W3C's identifier, and a link to our guide for the criterion.
- Less detail.Techniques, failures and glossary terms are left out. Use W3C's file if you need them.
How the files are kept up to date
The files are generated when the site is built, from a dated copy of W3C's wcag.json kept in our repository. The current copy was downloaded on ; W3C last changed the file on . W3C's README says the JSON files are published monthly.
Each build checks every row against our own WCAG 2.2 criteria list: the set of criteria, titles, levels, guidelines, the version introduced and the level counts must all agree, and 4.1.1 must be absent. If anything disagrees the build stops, so a file that reaches this page has passed those checks. When W3C changes its file, we download it again, rerun the checks and republish, and the date above changes with it.
Browse the 86 criteria
Every row in the files has a guide page on this site. The 9 criteria new in WCAG 2.2 are marked.
Principle 1 Perceivable
- 1.1.1 Non-text Content (Level A)
- 1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
- 1.2.2 Captions (Prerecorded) (Level A)
- 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
- 1.2.4 Captions (Live) (Level AA)
- 1.2.5 Audio Description (Prerecorded) (Level AA)
- 1.2.6 Sign Language (Prerecorded) (Level AAA)
- 1.2.7 Extended Audio Description (Prerecorded) (Level AAA)
- 1.2.8 Media Alternative (Prerecorded) (Level AAA)
- 1.2.9 Audio-only (Live) (Level AAA)
- 1.3.1 Info and Relationships (Level A)
- 1.3.2 Meaningful Sequence (Level A)
- 1.3.3 Sensory Characteristics (Level A)
- 1.3.4 Orientation (Level AA)
- 1.3.5 Identify Input Purpose (Level AA)
- 1.3.6 Identify Purpose (Level AAA)
- 1.4.1 Use of Color (Level A)
- 1.4.2 Audio Control (Level A)
- 1.4.3 Contrast (Minimum) (Level AA)
- 1.4.4 Resize Text (Level AA)
- 1.4.5 Images of Text (Level AA)
- 1.4.6 Contrast (Enhanced) (Level AAA)
- 1.4.7 Low or No Background Audio (Level AAA)
- 1.4.8 Visual Presentation (Level AAA)
- 1.4.9 Images of Text (No Exception) (Level AAA)
- 1.4.10 Reflow (Level AA)
- 1.4.11 Non-text Contrast (Level AA)
- 1.4.12 Text Spacing (Level AA)
- 1.4.13 Content on Hover or Focus (Level AA)
Principle 2 Operable
- 2.1.1 Keyboard (Level A)
- 2.1.2 No Keyboard Trap (Level A)
- 2.1.3 Keyboard (No Exception) (Level AAA)
- 2.1.4 Character Key Shortcuts (Level A)
- 2.2.1 Timing Adjustable (Level A)
- 2.2.2 Pause, Stop, Hide (Level A)
- 2.2.3 No Timing (Level AAA)
- 2.2.4 Interruptions (Level AAA)
- 2.2.5 Re-authenticating (Level AAA)
- 2.2.6 Timeouts (Level AAA)
- 2.3.1 Three Flashes or Below Threshold (Level A)
- 2.3.2 Three Flashes (Level AAA)
- 2.3.3 Animation from Interactions (Level AAA)
- 2.4.1 Bypass Blocks (Level A)
- 2.4.2 Page Titled (Level A)
- 2.4.3 Focus Order (Level A)
- 2.4.4 Link Purpose (In Context) (Level A)
- 2.4.5 Multiple Ways (Level AA)
- 2.4.6 Headings and Labels (Level AA)
- 2.4.7 Focus Visible (Level AA)
- 2.4.8 Location (Level AAA)
- 2.4.9 Link Purpose (Link Only) (Level AAA)
- 2.4.10 Section Headings (Level AAA)
- 2.4.11 Focus Not Obscured (Minimum) (Level AA, new in 2.2)
- 2.4.12 Focus Not Obscured (Enhanced) (Level AAA, new in 2.2)
- 2.4.13 Focus Appearance (Level AAA, new in 2.2)
- 2.5.1 Pointer Gestures (Level A)
- 2.5.2 Pointer Cancellation (Level A)
- 2.5.3 Label in Name (Level A)
- 2.5.4 Motion Actuation (Level A)
- 2.5.5 Target Size (Enhanced) (Level AAA)
- 2.5.6 Concurrent Input Mechanisms (Level AAA)
- 2.5.7 Dragging Movements (Level AA, new in 2.2)
- 2.5.8 Target Size (Minimum) (Level AA, new in 2.2)
Principle 3 Understandable
- 3.1.1 Language of Page (Level A)
- 3.1.2 Language of Parts (Level AA)
- 3.1.3 Unusual Words (Level AAA)
- 3.1.4 Abbreviations (Level AAA)
- 3.1.5 Reading Level (Level AAA)
- 3.1.6 Pronunciation (Level AAA)
- 3.2.1 On Focus (Level A)
- 3.2.2 On Input (Level A)
- 3.2.3 Consistent Navigation (Level AA)
- 3.2.4 Consistent Identification (Level AA)
- 3.2.5 Change on Request (Level AAA)
- 3.2.6 Consistent Help (Level A, new in 2.2)
- 3.3.1 Error Identification (Level A)
- 3.3.2 Labels or Instructions (Level A)
- 3.3.3 Error Suggestion (Level AA)
- 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
- 3.3.5 Help (Level AAA)
- 3.3.6 Error Prevention (All) (Level AAA)
- 3.3.7 Redundant Entry (Level A, new in 2.2)
- 3.3.8 Accessible Authentication (Minimum) (Level AA, new in 2.2)
- 3.3.9 Accessible Authentication (Enhanced) (Level AAA, new in 2.2)
Principle 4 Robust
- 4.1.2 Name, Role, Value (Level A)
- 4.1.3 Status Messages (Level AA)
Looking for a checklist instead?
- WCAG 2.2 Excel checklist: an audit template with status, notes and progress columns.
- WCAG 2.2 checklist: every criterion explained, grouped by principle and level.
- Interactive WCAG checklist: tick criteria off in the browser and track progress.
- WCAG 2.2 guide: plain-language pages for every success criterion.
Frequently Asked Questions
How many success criteria are in WCAG 2.2?
86. Level A has 31, Level AA has 24 and Level AAA has 31. Of those, 60 date from WCAG 2.0, 17 were added in WCAG 2.1 and 9 were added in WCAG 2.2. A site that conforms at Level AA meets the 55 Level A and AA criteria. Every one of them is a row in the CSV, Excel and JSON files on this page.
Why is 4.1.1 Parsing not in the files?
Because it is not part of WCAG 2.2. W3C's own WCAG 2.2 JSON file still carries an entry for 4.1.1, titled "Parsing (Obsolete and removed)", with no conformance level and with versions 2.0 and 2.1 only. We build the 2.2 set by keeping the criteria whose versions include 2.2, which leaves 4.1.1 out. If you work to WCAG 2.1, where 4.1.1 still applies, take it from the WCAG 2.1 Recommendation or W3C's WCAG 2.1 JSON file.
Can I use this data in my own tool, product or audit template?
Yes, on W3C's terms. The README for W3C's JSON files allows the data to be used in full or in part if you clearly attribute and link the WCAG source and do not change the content, and if anything you add is clearly marked as yours. That is how these files are built: the W3C columns are copied without change and carry the attribution, and our two added columns are named accessibility_build_url and accessibility_build_summary. Keep the attribution with any copy you make, and keep our summaries apart from the W3C text.
Is the summary column the official WCAG wording?
No. accessibility_build_summary is a one-sentence plain-language paraphrase written by Accessibility.build for quick scanning. It is shorter than the real criterion and leaves out exceptions and notes, so it must not be quoted as the success criterion or used to decide conformance. The official wording is in the w3c_text column, copied without change from W3C.
How is this different from the WCAG 2.2 Excel checklist?
The Excel checklist is an audit template: it has status, notes and progress-tracking columns and summary sheets for running an audit by hand. This page is the data itself: one clean row per criterion with W3C's full text, identifiers and links, for loading into a database, a test tool, a ticketing system or your own template. If you want to track an audit, use the checklist; if you want to build something, use these files.
Will Excel change criterion numbers like 1.4.10?
Not in the .xlsx file, where every cell is stored as text. A CSV has no cell types, so when Excel opens one directly it may read a value such as 1.4.10 as a date or a number, depending on your regional settings. If that happens, use the .xlsx file, or import the CSV through Excel's data import and set the ref column to Text.
Does the dataset include techniques, failures or the glossary?
No. These files flatten each success criterion into one row and stop there. W3C's wcag.json also holds the sufficient and advisory techniques, the failures and the glossary terms, nested under each criterion; if you need those, use W3C's file directly. Each row here links to the criterion's Understanding document and How to Meet entry, which list the techniques.
How current is the data?
The files are built from a copy of W3C's wcag.json downloaded on 11 November 2026; W3C last changed that file on 6 November 2026. The criterion text itself comes from the WCAG 2.2 Recommendation of 12 December 2024. The retrieval date is printed on this page and inside every file, so you can always tell which copy you have.
Sources
The data and the licence terms were read from the documents below on .
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation 12 December 2024
- WCAG 2.2 machine-readable data file (wcag.json), W3C Web Accessibility Initiative
- README for the WCAG JSON files, including the terms for using the data, w3c/wcag repository on GitHub
- Announcement: WCAG 2 available as JSON machine-readable files, public-wai-announce mailing list, 16 October 2025
- W3C Document License (2023)
- Using WAI Material: Permission to Use WAI-Copyrighted Material, W3C Web Accessibility Initiative
- W3C Intellectual Rights FAQ: May I annotate one of your specifications?
- Dataset structured data documentation, Google Search Central
Essential Accessibility Resources
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences