Skip to content
This repository has been archived by the owner on Aug 20, 2024. It is now read-only.

Commit

Permalink
Update docs.md
Browse files Browse the repository at this point in the history
  • Loading branch information
shawna-slh authored Oct 5, 2023
1 parent 9253029 commit 3534da8
Showing 1 changed file with 12 additions and 10 deletions.
22 changes: 12 additions & 10 deletions content/docs.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: "The WCAG 2 Documents"
nav_title: "The Documents"

lang: en # Change "en" to the translated-language shortcode from https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
last_updated: 2022-11-17 # Put the date of this translation YYYY-MM-DD (with month in the middle)
last_updated: 2023-10-05 # Put the date of this translation YYYY-MM-DD (with month in the middle)

# translators: # remove from the beginning of this line and the lines below: "# " (the hash sign and the space)
# - name: "Jan Doe" # Replace Jan Doe with translator name
Expand All @@ -31,7 +31,7 @@ description: Describes Web Content Accessibility Guidelines (WCAG) 2 supporting
# Translate the Working Group name. Leave the Working Group acronym in English.
# Do not change the dates in the footer below.
footer: >
<p><strong>Date:</strong> Updated 17 November 2022. First published July 2005.</p>
<p><strong>Date:</strong> Updated 5 October 2023. First published July 2005.</p>
<p><strong>Editor:</strong> <a href="http://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>. Contributors: <a href="http://www.w3.org/People/hidde/">Hidde de Vries</a> and <a href="http://www.w3.org/People/shadi/">Shadi Abou-Zahra</a>.</p>
<p>Developed with input from the Education and Outreach Working Group (<a href="https://www.w3.org/WAI/about/groups/eowg/">EOWG</a>).</p>
Expand Down Expand Up @@ -85,23 +85,25 @@ The supporting documents directly relate to WCAG guidelines and success criteria
* how it helps people with different disabilities
* browser and assistive technology support notes
* examples
* resources, such as [tools to check contrast between colors](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html#resources)
* resources

More:
* [About Understanding Documents](https://www.w3.org/WAI/WCAG21/Understanding/intro)
* **[About Understanding Documents](https://www.w3.org/WAI/WCAG22/Understanding/intro)**
* **[2.2 Understanding Document List](https://www.w3.org/WAI/WCAG22/Understanding/)**
* [2.1 Understanding Document List](https://www.w3.org/WAI/WCAG21/Understanding/)
* [2.0 Understanding Document List](https://www.w3.org/TR/UNDERSTANDING-WCAG20/)

### Techniques

<cite>Techniques for WCAG</cite> give specific guidance **for developers** on how to develop accessible web content. It provides general and technology-specific examples, including for HTML, CSS, scripting, multimedia, and [WAI-ARIA](/standards-guidelines/aria/).
<cite>Techniques for WCAG</cite> give specific guidance **for developers** on how to develop accessible web content. It provides general and technology-specific examples, including for HTML, CSS, scripting, multimedia, and WAI-ARIA.

* **Sufficient techniques** are examples of ways to meet success criteria. If you follow the sufficient techniques for the success criteria, then you meet the criteria.
* **Advisory techniques** are suggested ways to improve accessibility. They are very helpful to some users, and may be the only way that some users can access some types of content.
* **Failures** are things that cause accessibility barriers and fail specific success criteria.

More:
* [About Techniques](https://www.w3.org/WAI/WCAG21/Understanding/understanding-techniques)
* **[About Techniques](https://www.w3.org/WAI/WCAG22/Understanding/understanding-techniques)**
* **[2.2 Techniques List](https://www.w3.org/WAI/WCAG22/Techniques/)**
* [2.1 Techniques List](https://www.w3.org/WAI/WCAG21/Techniques/)
* [2.0 Techniques List](https://www.w3.org/TR/WCAG20-TECHS/)

Expand All @@ -114,14 +116,14 @@ Test Rules describe how to test conformance to WCAG success criteria. They are p

## Supplemental Guidance {#supplement}

Supplemental guidance goes beyond the requirements of WCAG. It is **not required** to meet WCAG. Much of the guidance is essential for people with certain impairments, including cognitive and learning disabilities and low vision.
Supplemental guidance goes beyond the requirements of WCAG. It is **not required** to meet WCAG. Much of the guidance is essential for people with certain impairments, including cognitive and learning disabilities.

* [About Supplemental Guidance](/WCAG2/supplemental/about/)
* [All Supplemental Guidance list](/WCAG2/supplemental/)
* **[About Supplemental Guidance](/WCAG2/supplemental/about/)**
* **[All Supplemental Guidance list](/WCAG2/supplemental/)**

## Additional Resources

Before you start working with WCAG, you probably want to read these resources:
**Before you start working with WCAG**, you probably want to read these resources:
* [[Introduction to Web Accessibility]](/fundamentals/accessibility-intro/)
* [[Accessibility Principles]](/fundamentals/accessibility-principles/)
* [[Web Content Accessibility Guidelines (WCAG) Overview]](/standards-guidelines/wcag/)
Expand Down

0 comments on commit 3534da8

Please sign in to comment.