From 346ae67bf17cf9184743432d231e1b9779cd6e9b Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 25 Jan 2024 18:03:41 +0100 Subject: [PATCH] WCAG 2.2 migration (#2147) * Update links in rules to go to 2.2 * Update glossary links to use WCAG 2.2 * Add WCAG 2.2 to tests * Update design docs to link to WCAG 2.2 * Replace uses of "WCAG 2.0|1" where needed with "WCAG 2.2" * Various aria corrections * Update _rules/role-attribute-valid-value-674b10.md Co-authored-by: Jean-Yves Moyen * Update _rules/document-has-landmark-with-non-repeated-content-b40fd1.md Co-authored-by: Jean-Yves Moyen * Fix failing test --------- Co-authored-by: Jean-Yves Moyen --- README.md | 4 +-- __tests__/link-is-outdated.js | 12 +++++--- __tests__/spelling-ignore.yml | 2 ++ _rules/aria-attr-defined-5f99a7.md | 6 ++-- ...aria-hidden-no-focusable-content-6cfa84.md | 10 +++---- _rules/aria-required-context-role-ff89c9.md | 6 ++-- _rules/aria-required-id-references-in6db8.md | 2 +- _rules/aria-required-owned-element-bc4a75.md | 4 +-- ...aria-state-or-property-permitted-5c01ea.md | 6 ++-- ...ia-state-or-property-valid-value-6a7281.md | 4 +-- _rules/attr-not-duplicated-e6952f.md | 2 +- _rules/audio-as-media-alternative-afb423.md | 2 +- ...oids-automatically-playing-audio-80f0bf.md | 8 +++--- _rules/audio-text-alternative-e7aa44.md | 4 +-- _rules/audio-transcript-2eb176.md | 6 ++-- ...-audio-does-not-exceed-3-seconds-aaa1bf.md | 10 +++---- ...play-audio-has-control-mechanism-4c31df.md | 6 ++-- _rules/auto-update-text-efbfc7.md | 10 +++---- _rules/autocomplete-valid-value-73f2c2.md | 16 +++++------ _rules/block-collapsible-3e12e1.md | 4 +-- ...button-non-empty-accessible-name-97a4e1.md | 16 +++++------ _rules/bypass-blocks-cf77f2.md | 22 +++++++-------- _rules/css-restrict-orientation-b33eff.md | 14 +++++----- _rules/device-motion-disabled-c249d5.md | 8 +++--- _rules/device-motion-user-interface-7677a9.md | 8 +++--- ...eadings-for-non-repeated-content-047fe0.md | 20 ++++++------- ...strument-to-non-repeated-content-ye5d6e.md | 8 +++--- ...ndmark-with-non-repeated-content-b40fd1.md | 8 +++--- ...nt-lang-matches-default-language-off6ek.md | 12 ++++---- _rules/element-lang-valid-de46e4.md | 8 +++--- ...marked-decorative-is-not-exposed-46ca7f.md | 10 +++---- ...-image-non-empty-accessible-name-7d6734.md | 8 +++--- _rules/focusable-no-keyboard-trap-80af7b.md | 8 +++--- ...o-keyboard-trap-non-standard-nav-ebe86a.md | 6 ++-- ...le-no-keyboard-trap-standard-nav-a1b64e.md | 8 +++--- _rules/form-field-label-descriptive-cc0f0a.md | 18 ++++++------ ...-field-non-empty-accessible-name-e086e5.md | 17 +++++------ _rules/heading-descriptive-b49b2e.md | 20 ++++++------- ...eading-non-empty-accessible-name-ffd0e9.md | 8 +++--- _rules/html-page-lang-b5c3f8.md | 6 ++-- .../html-page-lang-matches-default-ucwvc8.md | 10 +++---- _rules/html-page-lang-valid-bf051a.md | 10 +++---- .../html-page-lang-xml-lang-match-5b7ae0.md | 8 +++--- _rules/html-page-non-empty-title-2779a5.md | 12 ++++---- _rules/html-page-title-descriptive-c4a8a4.md | 6 ++-- _rules/id-value-unique-3ea0c8.md | 4 +-- ...dentical-name-equivalent-purpose-4b1c6c.md | 6 ++-- ...iframe-non-empty-accessible-name-cae760.md | 8 +++--- ...interactive-content-in-tab-order-akn7bn.md | 12 ++++---- ...mage-accessible-name-descriptive-qt1vmo.md | 14 +++++----- ...button-non-empty-accessible-name-59796f.md | 16 +++++------ ...mage-filename-as-accessible-name-9eb3f6.md | 10 +++---- _rules/image-no-text-0va7u6.md | 8 +++--- .../image-non-empty-accessible-name-23a2a8.md | 20 ++++++------- ...ge-not-in-acc-tree-is-decorative-e88epe.md | 16 +++++------ ...rtant-letter-spacing-wide-enough-24afc2.md | 6 ++-- ...mportant-line-height-wide-enough-78fd32.md | 4 +-- ...portant-word-spacing-wide-enough-9e45ec.md | 6 ++-- _rules/invalid-form-field-value-36b590.md | 12 ++++---- _rules/link-alone-descriptive-aizyf1.md | 16 +++++------ _rules/link-in-context-descriptive-5effbb.md | 28 +++++++++---------- .../link-non-empty-accessible-name-c487ae.md | 14 +++++----- ...dentical-name-equivalent-purpose-b20e66.md | 8 +++--- ...context-serve-equivalent-purpose-fd3a94.md | 4 +-- _rules/menuitem-non-empty-name-m6b1q3.md | 10 +++---- _rules/meta-refresh-no-delay-bc659a.md | 12 ++++---- ...ta-refresh-no-delay-no-exception-bisz58.md | 8 +++--- _rules/meta-viewport-b4f0c3.md | 14 +++++----- ...non-visual-reference-alternative-9bd38c.md | 18 ++++++------ _rules/object-has-accessible-name-8fc3b6.md | 2 +- ...al-children-no-focusable-content-307n5z.md | 4 +-- .../printable-characters-shortcut-ffbc54.md | 8 +++--- ...e-required-states-and-properties-4e8ab6.md | 2 +- ...able-element-keyboard-accessible-0ssw9k.md | 16 +++++------ ...usable-element-has-visible-focus-oj04fd.md | 8 +++--- ...e-header-cell-has-assigned-cells-d0f69e.md | 18 ++++++------ ...rs-attribute-refer-to-data-cells-a25f45.md | 8 +++--- _rules/text-contrast-afw4f7.md | 20 ++++++------- _rules/text-contrast-enhanced-09o5cg.md | 20 ++++++------- .../video-alternative-for-auditory-eac66b.md | 8 +++--- _rules/video-alternative-for-visual-c5a4ea.md | 12 ++++---- _rules/video-as-media-alternative-ab4d13.md | 6 ++-- _rules/video-audio-description-1ea59c.md | 8 +++--- _rules/video-captions-f51b46.md | 10 +++---- _rules/video-description-track-f196ce.md | 8 +++--- ...ideo-only-alternative-for-visual-c3232f.md | 8 +++--- .../video-only-as-media-alternative-fd26cf.md | 4 +-- _rules/video-only-audio-track-d7ba54.md | 4 +-- _rules/video-only-description-track-ac7dc6.md | 4 +-- _rules/video-only-transcript-ee13b5.md | 6 ++-- ...eo-strict-alternative-for-visual-1ec09b.md | 10 +++---- _rules/video-transcript-1a02b0.md | 12 ++++---- ...visible-label-in-accessible-name-2ee8b8.md | 14 +++++----- .../zoom-text-no-overflow-clipping-59br37.md | 8 +++--- pages/about.md | 4 +-- pages/design/definition-of-done.md | 4 +-- pages/design/rule-design.md | 7 ++--- pages/design/rule-template.md | 12 ++++---- pages/design/test-cases.md | 4 +-- pages/glossary/attribute-value.md | 2 +- pages/glossary/clearly-labeled-location.md | 2 +- pages/glossary/disabled-element.md | 2 +- pages/glossary/essential-text-presentation.md | 2 +- pages/glossary/form-field-error-indicator.md | 6 ++-- pages/glossary/highest-possible-contrast.md | 2 +- pages/glossary/inheriting-semantic-role.md | 2 +- pages/glossary/insignificant.md | 2 +- pages/glossary/instrument.md | 6 ++-- pages/glossary/marked-as-decorative.md | 4 +-- pages/glossary/owned-by.md | 2 +- pages/glossary/perceivable-content.md | 4 +-- ...rogrammatically-determined-link-context.md | 2 +- pages/glossary/semantic-role.md | 2 +- pages/glossary/visible.md | 2 +- pages/glossary/web-page-html.md | 4 +-- pages/implementations/earl-reports.md | 2 +- 116 files changed, 495 insertions(+), 489 deletions(-) diff --git a/README.md b/README.md index 2f137ae81e8..632b3b7c656 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ For more information, see [ACT Overview - What is ACT](https://www.w3.org/WAI/GL ## Write rules, not tools -An ACT rule is a unambiguous description of what the results of accessibility test tools and methodologies be when running a conformance test for the [Web Content Accessibility Guidelines][wcag21]. The rules are written without a specific implementation in mind. The goal is not to create an accessibility test tool. Instead we aim to harmonize between existing tools, and improve their transparency and the overall quality of their results. +An ACT rule is a unambiguous description of what the results of accessibility test tools and methodologies be when running a conformance test for the [Web Content Accessibility Guidelines][wcag22]. The rules are written without a specific implementation in mind. The goal is not to create an accessibility test tool. Instead we aim to harmonize between existing tools, and improve their transparency and the overall quality of their results. If you want to know more about us, visit our website at: [www.w3.org/community/act-r][act-r]. @@ -34,5 +34,5 @@ For info on how to use this GitHub repository, see the [ACT-Rules GitHub Guideli This repository automatically pushes changes to rules to the [w3c/wcag-act-rules](https://github.com/w3c/wcag-act-rules/) repository. There is an "Approve rule" action available which can be triggered manually by an ACT Task Force facilitator, which will set a proposed rule to "approved". -[wcag21]: https://www.w3.org/TR/WCAG21/ +[wcag22]: https://www.w3.org/TR/WCAG22/ [act-r]: https://www.w3.org/community/act-r/ diff --git a/__tests__/link-is-outdated.js b/__tests__/link-is-outdated.js index 81677cca2a2..0e2ff2d08af 100644 --- a/__tests__/link-is-outdated.js +++ b/__tests__/link-is-outdated.js @@ -14,10 +14,14 @@ const uniqueArray = require('../utils/unique-array') * Map of bad links vs their recommendations */ const badLinksAndRecommendations = { - '://www.w3.org/TR/WCAG20/': 'Use WCAG 2.1 reference- https://www.w3.org/WAI/WCAG21/', - '://www.w3.org/TR/UNDERSTANDING-WCAG20/': 'Use WCAG 2.1 reference - https://www.w3.org/WAI/WCAG21/Understanding/', - '://www.w3.org/TR/WCAG20-TECHS/': 'Use WCAG 2.1 reference - https://www.w3.org/WAI/WCAG21/Techniques/', - '://www.w3.org/TR/wai-aria-1.0/': 'Use ARIA 1.1 reference - https://www.w3.org/TR/wai-aria-1.1/', + '://www.w3.org/TR/WCAG20/': 'Use WCAG 2.2 reference- https://www.w3.org/WAI/WCAG22/', + '://www.w3.org/TR/WCAG21/': 'Use WCAG 2.2 reference- https://www.w3.org/WAI/WCAG22/', + '://www.w3.org/TR/UNDERSTANDING-WCAG20/': 'Use WCAG 2.2 reference - https://www.w3.org/WAI/WCAG22/Understanding/', + '://www.w3.org/WAI/WCAG21/Understanding/': 'Use WCAG 2.2 reference- ://www.w3.org/WAI/WCAG22/Understanding/', + '://www.w3.org/TR/WCAG20-TECHS/': 'Use WCAG 2.2 reference - https://www.w3.org/WAI/WCAG22/Techniques/', + '://www.w3.org/WAI/WCAG21/Techniques/': 'Use WCAG 2.2 reference - https://www.w3.org/WAI/WCAG22/Techniques/', + '://www.w3.org/TR/wai-aria-1.0/': 'Use ARIA 1.2 reference - https://www.w3.org/TR/wai-aria-1.2/', + '://www.w3.org/TR/wai-aria-1.1/': 'Use ARIA 1.2 reference - https://www.w3.org/TR/wai-aria-1.2/', '://www.w3.org/TR/dom41/': 'Use http://dom.spec.whatwg.org', '://www.w3.org/TR/html/': 'Use http://html.spec.whatwg.org', '://www.w3.org/TR/html52/': 'Use http://html.spec.whatwg.org', diff --git a/__tests__/spelling-ignore.yml b/__tests__/spelling-ignore.yml index c11d183830e..81316f10c55 100644 --- a/__tests__/spelling-ignore.yml +++ b/__tests__/spelling-ignore.yml @@ -28,6 +28,7 @@ - WCAG - WCAG2 - WCAG21 +- WCAG22 - CSS3 - css # lowercase needed in reference list - UA @@ -120,6 +121,7 @@ - multipage - attr-input-type - wai-aria-1.1 +- wai-aria-1.2 # Notes and acronyms - TODO diff --git a/_rules/aria-attr-defined-5f99a7.md b/_rules/aria-attr-defined-5f99a7.md index 60c74b84595..cc26dc7185a 100755 --- a/_rules/aria-attr-defined-5f99a7.md +++ b/_rules/aria-attr-defined-5f99a7.md @@ -42,9 +42,9 @@ The presence of unknown ARIA attributes is often the result of a typo or other d - [ARIA in HTML](https://www.w3.org/TR/html-aria/#index-aria-global) - [WAI ARIA Supported States and Properties](https://www.w3.org/TR/wai-aria-1.2/#supportedState) -- [G108: Using markup features to expose the name and role](https://www.w3.org/WAI/WCAG21/Techniques/general/G108) -- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) +- [G108: Using markup features to expose the name and role](https://www.w3.org/WAI/WCAG22/Techniques/general/G108) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) - [Semantics and ARIA](https://developers.google.com/web/fundamentals/accessibility/semantics-aria/) ## Test Cases diff --git a/_rules/aria-hidden-no-focusable-content-6cfa84.md b/_rules/aria-hidden-no-focusable-content-6cfa84.md index a03f6b3b3ce..dbd62d16329 100755 --- a/_rules/aria-hidden-no-focusable-content-6cfa84.md +++ b/_rules/aria-hidden-no-focusable-content-6cfa84.md @@ -44,9 +44,9 @@ Some user agents treat the value of `aria-hidden` attribute as case-sensitive. ## Background -Using `aria-hidden="false"` on a descendant of an element with `aria-hidden="true"` [**does not** expose that element](https://www.w3.org/TR/wai-aria-1.1/#aria-hidden). `aria-hidden="true"` hides itself and all its content from assistive technologies. +Using `aria-hidden="false"` on a descendant of an element with `aria-hidden="true"` [**does not** expose that element](https://www.w3.org/TR/wai-aria-1.2/#aria-hidden). `aria-hidden="true"` hides itself and all its content from assistive technologies. -By adding `aria-hidden="true"` to an element, content authors ensure that assistive technologies will ignore the element. This can be used to hide parts of a web page that are [pure decoration](https://www.w3.org/TR/WCAG21/#dfn-pure-decoration), such as icon fonts - that are not meant to be read by assistive technologies. +By adding `aria-hidden="true"` to an element, content authors ensure that assistive technologies will ignore the element. This can be used to hide parts of a web page that are [pure decoration](https://www.w3.org/TR/WCAG22/#dfn-pure-decoration), such as icon fonts - that are not meant to be read by assistive technologies. An element with an `aria-hidden` attribute set to `true` that is also part of the [sequential focus navigation][] may cause confusion for users of assistive technologies because the element can be reached via [sequential focus navigation][], but it should be hidden and not [included in the accessibility tree][]. @@ -59,9 +59,9 @@ The 1 second time span introduced in the exception of the definition of [focusab ### Bibliography - [CSS Scoping Module Level 1 (editor's draft)](https://drafts.csswg.org/css-scoping/) -- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) -- [`aria-hidden` (state)](https://www.w3.org/TR/wai-aria-1.1/#aria-hidden) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [`aria-hidden` (state)](https://www.w3.org/TR/wai-aria-1.2/#aria-hidden) - [Fourth rule of ARIA use](https://www.w3.org/TR/using-aria/#fourth) - [Element with presentational children has no focusable content](presentational-children-no-focusable-content-307n5z.md) diff --git a/_rules/aria-required-context-role-ff89c9.md b/_rules/aria-required-context-role-ff89c9.md index 79bec4eb6d8..67461d2e92f 100755 --- a/_rules/aria-required-context-role-ff89c9.md +++ b/_rules/aria-required-context-role-ff89c9.md @@ -59,7 +59,7 @@ Some user agents try to correct missing [required context roles][] or incorrect ### Bibliography -- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) - [Required Context Role][] ## Test Cases @@ -251,8 +251,8 @@ There is no element with an [explicit role][] different from its [implicit role] [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [required context role]: https://www.w3.org/TR/wai-aria-1.2/#scope 'WAI ARIA definition of Required Context Role' [required context roles]: https://www.w3.org/TR/wai-aria-1.2/#scope 'WAI ARIA definition of Required Context Role' -[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationships' -[sc411]: https://www.w3.org/TR/WCAG21/#parsing 'Success Criterion 4.1.1 Parsing' +[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationships' +[sc411]: https://www.w3.org/TR/WCAG22/#parsing 'Success Criterion 4.1.1 Parsing' [semantic role]: #semantic-role 'Definition of Semantic Role' [subclass role]: https://www.w3.org/TR/wai-aria-1.2/#subclassroles 'ARIA Specification of Subclass Role' [ul]: https://html.spec.whatwg.org/multipage/grouping-content.html#the-ul-element 'HTML specification of the ul element' diff --git a/_rules/aria-required-id-references-in6db8.md b/_rules/aria-required-id-references-in6db8.md index d90010083cd..de7401e8cb2 100644 --- a/_rules/aria-required-id-references-in6db8.md +++ b/_rules/aria-required-id-references-in6db8.md @@ -48,7 +48,7 @@ This rule is written specifically for `aria-controls`, because it is the only [I ### Bibliography -- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA5) +- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA5) - [WAI-ARIA required states and properties](https://www.w3.org/TR/wai-aria-1.2/#requiredState) - [RFC 3986](https://www.ietf.org/rfc/rfc3986.txt) diff --git a/_rules/aria-required-owned-element-bc4a75.md b/_rules/aria-required-owned-element-bc4a75.md index 939218e2bbd..1636a050a2b 100755 --- a/_rules/aria-required-owned-element-bc4a75.md +++ b/_rules/aria-required-owned-element-bc4a75.md @@ -36,7 +36,7 @@ Each test target only [owns][] elements with a [semantic role][] from the [requi ## Assumptions -If the [explicit semantic role][] on the target element is incorrectly used, and any relationships between elements are already programmatically determinable, failing this rule may not result in accessibility issues for users of assistive technologies, and it should then not be considered a failure under [WCAG success criterion 1.3.1 Info and Relationships](https://www.w3.org/TR/WCAG21/#info-and-relationships). +If the [explicit semantic role][] on the target element is incorrectly used, and any relationships between elements are already programmatically determinable, failing this rule may not result in accessibility issues for users of assistive technologies, and it should then not be considered a failure under [WCAG success criterion 1.3.1 Info and Relationships](https://www.w3.org/TR/WCAG22/#info-and-relationships). ## Accessibility Support @@ -55,7 +55,7 @@ The applicability of this rule is limited to the [WAI-ARIA 1.2 Recommendation][w ### Bibliography -- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) - [Required Owned Element](https://www.w3.org/TR/wai-aria-1.2/#mustContain) - [Owned Element](https://www.w3.org/TR/wai-aria-1.2/#dfn-owned-element) diff --git a/_rules/aria-state-or-property-permitted-5c01ea.md b/_rules/aria-state-or-property-permitted-5c01ea.md index a6e49c4e4f1..e33da0e7dec 100755 --- a/_rules/aria-state-or-property-permitted-5c01ea.md +++ b/_rules/aria-state-or-property-permitted-5c01ea.md @@ -72,11 +72,11 @@ Assessing the value of the attribute is out of scope for this rule. ### Bibliography -- [Understanding Success Criterion 4.1.1: Parsing](https://www.w3.org/WAI/WCAG21/Understanding/parsing.html) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html) +- [Understanding Success Criterion 4.1.1: Parsing](https://www.w3.org/WAI/WCAG22/Understanding/parsing.html) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html) - [WAI-ARIA 1.2, Supported States and Properties](https://www.w3.org/TR/wai-aria-1.2/#states_and_properties) - [WAI-ARIA 1.2, Global States and Properties](https://www.w3.org/TR/wai-aria-1.2/#global_states) -- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA5) +- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA5) - [Document conformance requirements for use of ARIA attributes in HTML](https://www.w3.org/TR/html-aria/#docconformance) ## Test Cases diff --git a/_rules/aria-state-or-property-valid-value-6a7281.md b/_rules/aria-state-or-property-valid-value-6a7281.md index a04df515595..fc0fe1f5307 100755 --- a/_rules/aria-state-or-property-valid-value-6a7281.md +++ b/_rules/aria-state-or-property-valid-value-6a7281.md @@ -57,8 +57,8 @@ This rule does not require the target of an `ID Reference` to exist. This is bec ### Bibliography -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html) -- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA5) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html) +- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA5) - [WAI-ARIA 1.2, Definitions of States and Properties](https://www.w3.org/TR/wai-aria-1.2/#state_prop_def) - [WAI-ARIA 1.2, Characteristics of States and Properties, Value](https://www.w3.org/TR/wai-aria-1.2/#propcharacteristic_value) - [Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)](https://www.ietf.org/rfc/rfc3986.txt) diff --git a/_rules/attr-not-duplicated-e6952f.md b/_rules/attr-not-duplicated-e6952f.md index 250c862621e..83e1d194ddf 100755 --- a/_rules/attr-not-duplicated-e6952f.md +++ b/_rules/attr-not-duplicated-e6952f.md @@ -55,7 +55,7 @@ There are no accessibility support issues known. ### Bibliography -- [H94: Ensuring that elements do not contain duplicate attributes](https://www.w3.org/WAI/WCAG21/Techniques/html/H94) +- [H94: Ensuring that elements do not contain duplicate attributes](https://www.w3.org/WAI/WCAG22/Techniques/html/H94) ## Test Cases diff --git a/_rules/audio-as-media-alternative-afb423.md b/_rules/audio-as-media-alternative-afb423.md index b122dea7ffa..7474f256ef8 100755 --- a/_rules/audio-as-media-alternative-afb423.md +++ b/_rules/audio-as-media-alternative-afb423.md @@ -47,7 +47,7 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding SC 1.2.1:Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) +- [Understanding SC 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) ## Test Cases diff --git a/_rules/audio-or-video-avoids-automatically-playing-audio-80f0bf.md b/_rules/audio-or-video-avoids-automatically-playing-audio-80f0bf.md index 11bf3b3c05a..362245bbadc 100755 --- a/_rules/audio-or-video-avoids-automatically-playing-audio-80f0bf.md +++ b/_rules/audio-or-video-avoids-automatically-playing-audio-80f0bf.md @@ -68,8 +68,8 @@ For each test target, the [outcome](#outcome) of at least one of the following r ## Assumptions - This rule assumes that it is not possible to satisfy [Success Criterion 1.4.2 Audio Control][sc142] if the total length of the automatically playing audio is more than 3 seconds, even if there are pauses in the sound and no more than 3 seconds in a row with actual sound. -- This rule assumes that the [mechanism](https://www.w3.org/TR/WCAG21/#dfn-mechanism) to control the sound must be located in the same [web page][]. Mechanisms located on other pages can still create accessibility issues for users relying on sound to navigate (e.g. screen readers users) since the autoplaying sound will interfere with their ability to find and activate the mechanism. If a [mechanism](https://www.w3.org/TR/WCAG21/#dfn-mechanism) external to the [web page][] is provided, it is possible to fail this rule but still satisfy [Success Criterion 1.4.2 Audio Control][sc142]. -- This rule assumes that the [mechanism](https://www.w3.org/TR/WCAG21/#dfn-mechanism) to control the sound must be visible and accessible in order to be effective and usable by all kinds of users. If the mechanism is hidden to some users, it is possible to fail this rule but still satisfy [Success Criterion 1.4.2 Audio Control][sc142]. +- This rule assumes that the [mechanism](https://www.w3.org/TR/WCAG22/#dfn-mechanism) to control the sound must be located in the same [web page][]. Mechanisms located on other pages can still create accessibility issues for users relying on sound to navigate (e.g. screen readers users) since the autoplaying sound will interfere with their ability to find and activate the mechanism. If a [mechanism](https://www.w3.org/TR/WCAG22/#dfn-mechanism) external to the [web page][] is provided, it is possible to fail this rule but still satisfy [Success Criterion 1.4.2 Audio Control][sc142]. +- This rule assumes that the [mechanism](https://www.w3.org/TR/WCAG22/#dfn-mechanism) to control the sound must be visible and accessible in order to be effective and usable by all kinds of users. If the mechanism is hidden to some users, it is possible to fail this rule but still satisfy [Success Criterion 1.4.2 Audio Control][sc142]. ## Accessibility Support @@ -81,7 +81,7 @@ The [instruments][instrument] used to pass this rule (if any), must meet all lev ### Bibliography -- [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG21/Understanding/audio-control.html) +- [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html) - [Accessible Multimedia](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/Multimedia) ## Test Cases @@ -198,5 +198,5 @@ This `audio` element does not play automatically. [attribute value]: #attribute-value 'Definition of Attribute Value' [instrument]: #instrument-to-achieve-an-objective 'Definition of Instrument to Achieve an Objective' [media resource]: https://html.spec.whatwg.org/multipage/media.html#media-resource 'HTML Specification of Media Resource' -[sc142]: https://www.w3.org/TR/WCAG21/#audio-control 'Success Criterion 1.4.2 Audio Control' +[sc142]: https://www.w3.org/TR/WCAG22/#audio-control 'Success Criterion 1.4.2 Audio Control' [web page]: #web-page-html 'Definition of HTML web page' diff --git a/_rules/audio-text-alternative-e7aa44.md b/_rules/audio-text-alternative-e7aa44.md index 1168a32817a..20d4af1a8e8 100755 --- a/_rules/audio-text-alternative-e7aa44.md +++ b/_rules/audio-text-alternative-e7aa44.md @@ -56,8 +56,8 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding SC 1.2.1:Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) -- [G158: Providing an alternative for time-based media for audio-only content](https://www.w3.org/WAI/WCAG21/Techniques/general/G158) +- [Understanding SC 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) +- [G158: Providing an alternative for time-based media for audio-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G158) ## Test Cases diff --git a/_rules/audio-transcript-2eb176.md b/_rules/audio-transcript-2eb176.md index bef637adc7b..25a28d92d38 100755 --- a/_rules/audio-transcript-2eb176.md +++ b/_rules/audio-transcript-2eb176.md @@ -31,7 +31,7 @@ This rule applies to every [non-streaming](#non-streaming-media-element) `audio` The auditory information of each test target is available through a text transcript. That text transcript is [visible][] and [included in the accessibility tree][], either on the page or through a link. -**Note:** A "text transcript" in the context of this rule is defined in WCAG 2 as an [alternative for time based media](https://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media). +**Note:** A "text transcript" in the context of this rule is defined in WCAG 2 as an [alternative for time based media](https://www.w3.org/TR/WCAG22/#dfn-alternative-for-time-based-media). ## Assumptions @@ -45,8 +45,8 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding SC 1.2.1:Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) -- [G158: Providing an alternative for time-based media for audio-only content](https://www.w3.org/WAI/WCAG21/Techniques/general/G158) +- [Understanding SC 1.2.1:Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) +- [G158: Providing an alternative for time-based media for audio-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G158) ## Test Cases diff --git a/_rules/auto-play-audio-does-not-exceed-3-seconds-aaa1bf.md b/_rules/auto-play-audio-does-not-exceed-3-seconds-aaa1bf.md index 73ea3ce9bb9..cdad5f0a82e 100755 --- a/_rules/auto-play-audio-does-not-exceed-3-seconds-aaa1bf.md +++ b/_rules/auto-play-audio-does-not-exceed-3-seconds-aaa1bf.md @@ -39,7 +39,7 @@ This rule applies to any `audio` or `video` element for which all the following For each test target the total audio output does not last more than 3 seconds. -**Note:** This rule does not cover single audio instances that play repeatedly for more than three seconds, or multiple audio instances for more than three seconds. The [WCAG Understanding documentation for 1.4.2 Audio Controls](https://www.w3.org/WAI/WCAG21/Understanding/audio-control.html) is ambiguous about how to handle these scenarios. +**Note:** This rule does not cover single audio instances that play repeatedly for more than three seconds, or multiple audio instances for more than three seconds. The [WCAG Understanding documentation for 1.4.2 Audio Controls](https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html) is ambiguous about how to handle these scenarios. ## Assumptions @@ -53,10 +53,10 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG21/Understanding/audio-control.html) -- [F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off](https://www.w3.org/WAI/WCAG21/Techniques/failures/F23) -- [G60: Playing a sound that turns off automatically within three seconds](https://www.w3.org/WAI/WCAG21/Techniques/general/G60) -- [G171: Playing sounds only on user request](https://www.w3.org/WAI/WCAG21/Techniques/general/G171) +- [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html) +- [F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off](https://www.w3.org/WAI/WCAG22/Techniques/failures/F23) +- [G60: Playing a sound that turns off automatically within three seconds](https://www.w3.org/WAI/WCAG22/Techniques/general/G60) +- [G171: Playing sounds only on user request](https://www.w3.org/WAI/WCAG22/Techniques/general/G171) ## Test Cases diff --git a/_rules/auto-play-audio-has-control-mechanism-4c31df.md b/_rules/auto-play-audio-has-control-mechanism-4c31df.md index 092f4a98d64..24de36af877 100755 --- a/_rules/auto-play-audio-has-control-mechanism-4c31df.md +++ b/_rules/auto-play-audio-has-control-mechanism-4c31df.md @@ -59,9 +59,9 @@ The native `video` and `audio` controls in several browser and assistive technol ### Bibliography -- [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG21/Understanding/audio-control.html) -- [Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays](https://www.w3.org/WAI/WCAG21/Techniques/failures/F93) -- [G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically](https://www.w3.org/WAI/WCAG21/Techniques/general/G170) +- [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html) +- [Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays](https://www.w3.org/WAI/WCAG22/Techniques/failures/F93) +- [G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically](https://www.w3.org/WAI/WCAG22/Techniques/general/G170) ## Test Cases diff --git a/_rules/auto-update-text-efbfc7.md b/_rules/auto-update-text-efbfc7.md index 9cdf485acbf..9d9fa658d47 100755 --- a/_rules/auto-update-text-efbfc7.md +++ b/_rules/auto-update-text-efbfc7.md @@ -308,16 +308,16 @@ This `span` element with text content that automatically changes multiple times [activation]: https://html.spec.whatwg.org/#activation [child]: https://dom.spec.whatwg.org/#concept-tree-child [clearly labeled location]: #clearly-labeled-location 'Definition of clearly labeled location' -[content]: https://www.w3.org/TR/WCAG21/#dfn-content +[content]: https://www.w3.org/TR/WCAG22/#dfn-content [descendant]: https://dom.spec.whatwg.org/#concept-tree-descendant -[essential]: https://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide.html#dfn-essential +[essential]: https://www.w3.org/WAI/WCAG22/Understanding/pause-stop-hide.html#dfn-essential [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree' -[f16]: https://www.w3.org/WAI/WCAG21/Techniques/failures/F16 -[g186]: https://www.w3.org/WAI/WCAG21/Techniques/general/G186 +[f16]: https://www.w3.org/WAI/WCAG22/Techniques/failures/F16 +[g186]: https://www.w3.org/WAI/WCAG22/Techniques/general/G186 [html document]: https://dom.spec.whatwg.org/#html-document [html element]: #namespaced-element [instrument]: #instrument-to-achieve-an-objective 'Definition of instrument to achieve an objective' -[sc 2.2.2]: https://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide +[sc 2.2.2]: https://www.w3.org/WAI/WCAG22/Understanding/pause-stop-hide [text node]: https://dom.spec.whatwg.org/#text [user interaction]: #user-interaction 'Definition of user interaction' [visible text content]: #visible-text-content 'Definition of visible text content' diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index c4798e1e832..8ce17821e7d 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -44,7 +44,7 @@ Each test target's `autocomplete` [attribute value][] is a [space separated][] l ## Assumptions -The `autocomplete` attribute is used on form fields that correspond to [Input Purposes for User Interface Components](https://www.w3.org/TR/WCAG21/#input-purposes) and collect information about the user. +The `autocomplete` attribute is used on form fields that correspond to [Input Purposes for User Interface Components](https://www.w3.org/TR/WCAG22/#input-purposes) and collect information about the user. If the `autocomplete` attribute is used to describe "custom" taxonomy, for example using the custom autocomplete value "banner" (``), success Criterion [1.3.5 Identify Input Purpose][sc135] may be satisfied even if this rule failed. @@ -73,8 +73,8 @@ On an `input` element with a `type` [attribute value][] of `hidden`, the autocom ### Bibliography -- [Understanding Success Criterion 1.3.5: Identify Input Purpose](https://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html) -- [Definition: programmatically determined (programmatically determinable)](https://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable) +- [Understanding Success Criterion 1.3.5: Identify Input Purpose](https://www.w3.org/WAI/WCAG22/Understanding/identify-input-purpose.html) +- [Definition: programmatically determined (programmatically determinable)](https://www.w3.org/TR/WCAG22/#dfn-programmatically-determinable) - [Autofill](https://html.spec.whatwg.org/#autofill) ## Test Cases @@ -309,7 +309,7 @@ This `autocomplete` attribute is inapplicable because it has the `off` value. This `input` element has a [fixed value](#73f2c2:fixed-value) due to its `type` [attribute value][] of `submit`. `autocomplete` does not apply to Submit buttons. ```html - + ``` #### Inapplicable Example 9 @@ -317,7 +317,7 @@ This `input` element has a [fixed value](#73f2c2:fixed-value) due to its `type` This `input` element is [hidden](#73f2c2:hidden) because of its `type` [attribute value][] of `hidden` (following standard [User Agent style sheet recommendations](https://html.spec.whatwg.org/multipage/rendering.html#hidden-elements). Knowing the transaction amount may still be used in other fields, e.g. to suggest a card with sufficient balance; this is not tested by this rule. ```html - + ``` [ascii whitespace]: https://infra.spec.whatwg.org/#ascii-whitespace 'HTML ASCII whitespace 2020/08/12' @@ -328,11 +328,11 @@ This `input` element is [hidden](#73f2c2:hidden) because of its `type` [attribut [disabled element]: #disabled-element 'Definition of Disabled Element' [html specification for autofill detail tokens]: https://html.spec.whatwg.org/#autofill-detail-tokens 'HTML Autofill Detail, 2020/08/12' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the accessibility tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' -[sc135]: https://www.w3.org/TR/WCAG21/#identify-input-purpose 'WCAG 2.1 success criterion 1.3.5 Identify Input Purpose' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[sc135]: https://www.w3.org/TR/WCAG22/#identify-input-purpose 'WCAG 2.2 success criterion 1.3.5 Identify Input Purpose' [semantic role]: #semantic-role 'Definition of Semantic Role' [sequential focus navigation]: https://html.spec.whatwg.org/#sequential-focus-navigation 'HTML sequential focus navigation, 2020/08/12' [space separated]: https://html.spec.whatwg.org/#set-of-space-separated-tokens 'HTML Set of space separated tokens 2020/08/12' [visible]: #visible 'Definition of Visible' -[widget role]: https://www.w3.org/TR/wai-aria-1.1/#widget_roles 'WAI-ARIA widget roles' +[widget role]: https://www.w3.org/TR/wai-aria-1.2/#widget_roles 'WAI-ARIA widget roles' [html]: #namespaced-element diff --git a/_rules/block-collapsible-3e12e1.md b/_rules/block-collapsible-3e12e1.md index 4929a593bf4..54d169595c5 100755 --- a/_rules/block-collapsible-3e12e1.md +++ b/_rules/block-collapsible-3e12e1.md @@ -300,6 +300,6 @@ This [document][] is not an [HTML web page][]. [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [instrument]: #instrument-to-achieve-an-objective 'Definition of Instrument to Achieve an Objective' [non-repeated content after repeated content]: #non-repeated-content 'Definition of Non-Repeated Content after Repeated Content' -[sc241]: https://www.w3.org/TR/WCAG21/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' -[tech scr28]: https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR28 'Technique SCR28: Using an Expandable and Collapsible Menu to Bypass Block of Content' +[sc241]: https://www.w3.org/TR/WCAG22/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' +[tech scr28]: https://www.w3.org/WAI/WCAG22/Techniques/client-side-script/SCR28 'Technique SCR28: Using an Expandable and Collapsible Menu to Bypass Block of Content' [visible]: #visible 'Definition of Visible' diff --git a/_rules/button-non-empty-accessible-name-97a4e1.md b/_rules/button-non-empty-accessible-name-97a4e1.md index 06637ff65da..253722c4477 100755 --- a/_rules/button-non-empty-accessible-name-97a4e1.md +++ b/_rules/button-non-empty-accessible-name-97a4e1.md @@ -32,7 +32,7 @@ Each target element has an [accessible name][] that is not empty (`""`). ## Assumptions -- The rule assumes that all buttons are [user interface components as defined by WCAG 2](https://www.w3.org/TR/WCAG21/#dfn-user-interface-components). +- The rule assumes that all buttons are [user interface components as defined by WCAG 2](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components). ## Accessibility Support @@ -42,7 +42,7 @@ Each target element has an [accessible name][] that is not empty (`""`). ## Background -This rule considers an exception for "image buttons" (i.e., `input` elements with a `type` [attribute value] of `image`). Image buttons failing this rule would fail [Success Criterion 4.1.2](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) and [Success Criterion 1.1.1](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content) which is not part of the accessibility requirements for this rule. +This rule considers an exception for "image buttons" (i.e., `input` elements with a `type` [attribute value] of `image`). Image buttons failing this rule would fail [Success Criterion 4.1.2](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) and [Success Criterion 1.1.1](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content) which is not part of the accessibility requirements for this rule. ### Related rules @@ -51,9 +51,9 @@ This rule considers an exception for "image buttons" (i.e., `input` elements wit ### Bibliography - [HTML Accessibility API Mappings 1.0 (working draft), 5.2 `input type="button"`, `input type="submit"` and `input type="reset"`](https://www.w3.org/TR/html-aam/#input-type-button-input-type-submit-and-input-type-reset) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) -- [ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA14) -- [ARIA16: Using aria-labelledby to provide a name for user interface controls](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA16) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14) +- [ARIA16: Using aria-labelledby to provide a name for user interface controls](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA16) ## Test Cases @@ -183,7 +183,7 @@ This `button` element has an [explicit role][] of `none`. However, it is [focusa #### Inapplicable Example 1 -This `input` element has a `type` attribute set to `image`. These images are tested in a separate rule which also tests [success criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG21/#non-text-content). +This `input` element has a `type` attribute set to `image`. These images are tested in a separate rule which also tests [success criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG22/#non-text-content). ```html @@ -199,7 +199,7 @@ This `button` element does not need an [accessible name][] because it is not inc #### Inapplicable Example 3 -This `button` element has a `link` role. Links are tested in a separate rule which also tests [success criterion 2.4.4 Link Purpose (In Context)](https://www.w3.org/TR/WCAG21/#link-purpose-in-context). +This `button` element has a `link` role. Links are tested in a separate rule which also tests [success criterion 2.4.4 Link Purpose (In Context)](https://www.w3.org/TR/WCAG22/#link-purpose-in-context). ```html @@ -227,5 +227,5 @@ This `button` element has an [explicit role][] of `none`; it is not [focusable][ [focusable]: #focusable 'Definition of focusable' [html aam input button]: https://www.w3.org/TR/html-aam-1.0/#input-type-button-input-type-submit-and-input-type-reset 'HTML Accessibility API Mapping, reset and submit buttons' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [semantic role]: #semantic-role 'Definition of Semantic Role' diff --git a/_rules/bypass-blocks-cf77f2.md b/_rules/bypass-blocks-cf77f2.md index 823691b0228..1375bc09411 100755 --- a/_rules/bypass-blocks-cf77f2.md +++ b/_rules/bypass-blocks-cf77f2.md @@ -67,7 +67,7 @@ For each test target, the outcome of at least one of the following rules is pass ## Assumptions - This rule assumes that the mean to bypass blocks is included in the content of the [HTML web page][]. For example, server-side scripting, or a global "settings" page, can provide a functionality similar to [_Block of repeated content is collapsible_][block collapsible] by serving a modified version of the page; in which case this rule would fail but [Success Criterion 2.4.1 Bypass blocks][sc241] could nonetheless be satisfied. -- This rule assumes that `frame` and `frameset` elements are not used, given that they are deprecated in HTML5. They can be used to organize content as per [H70: Using frame elements to group blocks of repeated material](https://www.w3.org/WAI/WCAG21/Techniques/html/H70) and [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG21/Techniques/html/H64), in that case, this rule would fail but [Success Criterion 2.4.1 Bypass blocks][sc241] could nonetheless be satisfied. +- This rule assumes that `frame` and `frameset` elements are not used, given that they are deprecated in HTML5. They can be used to organize content as per [H70: Using frame elements to group blocks of repeated material](https://www.w3.org/WAI/WCAG22/Techniques/html/H70) and [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H64), in that case, this rule would fail but [Success Criterion 2.4.1 Bypass blocks][sc241] could nonetheless be satisfied. - This rule assumes that completely removing [blocks of repeated content][block of repeated content] is sufficient to pass [Success Criterion 2.4.1 Bypass blocks][sc241]. However, providing an [instrument][] to remove them without providing one to show them again is likely going to create other unrelated issues. - This rule assumes that repeated content that is at the end of the page (and not followed any non-repeated content) can be bypassed by means provided by user agents (such as pressing the "End" key to scroll to the bottom of the page). Therefore, they do not need any other way of being bypassed and are ignored by this rule. If there isn't a way to bypass them, this rule may pass while [Success Criterion 2.4.1 Bypass blocks][sc241] is not satisfied. - This rule assumes that the language of each test target can be correctly determined (either programmatically or by analyzing the content), and sufficiently understood. @@ -76,7 +76,7 @@ For each test target, the outcome of at least one of the following rules is pass Techniques and solutions that identify blocks of content are sufficient ways of passing [Success Criterion 2.4.1 Bypass blocks][sc241]. They are, however, only beneficial for users who have ways of navigating with this information. For example, adding headings to a document will only help users who can "jump" from heading to heading (such a possibility can be provided by browsers, browsers plugins, screen readers, or other assistive technologies). Techniques and solutions based on links will benefit all users (for example, sighted keyboard users with no other assistive technology) and are therefore recommended. -If the [instruments][instrument] used to pass some of the atomic rules are not keyboard accessible, or not [included in the accessibility tree][], passing this rule can still leave many users without a way to bypass blocks of repeated content. WCAG's definition of [mechanism][] has a note saying that it "needs to meet all success criteria for the conformance level claimed". This includes [Success Criterion 2.1.1 Keyboard](https://www.w3.org/TR/WCAG21/#keyboard-accessible) and [Success Criterion 4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG21/#name-role-value) which are both at level A. +If the [instruments][instrument] used to pass some of the atomic rules are not keyboard accessible, or not [included in the accessibility tree][], passing this rule can still leave many users without a way to bypass blocks of repeated content. WCAG's definition of [mechanism][] has a note saying that it "needs to meet all success criteria for the conformance level claimed". This includes [Success Criterion 2.1.1 Keyboard](https://www.w3.org/TR/WCAG22/#keyboard-accessible) and [Success Criterion 4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG22/#name-role-value) which are both at level A. This rule only checks if there is a way to bypass at least one section of repeated content. On pages with several interleaved repeated and non-repeated content, this is not sufficient to satisfy [Success Criterion 2.4.1 Bypass blocks][sc241]. Checking for more sections to bypass was considered but rejected due to both the added complexity it would create, and the risk of failing on pages that might be correct. @@ -517,14 +517,14 @@ This [document][] is not an [HTML web page][]. [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [instrument]: #instrument-to-achieve-an-objective 'Definition of Instrument to Achieve an Objective' [just before]: #just-before 'Definition of Just Before' -[mechanism]: https://www.w3.org/TR/WCAG21/#dfn-mechanism 'WCAG definition of Mechanism' +[mechanism]: https://www.w3.org/TR/WCAG22/#dfn-mechanism 'WCAG definition of Mechanism' [non-repeated content after repeated content]: #non-repeated-content 'Definition of Non-Repeated Content after repeated content' [perceivable content]: #perceivable-content 'Definition of Perceivable Content' -[sc241]: https://www.w3.org/TR/WCAG21/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' -[tech aria11]: https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA11 'Technique ARIA11: Using ARIA Landmarks to Identify Regions of a Page' -[tech g1]: https://www.w3.org/WAI/WCAG21/Techniques/general/G1 'Technique G1: Adding a Link at the Top of each Page that Goes Directly to the Main Content Area' -[tech g123]: (https://www.w3.org/WAI/WCAG21/Techniques/general/G123) 'Technique G123: Adding a Link at the Beginning of a Block of Repeated Content to Go to the End of the Block' -[tech g124]: https://www.w3.org/WAI/WCAG21/Techniques/general/G124 'Technique G124: Adding Links at the Top of the Page to each Area of the Content' -[tech h69]: https://www.w3.org/WAI/WCAG21/Techniques/html/H69 'Technique H69: Providing Heading Elements at the Beginning of each Section of Content' -[tech scr28]: https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR28 'Technique SCR28: Using an Expandable and Collapsible Menu to Bypass Block of Content' -[usc241]: https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html 'Understanding Success Criterion 2.4.1: Bypass Blocks' +[sc241]: https://www.w3.org/TR/WCAG22/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' +[tech aria11]: https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA11 'Technique ARIA11: Using ARIA Landmarks to Identify Regions of a Page' +[tech g1]: https://www.w3.org/WAI/WCAG22/Techniques/general/G1 'Technique G1: Adding a Link at the Top of each Page that Goes Directly to the Main Content Area' +[tech g123]: (https://www.w3.org/WAI/WCAG22/Techniques/general/G123) 'Technique G123: Adding a Link at the Beginning of a Block of Repeated Content to Go to the End of the Block' +[tech g124]: https://www.w3.org/WAI/WCAG22/Techniques/general/G124 'Technique G124: Adding Links at the Top of the Page to each Area of the Content' +[tech h69]: https://www.w3.org/WAI/WCAG22/Techniques/html/H69 'Technique H69: Providing Heading Elements at the Beginning of each Section of Content' +[tech scr28]: https://www.w3.org/WAI/WCAG22/Techniques/client-side-script/SCR28 'Technique SCR28: Using an Expandable and Collapsible Menu to Bypass Block of Content' +[usc241]: https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html 'Understanding Success Criterion 2.4.1: Bypass Blocks' diff --git a/_rules/css-restrict-orientation-b33eff.md b/_rules/css-restrict-orientation-b33eff.md index bbba0af4025..f1e08b1707b 100755 --- a/_rules/css-restrict-orientation-b33eff.md +++ b/_rules/css-restrict-orientation-b33eff.md @@ -29,11 +29,11 @@ This rule applies to any [HTML element][] that is [visible](#visible) and has on - the CSS [rotate](https://www.w3.org/TR/css-transforms-2/#individual-transforms) property; or - the CSS [transform](https://www.w3.org/TR/css-transforms/#propdef-transform) property with any of the below [transformation functions](https://www.w3.org/TR/css-transforms/#transform-functions): - - [rotate](https://www.w3.org/TR/css-transforms/#funcdef-transform-rotate) - - [rotate3d](https://www.w3.org/TR/css-transforms-2/#funcdef-rotate3d) - - [rotateZ](https://www.w3.org/TR/css-transforms-2/#funcdef-rotatez) - - [matrix](https://www.w3.org/TR/css-transforms/#funcdef-transform-matrix) - - [matrix3d](https://www.w3.org/TR/css-transforms-2/#funcdef-matrix3d) + - [rotate](https://www.w3.org/TR/css-transforms/#funcdef-transform-rotate) + - [rotate3d](https://www.w3.org/TR/css-transforms-2/#funcdef-rotate3d) + - [rotateZ](https://www.w3.org/TR/css-transforms-2/#funcdef-rotatez) + - [matrix](https://www.w3.org/TR/css-transforms/#funcdef-transform-matrix) + - [matrix3d](https://www.w3.org/TR/css-transforms-2/#funcdef-matrix3d) **Note:** These specific [transformation functions](https://www.w3.org/TR/css-transforms/#transform-functions) are of interest to this rule as they have the potential to affect the [rotation](https://www.w3.org/TR/css-transforms-2/#Rotate3dDefined) of a given element. @@ -49,7 +49,7 @@ The target element is neither rotated clockwise nor counter clockwise around the This rule does not consider and may produce incorrect results for: -- Elements for which a particular display orientation is [essential](https://www.w3.org/TR/WCAG21/#dfn-essential). +- Elements for which a particular display orientation is [essential](https://www.w3.org/TR/WCAG22/#dfn-essential). - The existence of any control on the page that can change the orientation on demand. - Scripts are not used to adjust the CSS orientation lock. @@ -61,7 +61,7 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.3.4: Orientation](https://www.w3.org/WAI/WCAG21/Understanding/orientation.html) +- [Understanding Success Criterion 1.3.4: Orientation](https://www.w3.org/WAI/WCAG22/Understanding/orientation.html) - [CSS Transforms Module Level 1](https://www.w3.org/TR/css-transforms/#funcdef-transform-matrix) - [CSS Transforms Module Level 2](https://www.w3.org/TR/css-transforms-2) - [CSS3 Media Queries](https://www.w3.org/TR/css3-mediaqueries/) diff --git a/_rules/device-motion-disabled-c249d5.md b/_rules/device-motion-disabled-c249d5.md index a5596e441f5..6fd8e663e79 100755 --- a/_rules/device-motion-disabled-c249d5.md +++ b/_rules/device-motion-disabled-c249d5.md @@ -58,7 +58,7 @@ The [instruments][instrument] used to pass this rule (if any), must meet all lev ### Bibliography - [Understanding Success Criterion 2.5.4: Motion Actuation][sc2.5.4] -- [G213: Provide conventional controls and an application setting for motion activated input](https://www.w3.org/WAI/WCAG21/Techniques/general/G213.html) +- [G213: Provide conventional controls and an application setting for motion activated input](https://www.w3.org/WAI/WCAG22/Techniques/general/G213.html) - [DeviceOrientation Event Specification](https://www.w3.org/TR/orientation-event/) ## Test Cases @@ -212,12 +212,12 @@ This [HTML document][] is not operable by device motion.

ACT-Rules

``` -[accessibility supported]: https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation#dfn-accessibility-supported +[accessibility supported]: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation#dfn-accessibility-supported [blocked event]: #blocked-event 'Definition of blocked event' [changes in content]: #changes-in-content 'Definition of changes in content' [device motion]: https://www.w3.org/TR/orientation-event/#devicemotion 'Definition of device motion event' [device orientation]: https://www.w3.org/TR/orientation-event/#deviceorientation 'Definition of device orientation event' -[essential]: https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html#dfn-essential +[essential]: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation.html#dfn-essential [event]: https://dom.spec.whatwg.org/#concept-event 'Definition of event' [event firing]: https://dom.spec.whatwg.org/#concept-event-fire [event listener]: https://dom.spec.whatwg.org/#concept-event-listener @@ -225,7 +225,7 @@ This [HTML document][] is not operable by device motion. [firing]: https://dom.spec.whatwg.org/#concept-event-fire 'Definition of event firing' [html document]: https://dom.spec.whatwg.org/#concept-document [instrument]: #instrument-to-achieve-an-objective 'Definition of Instrument to Achieve an Objective' -[sc2.5.4]: https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html +[sc2.5.4]: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation.html [set of clearly labeled instruments]: #set-of-clearly-labeled-instruments 'Definition of set of clearly labeled instruments' [web page]: #web-page-html 'Definition of web page' [window object]: https://html.spec.whatwg.org/multipage/window-object.html#dom-window diff --git a/_rules/device-motion-user-interface-7677a9.md b/_rules/device-motion-user-interface-7677a9.md index 421e29c377e..e3bea3a8deb 100755 --- a/_rules/device-motion-user-interface-7677a9.md +++ b/_rules/device-motion-user-interface-7677a9.md @@ -55,7 +55,7 @@ The [instruments][instrument] used to pass this rule (if any), must meet all lev ### Bibliography - [Understanding Success Criterion 2.5.4: Motion Actuation][sc2.5.4] -- [G213: Provide conventional controls and an application setting for motion activated input](https://www.w3.org/WAI/WCAG21/Techniques/general/G213.html) +- [G213: Provide conventional controls and an application setting for motion activated input](https://www.w3.org/WAI/WCAG22/Techniques/general/G213.html) - [DeviceOrientation Event Specification](https://www.w3.org/TR/orientation-event/) ## Test Cases @@ -272,18 +272,18 @@ This [HTML document][] is not operable by device motion.

ACT-Rules

``` -[accessibility supported]: https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation#dfn-accessibility-supported +[accessibility supported]: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation#dfn-accessibility-supported [changes in content]: #changes-in-content 'Definition of changes in content' [clearly labeled location]: #clearly-labeled-location 'Definition of clearly labeled location' [device motion]: https://www.w3.org/TR/orientation-event/#devicemotion 'Definition of device motion event' [device orientation]: https://www.w3.org/TR/orientation-event/#deviceorientation 'Definition of device orientation event' -[essential]: https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html#dfn-essential +[essential]: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation.html#dfn-essential [event]: https://dom.spec.whatwg.org/#concept-event 'Definition of event' [event listener]: https://dom.spec.whatwg.org/#concept-event-listener [event listener list]: https://dom.spec.whatwg.org/#eventtarget-event-listener-list [firing]: https://dom.spec.whatwg.org/#concept-event-fire 'Definition of event firing' [html document]: https://dom.spec.whatwg.org/#concept-document [instrument]: #instrument-to-achieve-an-objective 'Definition of instrument to achieve an objective' -[sc2.5.4]: https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html +[sc2.5.4]: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation.html [web page]: #web-page-html 'Definition of web page' [window object]: https://html.spec.whatwg.org/multipage/window-object.html#dom-window diff --git a/_rules/document-has-headings-for-non-repeated-content-047fe0.md b/_rules/document-has-headings-for-non-repeated-content-047fe0.md index 326cc98da2b..32ccdeea247 100755 --- a/_rules/document-has-headings-for-non-repeated-content-047fe0.md +++ b/_rules/document-has-headings-for-non-repeated-content-047fe0.md @@ -39,24 +39,24 @@ In each test target, either there is no [non-repeated content after repeated con ## Assumptions -- This rule assumes that headings used to pass [Technique H69: Providing heading elements at the beginning of each section of content][tech h69] have to be [included in the accessibility tree][] in order to be beneficial to users of assistive technologies. -- This rule assumes that the first non-repeated content is starting a new section of content. If this is not the case, it is possible to fail the rule while still passing [Technique H69: Providing heading elements at the beginning of each section of content][tech h69]. +- This rule assumes that headings used to pass [Technique H69: Providing heading elements at the beginning of each section of content][h69] have to be [included in the accessibility tree][] in order to be beneficial to users of assistive technologies. +- This rule assumes that the first non-repeated content is starting a new section of content. If this is not the case, it is possible to fail the rule while still passing [Technique H69: Providing heading elements at the beginning of each section of content][h69]. ## Accessibility Support - Having a heading for the non-repeated content is sufficient to pass [Success Criterion 2.4.1 Bypass blocks][sc241]. However, if headings are used for that goal, they will only benefit users who can actually navigate from heading to heading (such a functionality can be provided by browsers, browsers plugins, screen readers or other assistive technologies). Users without any possibility for headings navigation will be left without way of bypassing blocks of repeated content and will still experience accessibility issues. Therefore, it is recommended to provide other ways of bypassing blocks. -- When headings are rendered without sufficient visual cues, they are not perceived as headings by sighted users. In this case, passing this rule might still fail [Technique H69: Providing heading elements at the beginning of each section of content][tech h69] and [Success Criterion 2.4.1 Bypass blocks][sc241]. Additionally, this is likely a failure of [Success Criterion 1.3.1 Info and Relationships][sc131]. +- When headings are rendered without sufficient visual cues, they are not perceived as headings by sighted users. In this case, passing this rule might still fail [Technique H69: Providing heading elements at the beginning of each section of content][h69] and [Success Criterion 2.4.1 Bypass blocks][sc241]. Additionally, this is likely a failure of [Success Criterion 1.3.1 Info and Relationships][sc131]. ## Background -The intention of this rule is that the heading is at (or near) the start of the main area of content of a document. However, defining the main area of content in a non-ambiguous way is not really doable. Therefore, the rule takes a more lenient position and only requires the heading to be some non-repeated content. Additional conditions on this heading were considered and rejected when writing the rule since it might be acceptable, for example, to have non-repeated content such as breadcrumb before any heading. Therefore, it is possible to pass this rule but still fail [H69: Providing heading elements at the beginning of each section of content][tech h69] and violate [Success Criterion 2.4.1 Bypass blocks][sc241]. +The intention of this rule is that the heading is at (or near) the start of the main area of content of a document. However, defining the main area of content in a non-ambiguous way is not really doable. Therefore, the rule takes a more lenient position and only requires the heading to be some non-repeated content. Additional conditions on this heading were considered and rejected when writing the rule since it might be acceptable, for example, to have non-repeated content such as breadcrumb before any heading. Therefore, it is possible to pass this rule but still fail [H69: Providing heading elements at the beginning of each section of content][h69] and violate [Success Criterion 2.4.1 Bypass blocks][sc241]. -Neither this rule, nor technique [H69: Providing heading elements at the beginning of each section of content][tech h69], expects the heading to accurately describe its corresponding section. However, having non descriptive headings fails [Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/TR/WCAG21/#headings-and-labels) +Neither this rule, nor technique [H69: Providing heading elements at the beginning of each section of content][h69], expects the heading to accurately describe its corresponding section. However, having non descriptive headings fails [Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/TR/WCAG22/#headings-and-labels) ### Bibliography - [Understanding Success Criterion 2.4.1: Bypass Blocks][usc241] -- [H69: Providing heading elements at the beginning of each section of content][tech h69] +- [H69: Providing heading elements at the beginning of each section of content][h69] - [CSS Scoping (work in progress)](https://drafts.csswg.org/css-scoping/) ## Test Cases @@ -461,8 +461,8 @@ This [document][] is not an [HTML web page][]. [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [non-repeated content after repeated content]: #non-repeated-content 'Definition of Non-Repeated Content after Repeated Content' [semantic]: #semantic-role 'Definition of Semantic Role' -[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationships' -[sc241]: https://www.w3.org/TR/WCAG21/#bypass-blocks 'Success Criterion 2.4.1: Bypass Blocks' -[tech h69]: https://www.w3.org/WAI/WCAG21/Techniques/html/H69 'Technique H69: Providing Heading Elements at the Beginning of each Section of Content' -[usc241]: https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html 'Understanding Success Criterion 2.4.1: Bypass Blocks' +[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationships' +[sc241]: https://www.w3.org/TR/WCAG22/#bypass-blocks 'Success Criterion 2.4.1: Bypass Blocks' +[h69]: https://www.w3.org/WAI/WCAG22/Techniques/html/H69 'Technique H69: Providing Heading Elements at the Beginning of each Section of Content' +[usc241]: https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html 'Understanding Success Criterion 2.4.1: Bypass Blocks' [visible]: #visible 'Definition of Visible' diff --git a/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md b/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md index fb16874e69d..40e7d86d605 100755 --- a/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md +++ b/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md @@ -411,8 +411,8 @@ This [document][] is not an [HTML web page][]. [navigation landmark]: https://www.w3.org/TR/wai-aria-practices-1.1/#aria_lh_navigation 'WAI-ARIA authoring practices, Navigation Landmark' [non-repeated content after repeated content]: #non-repeated-content 'Definition of Non-Repeated Content after Repeated Content' [perceivable content]: #perceivable-content 'Definition of Perceivable Content' -[sc241]: https://www.w3.org/TR/WCAG21/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' -[tech g1]: https://www.w3.org/WAI/WCAG21/Techniques/general/G1 'Technique G1: Adding a Link at the Top of each Page that Goes Directly to the Main Content Area' -[tech g123]: https://www.w3.org/WAI/WCAG21/Techniques/general/G123 'Technique G123: Adding a Link at the Beginning of a Block of Repeated Content to Go to the End of the Block' -[tech g124]: https://www.w3.org/WAI/WCAG21/Techniques/general/G124 'Technique G124: Adding Links at the Top of the Page to each Area of the Content' +[sc241]: https://www.w3.org/TR/WCAG22/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' +[tech g1]: https://www.w3.org/WAI/WCAG22/Techniques/general/G1 'Technique G1: Adding a Link at the Top of each Page that Goes Directly to the Main Content Area' +[tech g123]: https://www.w3.org/WAI/WCAG22/Techniques/general/G123 'Technique G123: Adding a Link at the Beginning of a Block of Repeated Content to Go to the End of the Block' +[tech g124]: https://www.w3.org/WAI/WCAG22/Techniques/general/G124 'Technique G124: Adding Links at the Top of the Page to each Area of the Content' [visible]: #visible 'Definition of Visible' diff --git a/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md b/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md index 81405f07008..51f64e77d02 100755 --- a/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md +++ b/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md @@ -51,7 +51,7 @@ Most of the time, this rule passes by enclosing the primary content of the page - [Technique ARIA11: Using ARIA landmarks to identify regions of a page][tech aria11] - [ARIA Landmarks Example](https://www.w3.org/TR/wai-aria-practices/examples/landmarks/index.html) - [CSS scoping (work in progress)](https://drafts.csswg.org/css-scoping/) -- [The `main` role](https://www.w3.org/TR/wai-aria-1.1/#main) +- [The `main` role](https://www.w3.org/TR/wai-aria-1.2/#main) ## Test Cases @@ -267,11 +267,11 @@ This [document][] is not an [HTML web page][]. [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [inclusive descendant]: https://dom.spec.whatwg.org/#concept-tree-inclusive-descendant 'DOM definition of Inclusive Descendant' [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' -[landmark]: https://www.w3.org/TR/wai-aria-1.1/#landmark_roles 'List of Landmark Roles' +[landmark]: https://www.w3.org/TR/wai-aria-1.2/#landmark_roles 'List of Landmark Roles' [non-repeated content after repeated content]: #non-repeated-content 'Definition of Non-Repeated Content after Repeated Content' [perceivable content]: #perceivable-content 'Definition of Perceivable Content' -[sc241]: https://www.w3.org/TR/WCAG21/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' +[sc241]: https://www.w3.org/TR/WCAG22/#bypass-blocks 'Success Criterion 2.4.1 Bypass Blocks' [semantic role]: #semantic-role 'Definition of Semantic Role' -[tech aria11]: https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA11 'Technique ARIA11: Using ARIA Landmarks to Identify Regions of a Page' +[tech aria11]: https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA11 'Technique ARIA11: Using ARIA Landmarks to Identify Regions of a Page' [tree order]: https://dom.spec.whatwg.org/#concept-tree-order 'DOM specification of Tree Order' [visible]: #visible 'Definition of Visible' diff --git a/_rules/element-lang-matches-default-language-off6ek.md b/_rules/element-lang-matches-default-language-off6ek.md index b1907a270f9..193a6717220 100644 --- a/_rules/element-lang-matches-default-language-off6ek.md +++ b/_rules/element-lang-matches-default-language-off6ek.md @@ -58,7 +58,7 @@ There are no accessibility support issues known. ## Background -This rule checks that, if a `lang` attribute is used, its value is correct with respect to the content. This rule does not check whether a `lang` attribute should have been used or not. Especially, this rule does not check when `lang` attributes are missing. This must be tested separately and it is therefore possible to pass this rule without satisfying [Success Criterion 3.1.2 Language of Parts](https://www.w3.org/TR/WCAG21/#language-of-parts). +This rule checks that, if a `lang` attribute is used, its value is correct with respect to the content. This rule does not check whether a `lang` attribute should have been used or not. Especially, this rule does not check when `lang` attributes are missing. This must be tested separately and it is therefore possible to pass this rule without satisfying [Success Criterion 3.1.2 Language of Parts](https://www.w3.org/TR/WCAG22/#language-of-parts). ### Related rules @@ -67,11 +67,11 @@ This rule checks that, if a `lang` attribute is used, its value is correct with ### Bibliography - [Understanding Success Criterion 3.1.2: Language of Page][usc312] -- [H58: Using language attributes to identify changes in the human language](https://www.w3.org/WAI/WCAG21/Techniques/html/H58) +- [H58: Using language attributes to identify changes in the human language](https://www.w3.org/WAI/WCAG22/Techniques/html/H58) - [RFC 5646: Tags for Identifying Languages](https://www.rfc-editor.org/rfc/rfc5646.html) - [The `lang` and `xml:lang` attributes](https://html.spec.whatwg.org/multipage/dom.html#the-lang-and-xml:lang-attributes) -In all examples, the `html` element has itself a `lang` attribute in order to make sure that the examples satisfy [Success Criterion 3.1.1 Language of Page](https://www.w3.org/TR/WCAG21/#language-of-page). These `html` elements are, however, never applicable because they are not descendants of a `body` element, and the example descriptions do not mention them further. +In all examples, the `html` element has itself a `lang` attribute in order to make sure that the examples satisfy [Success Criterion 3.1.1 Language of Page](https://www.w3.org/TR/WCAG22/#language-of-page). These `html` elements are, however, never applicable because they are not descendants of a `body` element, and the example descriptions do not mention them further. ## Test Cases @@ -313,7 +313,7 @@ The [text inheriting its programmatic language][] from this `div` element is onl [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'CSS Scoping definition of Flat tree, working draft' [grandfathered tags]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.8 [html element]: #namespaced-element -[human language]: https://www.w3.org/TR/WCAG21/#dfn-human-language-s 'WCAG definition of Human Language' +[human language]: https://www.w3.org/TR/WCAG22/#dfn-human-language-s 'WCAG definition of Human Language' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [inclusive descendant]: https://dom.spec.whatwg.org/#concept-tree-inclusive-descendant 'DOM definition of Inclusive Descendant' [iso 639.2]: https://www.loc.gov/standards/iso639-2/php/code_list.php 'ISO 639.2: Codes for the Representation of Names of Languages' @@ -321,8 +321,8 @@ The [text inheriting its programmatic language][] from this `div` element is onl [primary language]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.1 'Definition of primary language subtag' [rfc 5646]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.1 [text inheriting its programmatic language]: #text-inheriting-language:text 'Definition of Text Inheriting its Programmatic Language from an Element' -[sc312]: https://www.w3.org/TR/WCAG21/#language-of-parts 'Success Criterion 3.1.2 Language of Parts' -[usc312]: https://www.w3.org/WAI/WCAG21/Understanding/language-of-parts.html 'Understanding Success Criterion 3.1.2: Language of Parts' +[sc312]: https://www.w3.org/TR/WCAG22/#language-of-parts 'Success Criterion 3.1.2 Language of Parts' +[usc312]: https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts.html 'Understanding Success Criterion 3.1.2: Language of Parts' [known primary language tag]: #known-primary-language-tag 'Definition of Known Primary Language Tag' [visible]: #visible 'Definition of Visible' [whitespace]: #whitespace 'Definition of whitespace' diff --git a/_rules/element-lang-valid-de46e4.md b/_rules/element-lang-valid-de46e4.md index 58932e20541..18baddbac22 100755 --- a/_rules/element-lang-valid-de46e4.md +++ b/_rules/element-lang-valid-de46e4.md @@ -58,9 +58,9 @@ There are differences in how assistive technologies handle unknown and invalid l ### Bibliography - [CSS Scoping Module Level 1 (editor's draft)](https://drafts.csswg.org/css-scoping/) -- [H58: Using language attributes to identify changes in the human language](https://www.w3.org/WAI/WCAG21/Techniques/html/H58) +- [H58: Using language attributes to identify changes in the human language](https://www.w3.org/WAI/WCAG22/Techniques/html/H58) - [RFC 5646: Tags for Identifying Languages](https://www.rfc-editor.org/rfc/rfc5646.html) -- [Understanding Success Criterion 3.1.2: Language of Parts](https://www.w3.org/WAI/WCAG21/Understanding/language-of-parts) +- [Understanding Success Criterion 3.1.2: Language of Parts](https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts) ## Test Cases @@ -345,14 +345,14 @@ The [text inheriting its programmatic language][] from this `div` element is onl [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree [grandfathered tags]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.8 [html element]: #namespaced-element -[human language]: https://www.w3.org/TR/WCAG21/#dfn-human-language-s 'WCAG definition of Human Language' +[human language]: https://www.w3.org/TR/WCAG22/#dfn-human-language-s 'WCAG definition of Human Language' [included in the accessibility tree]: #included-in-the-accessibility-tree [inclusive descendant]: https://dom.spec.whatwg.org/#concept-tree-inclusive-descendant 'DOM definition of Inclusive Descendant' [iso 639.2]: https://www.loc.gov/standards/iso639-2/php/code_list.php 'ISO 639.2: Codes for the Representation of Names of Languages' [language subtag registry]: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry [node document]: https://dom.spec.whatwg.org/#concept-node-document [rfc 5646]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.1 -[sc312]: https://www.w3.org/TR/WCAG21/#language-of-parts 'Success Criterion 3.1.2 Language of Parts' +[sc312]: https://www.w3.org/TR/WCAG22/#language-of-parts 'Success Criterion 3.1.2 Language of Parts' [text inheriting its programmatic language]: #text-inheriting-language 'Definition of Text Inheriting its Programmatic Language from an Element' [text node]: https://dom.spec.whatwg.org/#text [known primary language tag]: #known-primary-language-tag diff --git a/_rules/element-marked-decorative-is-not-exposed-46ca7f.md b/_rules/element-marked-decorative-is-not-exposed-46ca7f.md index a2ec0532901..3153f81e41b 100755 --- a/_rules/element-marked-decorative-is-not-exposed-46ca7f.md +++ b/_rules/element-marked-decorative-is-not-exposed-46ca7f.md @@ -140,13 +140,13 @@ This `img` element is not [marked as decorative][]. ``` -[decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG definition of Pure decoration' +[decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure decoration' [focusable]: #focusable 'Definition of Focusable' -[global aria attribute]: https://www.w3.org/TR/wai-aria-1.1/#global_states 'List of Global ARIA States and Properties' +[global aria attribute]: https://www.w3.org/TR/wai-aria-1.2/#global_states 'List of Global ARIA States and Properties' [implicit role]: #implicit-role 'Definition of Implicit Role' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [marked as decorative]: #marked-as-decorative 'Definition of Marked as decorative' -[non-text content]: https://www.w3.org/TR/WCAG21/#dfn-non-text-content 'WCAG definition of Non-text content' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' -[sc111]: https://www.w3.org/TR/WCAG21/#non-text-content 'Success Criterion 1.1.1: Non-text Content' +[non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content 'WCAG definition of Non-text content' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[sc111]: https://www.w3.org/TR/WCAG22/#non-text-content 'Success Criterion 1.1.1: Non-text Content' [semantic role]: #semantic-role 'Definition of Semantic Role' diff --git a/_rules/explicit-SVG-image-non-empty-accessible-name-7d6734.md b/_rules/explicit-SVG-image-non-empty-accessible-name-7d6734.md index 7a8cf9bb93a..b1be180463d 100755 --- a/_rules/explicit-SVG-image-non-empty-accessible-name-7d6734.md +++ b/_rules/explicit-SVG-image-non-empty-accessible-name-7d6734.md @@ -46,12 +46,12 @@ Until browser support for the [SVG Accessibility API Mappings][] is more consist ### Bibliography -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) - [SVG Accessibility API Mappings (working draft)][svg accessibility api mappings] - [WAI-ARIA Graphics Module](https://www.w3.org/TR/graphics-aria-1.0/) -- [ARIA4: Using a WAI-ARIA role to expose the role of a user interface component](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA4) -- [ARIA6: Using aria-label to provide labels for objects](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA6) -- [ARIA10: Using aria-labelledby to provide a text alternative for non-text content](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA10) +- [ARIA4: Using a WAI-ARIA role to expose the role of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA4) +- [ARIA6: Using aria-label to provide labels for objects](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA6) +- [ARIA10: Using aria-labelledby to provide a text alternative for non-text content](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA10) ## Test Cases diff --git a/_rules/focusable-no-keyboard-trap-80af7b.md b/_rules/focusable-no-keyboard-trap-80af7b.md index 796057af3d6..135bd432df4 100755 --- a/_rules/focusable-no-keyboard-trap-80af7b.md +++ b/_rules/focusable-no-keyboard-trap-80af7b.md @@ -58,9 +58,9 @@ This rule only requires navigation in one direction (either forward or backward) ### Bibliography -- [Understanding Success Criterion 2.1.2: No Keyboard Trap](https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html) -- [G21: Ensuring that users are not trapped in content](https://www.w3.org/WAI/WCAG21/Techniques/general/G21) -- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type](https://www.w3.org/WAI/WCAG21/Techniques/failures/F10) +- [Understanding Success Criterion 2.1.2: No Keyboard Trap](https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap.html) +- [G21: Ensuring that users are not trapped in content](https://www.w3.org/WAI/WCAG22/Techniques/general/G21) +- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type](https://www.w3.org/WAI/WCAG22/Techniques/failures/F10) ## Test Cases @@ -276,4 +276,4 @@ There is no [focusable][] element. [focusable]: #focusable 'Definition of focusable' [html or svg element]: #namespaced-element -[sc212]: https://www.w3.org/TR/WCAG21/#no-keyboard-trap 'Success Criterion 2.1.2 No Keyboard Trap' +[sc212]: https://www.w3.org/TR/WCAG22/#no-keyboard-trap 'Success Criterion 2.1.2 No Keyboard Trap' diff --git a/_rules/focusable-no-keyboard-trap-non-standard-nav-ebe86a.md b/_rules/focusable-no-keyboard-trap-non-standard-nav-ebe86a.md index b3674fe60a1..f457c14ab06 100755 --- a/_rules/focusable-no-keyboard-trap-non-standard-nav-ebe86a.md +++ b/_rules/focusable-no-keyboard-trap-non-standard-nav-ebe86a.md @@ -54,9 +54,9 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 2.1.2: No Keyboard Trap](https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html) -- [G21: Ensuring that users are not trapped in content](https://www.w3.org/WAI/WCAG21/Techniques/general/G21) -- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type](https://www.w3.org/WAI/WCAG21/Techniques/failures/F10) +- [Understanding Success Criterion 2.1.2: No Keyboard Trap](https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap.html) +- [G21: Ensuring that users are not trapped in content](https://www.w3.org/WAI/WCAG22/Techniques/general/G21) +- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type](https://www.w3.org/WAI/WCAG22/Techniques/failures/F10) ## Test Cases diff --git a/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md b/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md index 7b365684544..d48dba0605a 100755 --- a/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md +++ b/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md @@ -46,9 +46,9 @@ This rule only requires navigation in one direction (either forward or backward) ### Bibliography -- [Understanding Success Criterion 2.1.2: No Keyboard Trap](https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html) -- [G21: Ensuring that users are not trapped in content](https://www.w3.org/WAI/WCAG21/Techniques/general/G21) -- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type](https://www.w3.org/WAI/WCAG21/Techniques/failures/F10) +- [Understanding Success Criterion 2.1.2: No Keyboard Trap](https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap.html) +- [G21: Ensuring that users are not trapped in content](https://www.w3.org/WAI/WCAG22/Techniques/general/G21) +- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type](https://www.w3.org/WAI/WCAG22/Techniques/failures/F10) ## Test Cases @@ -154,4 +154,4 @@ There is no [focusable][] element. [focusable]: #focusable 'Definition of focusable' [html or svg element]: #namespaced-element -[sc212]: https://www.w3.org/TR/WCAG21/#no-keyboard-trap 'Success Criterion 2.1.2 No Keyboard Trap' +[sc212]: https://www.w3.org/TR/WCAG22/#no-keyboard-trap 'Success Criterion 2.1.2 No Keyboard Trap' diff --git a/_rules/form-field-label-descriptive-cc0f0a.md b/_rules/form-field-label-descriptive-cc0f0a.md index a4b39f5f5df..dfbbf37bd89 100755 --- a/_rules/form-field-label-descriptive-cc0f0a.md +++ b/_rules/form-field-label-descriptive-cc0f0a.md @@ -80,9 +80,9 @@ Having a [label][] which is not included in the [accessible name][] is a violati - [Accessible Rich Internet Applications (WAI-ARIA) 1.2][aria12] - [Understanding Success Criterion 2.4.6: Headings and Labels][usc246] - [Understanding Success Criterion 4.1.2: Name, Role and Value][usc412] -- [G131: Providing descriptive labels](https://www.w3.org/WAI/WCAG21/Techniques/general/G131) -- [H44: Using label elements to associate text labels with form controls](https://www.w3.org/WAI/WCAG21/Techniques/html/H44) -- [ARIA16: Using aria-labelledby to provide a name for user interface controls](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA16) +- [G131: Providing descriptive labels](https://www.w3.org/WAI/WCAG22/Techniques/general/G131) +- [H44: Using label elements to associate text labels with form controls](https://www.w3.org/WAI/WCAG22/Techniques/html/H44) +- [ARIA16: Using aria-labelledby to provide a name for user interface controls](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA16) ## Test Cases @@ -262,14 +262,14 @@ The `label` is a [visible][] [programmatic label][] of the `input` element. Howe [accessible name]: #accessible-name 'Definition of accessible name' [aria12]: https://www.w3.org/TR/wai-aria-1.2/ 'Accessible Rich Internet Applications 1.2' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[label]: https://www.w3.org/TR/WCAG21/#dfn-labels 'Definition of label' +[label]: https://www.w3.org/TR/WCAG22/#dfn-labels 'Definition of label' [presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [programmatic label]: #programmatic-label 'Definition of programmatic label' -[sc246]: https://www.w3.org/WAI/WCAG21/#headings-and-labels.html 'Success Criterion 2.4.6: Headings and Labels' -[sc253]: https://www.w3.org/WAI/WCAG21/label-in-name 'Success Criterion 2.5.3: Label in Name' -[sc412]: https://www.w3.org/WAI/WCAG21/#name-role-value 'Success Criterion 4.1.2: Name, Role and Value' +[sc246]: https://www.w3.org/WAI/WCAG22/#headings-and-labels.html 'Success Criterion 2.4.6: Headings and Labels' +[sc253]: https://www.w3.org/WAI/WCAG22/label-in-name 'Success Criterion 2.5.3: Label in Name' +[sc412]: https://www.w3.org/WAI/WCAG22/#name-role-value 'Success Criterion 4.1.2: Name, Role and Value' [semantic role]: #semantic-role 'Definition of semantic role' -[usc246]: https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html 'Understanding SC 2.4.6: Headings and Labels' -[usc412]: https://www.w3.org/WAI/WCAG21/Understanding/name-role-value 'Understanding SC 4.1.2: Name, Role and Value' +[usc246]: https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html 'Understanding SC 2.4.6: Headings and Labels' +[usc412]: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value 'Understanding SC 4.1.2: Name, Role and Value' [visible]: #visible 'Definition of visible' [visual context]: #visual-context 'Definition of visual context' diff --git a/_rules/form-field-non-empty-accessible-name-e086e5.md b/_rules/form-field-non-empty-accessible-name-e086e5.md index ec82787d959..d71625aff77 100755 --- a/_rules/form-field-non-empty-accessible-name-e086e5.md +++ b/_rules/form-field-non-empty-accessible-name-e086e5.md @@ -48,14 +48,14 @@ The list of roles in the applicability is derived by taking all the roles from [ This rule does not test other control-like roles such as `button` and `menuitem`, because these do not inherit from `input` or `select`. These should be tested separately. -This rule does not map to [3.3.2 Labels or Instructions](https://www.w3.org/TR/WCAG21/#labels-or-instructions) as there are sufficient techniques within 3.3.2 that don't need the elements to have an [accessible name][]. For example "[G131: Providing descriptive labels](https://www.w3.org/WAI/WCAG21/Techniques/general/G131)" **AND** "[G162: Positioning labels to maximize predictability of relationships](https://www.w3.org/WAI/WCAG21/Techniques/general/G162)" would be sufficient. +This rule does not map to [3.3.2 Labels or Instructions](https://www.w3.org/TR/WCAG22/#labels-or-instructions) as there are sufficient techniques within 3.3.2 that don't need the elements to have an [accessible name][]. For example "[G131: Providing descriptive labels](https://www.w3.org/WAI/WCAG22/Techniques/general/G131)" **AND** "[G162: Positioning labels to maximize predictability of relationships](https://www.w3.org/WAI/WCAG22/Techniques/general/G162)" would be sufficient. ### Bibliography -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) -- [H91: Using HTML form controls and links](https://www.w3.org/WAI/WCAG21/Techniques/html/H91) -- [H44: Using label elements to associate text labels with form controls](https://www.w3.org/WAI/WCAG21/Techniques/html/H44) -- [H65: Using the title attribute to identify form controls when the label element cannot be used](https://www.w3.org/WAI/WCAG21/Techniques/html/H65) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [H91: Using HTML form controls and links](https://www.w3.org/WAI/WCAG22/Techniques/html/H91) +- [H44: Using label elements to associate text labels with form controls](https://www.w3.org/WAI/WCAG22/Techniques/html/H44) +- [H65: Using the title attribute to identify form controls when the label element cannot be used](https://www.w3.org/WAI/WCAG22/Techniques/html/H65) ## Test Cases @@ -138,7 +138,8 @@ These `menuitemcheckbox` elements have an [accessible name][] because its aria-l ```html

Add one or more dip:

-
``` -[decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG definition of Pure decoration' +[decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure decoration' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' -[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships ' Success Criterion 1.3.1 Info and Relationships' -[sc246]: https://www.w3.org/TR/WCAG21/#headings-and-labels 'Success Criterion 2.4.6 Headings and Labels' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships ' Success Criterion 1.3.1 Info and Relationships' +[sc246]: https://www.w3.org/TR/WCAG22/#headings-and-labels 'Success Criterion 2.4.6 Headings and Labels' [semantic role]: #semantic-role 'Definition of semantic role' [visible]: #visible 'Definition of visible' [accessible name]: #accessible-name 'Definition of accessible name' diff --git a/_rules/heading-non-empty-accessible-name-ffd0e9.md b/_rules/heading-non-empty-accessible-name-ffd0e9.md index 1bd7985856d..6431cb0b893 100755 --- a/_rules/heading-non-empty-accessible-name-ffd0e9.md +++ b/_rules/heading-non-empty-accessible-name-ffd0e9.md @@ -187,12 +187,12 @@ This `h1` element is not [included in the accessibility tree][]. [accessible name]: #accessible-name 'Definition of accessible name' [accessible name and description computation]: https://www.w3.org/TR/accname [explicit role]: #explicit-role 'Definition of explicit role' -[global]: https://www.w3.org/TR/wai-aria-1.1/#global_states 'Definition of Global ARIA States and Properties' +[global]: https://www.w3.org/TR/wai-aria-1.2/#global_states 'Definition of Global ARIA States and Properties' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [property]: https://www.w3.org/TR/wai-aria/#dfn-property 'Definition of ARIA Property' [semantic role]: #semantic-role 'Definition of semantic role' -[tech h42]: https://www.w3.org/WAI/WCAG21/Techniques/html/H42 'Technique H42: Using h1-h6 to identify headings' -[usc131]: https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html 'Understanding Success Criterion 1.3.1: Info and Relationships' +[tech h42]: https://www.w3.org/WAI/WCAG22/Techniques/html/H42 'Technique H42: Using h1-h6 to identify headings' +[usc131]: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html 'Understanding Success Criterion 1.3.1: Info and Relationships' [visible]: #visible 'Definition of visible' [html element]: #namespaced-element diff --git a/_rules/html-page-lang-b5c3f8.md b/_rules/html-page-lang-b5c3f8.md index 6c782b7122f..1156ef12007 100755 --- a/_rules/html-page-lang-b5c3f8.md +++ b/_rules/html-page-lang-b5c3f8.md @@ -41,7 +41,7 @@ Each test target has a `lang` [attribute value][] that is neither empty (`""`) n ## Assumptions -The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG21/#language-of-page). +The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG22/#language-of-page). ## Accessibility Support @@ -56,8 +56,8 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 3.1.1: Language of Page](https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html) -- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG21/Techniques/html/H57) +- [Understanding Success Criterion 3.1.1: Language of Page](https://www.w3.org/WAI/WCAG22/Understanding/language-of-page.html) +- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG22/Techniques/html/H57) - [RFC 5646: Tags for Identifying Languages](https://www.rfc-editor.org/rfc/rfc5646.html) - [The `lang` and `xml:lang` attributes](https://html.spec.whatwg.org/multipage/dom.html#the-lang-and-xml:lang-attributes) diff --git a/_rules/html-page-lang-matches-default-ucwvc8.md b/_rules/html-page-lang-matches-default-ucwvc8.md index a50ba5e161f..9500634216b 100755 --- a/_rules/html-page-lang-matches-default-ucwvc8.md +++ b/_rules/html-page-lang-matches-default-ucwvc8.md @@ -46,9 +46,9 @@ For each test target, the [known primary language tag][] of its `lang` attribute ## Assumptions -- This rule assumes that the default human language of a page, as described in WCAG 2, can be determined by counting the number of words used in each language. If the default language needs to be derived in some other way (such as frequency analysis, mutual information based distance, …), this rule may fail while [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG21/#language-of-page) is still satisfied. +- This rule assumes that the default human language of a page, as described in WCAG 2, can be determined by counting the number of words used in each language. If the default language needs to be derived in some other way (such as frequency analysis, mutual information based distance, …), this rule may fail while [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG22/#language-of-page) is still satisfied. -- The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG21/#language-of-page). +- The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG22/#language-of-page). - This rule assumes that user agents and assistive technologies can programmatically determine [known primary language tags][known primary language tag] even if these do not conform to the [RFC 5646][] syntax. @@ -69,8 +69,8 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 3.1.1: Language of Page](https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html) -- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG21/Techniques/html/H57) +- [Understanding Success Criterion 3.1.1: Language of Page](https://www.w3.org/WAI/WCAG22/Understanding/language-of-page.html) +- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG22/Techniques/html/H57) - [RFC 5646: Tags for Identifying Languages](https://www.rfc-editor.org/rfc/rfc5646.html) - [The `lang` and `xml:lang` attributes](https://html.spec.whatwg.org/multipage/dom.html#the-lang-and-xml:lang-attributes) @@ -329,6 +329,6 @@ The `lang` [attribute value][] of this page is a [grandfathered tag][grandfather [grandfathered tags]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.8 [iso 639.2]: https://www.loc.gov/standards/iso639-2/php/code_list.php 'ISO 639.2: Codes for the Representation of Names of Languages' [rfc 5646]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.1 -[sc311]: https://www.w3.org/TR/WCAG21/#language-of-page 'Success Criterion 3.1.1 Language of Page' +[sc311]: https://www.w3.org/TR/WCAG22/#language-of-page 'Success Criterion 3.1.1 Language of Page' [top-level browsing context]: https://html.spec.whatwg.org/#top-level-browsing-context 'HTML top-level browsing context, as of 2020/06/05' [known primary language tag]: #known-primary-language-tag diff --git a/_rules/html-page-lang-valid-bf051a.md b/_rules/html-page-lang-valid-bf051a.md index 6c372b8155b..03e1244548c 100755 --- a/_rules/html-page-lang-valid-bf051a.md +++ b/_rules/html-page-lang-valid-bf051a.md @@ -40,7 +40,7 @@ For each test target, the `lang` attribute has a [known primary language tag][]. ## Assumptions -- The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG21/#language-of-page). +- The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG22/#language-of-page). - This rule assumes that user agents and assistive technologies can programmatically determine [known primary language tags][known primary language tag] even if these do not conform to the [RFC 5646][] syntax. @@ -52,7 +52,7 @@ There are no accessibility support issues known. ## Background -This rule is only applicable to non-embedded HTML pages. HTML pages embedded into other documents, such as through `iframe` or `object` elements are not applicable because they are not [web pages](https://www.w3.org/TR/WCAG21/#dfn-web-page-s) according to the definition in WCAG. +This rule is only applicable to non-embedded HTML pages. HTML pages embedded into other documents, such as through `iframe` or `object` elements are not applicable because they are not [web pages](https://www.w3.org/TR/WCAG22/#dfn-web-page-s) according to the definition in WCAG. ### Related rules @@ -61,8 +61,8 @@ This rule is only applicable to non-embedded HTML pages. HTML pages embedded int ### Bibliography -- [Understanding Success Criterion 3.1.1: Language of Page](https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html) -- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG21/Techniques/html/H57) +- [Understanding Success Criterion 3.1.1: Language of Page](https://www.w3.org/WAI/WCAG22/Understanding/language-of-page.html) +- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG22/Techniques/html/H57) - [RFC 5646: Tags for Identifying Languages](https://www.rfc-editor.org/rfc/rfc5646.html) - [The `lang` and `xml:lang` attributes](https://html.spec.whatwg.org/multipage/dom.html#the-lang-and-xml:lang-attributes) @@ -142,5 +142,5 @@ This rule does not apply to `svg` elements. [iso 639.2]: https://www.loc.gov/standards/iso639-2/php/code_list.php 'ISO 639.2: Codes for the Representation of Names of Languages' [region subtag]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.4 'Definition of region subtag' [rfc 5646]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.1 -[sc311]: https://www.w3.org/TR/WCAG21/#language-of-page 'Success Criterion 3.1.1 Language of Page' +[sc311]: https://www.w3.org/TR/WCAG22/#language-of-page 'Success Criterion 3.1.1 Language of Page' [known primary language tag]: #known-primary-language-tag 'Definition of Known Primary Language Tag' diff --git a/_rules/html-page-lang-xml-lang-match-5b7ae0.md b/_rules/html-page-lang-xml-lang-match-5b7ae0.md index f83eef692e6..7f81e1f0d9b 100755 --- a/_rules/html-page-lang-xml-lang-match-5b7ae0.md +++ b/_rules/html-page-lang-xml-lang-match-5b7ae0.md @@ -38,7 +38,7 @@ For each test target, the values of the [primary language subtags][], if any exi ## Assumptions -- The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG21/#language-of-page). +- The language of the page can be set by other methods than the `lang` attribute, for example using HTTP headers or the `meta` element. These methods are not supported by all assistive technologies. This rule assumes that these other methods are insufficient to satisfying [Success Criterion 3.1.1: Language of Page](https://www.w3.org/TR/WCAG22/#language-of-page). - This rule assumes that user agents and assistive technologies can programmatically determine [known primary language tags][known primary language tag] even if these do not conform to the [RFC 5646][] syntax. @@ -52,11 +52,11 @@ Since most assistive technologies will consistently use `lang` over `xml:lang` w ## Background -This rule is only applicable to non-embedded HTML pages. HTML pages embedded into other documents, such as through `iframe` or `object` elements are not applicable because they are not [web pages](https://www.w3.org/TR/WCAG21/#dfn-web-page-s) according to the definition in WCAG. +This rule is only applicable to non-embedded HTML pages. HTML pages embedded into other documents, such as through `iframe` or `object` elements are not applicable because they are not [web pages](https://www.w3.org/TR/WCAG22/#dfn-web-page-s) according to the definition in WCAG. ### Bibliography -- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG21/Techniques/html/H57) +- [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG22/Techniques/html/H57) - [RFC 5646: Tags for Identifying Languages](https://www.rfc-editor.org/rfc/rfc5646.html) - [The `lang` and `xml:lang` attributes](https://html.spec.whatwg.org/multipage/dom.html#the-lang-and-xml:lang-attributes) @@ -178,6 +178,6 @@ This rule does not apply to `html` elements with an empty (`""`) `xml:lang` attr [nested browsing context]: https://html.spec.whatwg.org/#nested-browsing-context 'Definition of nested browsing context' [primary language subtags]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.1 'Definition of primary language subtag' [rfc 5646]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.1 -[sc311]: https://www.w3.org/TR/WCAG21/#language-of-page 'Success Criterion 3.1.1 Language of Page' +[sc311]: https://www.w3.org/TR/WCAG22/#language-of-page 'Success Criterion 3.1.1 Language of Page' [top-level browsing context]: https://html.spec.whatwg.org/#top-level-browsing-context 'Definition of top-level browsing context' [known primary language tag]: #known-primary-language-tag 'Definition of Known Primary Language Tag' diff --git a/_rules/html-page-non-empty-title-2779a5.md b/_rules/html-page-non-empty-title-2779a5.md index 980bed8ed21..c594dc09fef 100755 --- a/_rules/html-page-non-empty-title-2779a5.md +++ b/_rules/html-page-non-empty-title-2779a5.md @@ -51,9 +51,9 @@ For each target element, the first [HTML][] `title` element that is a [descendan ## Assumptions -This rule assumes that [Success Criterion 2.4.2 Page Titled](https://www.w3.org/TR/WCAG21/#page-titled) does not require that a document only has one `title` element, nor that it is a child of the `head` element of a document. While this is invalid in HTML, the HTML 5.2 specification describes what should happen in case of multiple titles, and titles outside the `head` element. Because of this, neither of these validation issues causes a conformance problem for WCAG. Regardless of whether this is required by 2.4.2 Page Titled, failing this rule means the success criterion is not satisfied. +This rule assumes that [Success Criterion 2.4.2 Page Titled](https://www.w3.org/TR/WCAG22/#page-titled) does not require that a document only has one `title` element, nor that it is a child of the `head` element of a document. While this is invalid in HTML, the HTML 5.2 specification describes what should happen in case of multiple titles, and titles outside the `head` element. Because of this, neither of these validation issues causes a conformance problem for WCAG. Regardless of whether this is required by 2.4.2 Page Titled, failing this rule means the success criterion is not satisfied. -This rule assumes that the title of the page is not provided by a higher-level protocol. For example, the subject field of an email authored in HTML can provide a title without requiring a `title` element. In such a case, this rule will fail while [Success Criterion 2.4.2 Page Titled](https://www.w3.org/TR/WCAG21/#page-titled) may still be satisfied. +This rule assumes that the title of the page is not provided by a higher-level protocol. For example, the subject field of an email authored in HTML can provide a title without requiring a `title` element. In such a case, this rule will fail while [Success Criterion 2.4.2 Page Titled](https://www.w3.org/TR/WCAG22/#page-titled) may still be satisfied. ## Accessibility Support @@ -61,7 +61,7 @@ There are no accessibility support issues known. ## Background -This rule is only applicable to non-embedded HTML pages. HTML pages embedded into other documents, such as through `iframe` or `object` elements are not applicable because they are not [web pages](https://www.w3.org/TR/WCAG21/#dfn-web-page-s) according to the definition in WCAG. +This rule is only applicable to non-embedded HTML pages. HTML pages embedded into other documents, such as through `iframe` or `object` elements are not applicable because they are not [web pages](https://www.w3.org/TR/WCAG22/#dfn-web-page-s) according to the definition in WCAG. ### Related rules @@ -69,9 +69,9 @@ This rule is only applicable to non-embedded HTML pages. HTML pages embedded int ### Bibliography -- [Understanding Success Criterion 2.4.2: Page Titled](https://www.w3.org/WAI/WCAG21/Understanding/page-titled) -- [G88: Providing descriptive titles for Web pages](https://www.w3.org/WAI/WCAG21/Techniques/general/G88) -- [H25: Providing a title using the title element](https://www.w3.org/WAI/WCAG21/Techniques/html/H25) +- [Understanding Success Criterion 2.4.2: Page Titled](https://www.w3.org/WAI/WCAG22/Understanding/page-titled) +- [G88: Providing descriptive titles for Web pages](https://www.w3.org/WAI/WCAG22/Techniques/general/G88) +- [H25: Providing a title using the title element](https://www.w3.org/WAI/WCAG22/Techniques/html/H25) - [HTML Specification - The `title` element](https://html.spec.whatwg.org/#the-title-element) ## Test Cases diff --git a/_rules/html-page-title-descriptive-c4a8a4.md b/_rules/html-page-title-descriptive-c4a8a4.md index ca7bf1e8abf..acec5e9e8bc 100755 --- a/_rules/html-page-title-descriptive-c4a8a4.md +++ b/_rules/html-page-title-descriptive-c4a8a4.md @@ -66,9 +66,9 @@ The [HTML specification - The `title` element](https://html.spec.whatwg.org/#the ### Bibliography -- [Understanding Success Criterion 2.4.2: Page titled](https://www.w3.org/WAI/WCAG21/Understanding/page-titled.html) -- [Technique G88: Providing descriptive titles for Web pages](https://www.w3.org/WAI/WCAG21/Techniques/general/G88) -- [Technique H25: Providing a title using the title element](https://www.w3.org/WAI/WCAG21/Techniques/html/H25) +- [Understanding Success Criterion 2.4.2: Page titled](https://www.w3.org/WAI/WCAG22/Understanding/page-titled.html) +- [Technique G88: Providing descriptive titles for Web pages](https://www.w3.org/WAI/WCAG22/Techniques/general/G88) +- [Technique H25: Providing a title using the title element](https://www.w3.org/WAI/WCAG22/Techniques/html/H25) ## Test Cases diff --git a/_rules/id-value-unique-3ea0c8.md b/_rules/id-value-unique-3ea0c8.md index 2d77102c44a..c994931eb5f 100755 --- a/_rules/id-value-unique-3ea0c8.md +++ b/_rules/id-value-unique-3ea0c8.md @@ -55,8 +55,8 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 4.1.1: Parsing](https://www.w3.org/WAI/WCAG21/Understanding/parsing) -- [H93: Ensuring that id attributes are unique on a Web page](https://www.w3.org/WAI/WCAG21/Techniques/html/H93) +- [Understanding Success Criterion 4.1.1: Parsing](https://www.w3.org/WAI/WCAG22/Understanding/parsing) +- [H93: Ensuring that id attributes are unique on a Web page](https://www.w3.org/WAI/WCAG22/Techniques/html/H93) ## Test Cases diff --git a/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md b/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md index 61be610f1ed..edaa19a5c71 100755 --- a/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md +++ b/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md @@ -50,7 +50,7 @@ When determining if target elements embed the same resource, resolving the embed ### Bibliography - [CSS Scoping Module Level 1 (editor's draft)](https://drafts.csswg.org/css-scoping/) -- [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG21/Techniques/html/H64) +- [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H64) - [Understanding Success Criterion 4.1.2: Name, Role, Value][usc412] ## Test Cases @@ -363,9 +363,9 @@ These `iframe` elements are not [included in the accessibility tree][], because [document]: https://dom.spec.whatwg.org/#concept-document 'Definition of document' [document tree]: https://dom.spec.whatwg.org/#document-trees 'Definition of document tree' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[sc412]: https://www.w3.org/TR/WCAG21/#name-role-value 'Success Criterion 4.1.2: Name, Role, Value' +[sc412]: https://www.w3.org/TR/WCAG22/#name-role-value 'Success Criterion 4.1.2: Name, Role, Value' [top-level browsing context]: https://html.spec.whatwg.org/#top-level-browsing-context 'Definition of top level browsing context' -[usc412]: https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html 'Understanding Success Criterion 4.1.2: Name, Role, Value' +[usc412]: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html 'Understanding Success Criterion 4.1.2: Name, Role, Value' [web page (html)]: #web-page-html 'Definition of web page (HTML)' [same resource]: #same-resource 'Definition of same resource' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree' diff --git a/_rules/iframe-non-empty-accessible-name-cae760.md b/_rules/iframe-non-empty-accessible-name-cae760.md index dca37c0e248..4c72f047bd2 100755 --- a/_rules/iframe-non-empty-accessible-name-cae760.md +++ b/_rules/iframe-non-empty-accessible-name-cae760.md @@ -35,7 +35,7 @@ Each target element has an [accessible name][] that is not empty (`""`). ## Assumptions -If an `iframe` is not perceived by the user as a single control, it does not qualify as a [user interface component][] under WCAG 2. In such a scenario, failing this rule would not fail [success criterion 4.1.2](https://www.w3.org/TR/WCAG21/#name-role-value). Unless the `iframe` is both removed from the accessibility tree and removed from [sequential focus navigation][], they usually are considered to be [user interface components][user interface component]. +If an `iframe` is not perceived by the user as a single control, it does not qualify as a [user interface component][] under WCAG 2. In such a scenario, failing this rule would not fail [success criterion 4.1.2](https://www.w3.org/TR/WCAG22/#name-role-value). Unless the `iframe` is both removed from the accessibility tree and removed from [sequential focus navigation][], they usually are considered to be [user interface components][user interface component]. ## Accessibility Support @@ -53,8 +53,8 @@ Due to inconsistencies in handling focus on `iframe`, this rule ignores `iframe` ### Bibliography -- [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG21/Techniques/html/H64) -- [Understanding Success Criterion 4.1.2](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html) +- [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H64) +- [Understanding Success Criterion 4.1.2](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html) - [User interface component][] ## Test Cases @@ -160,6 +160,6 @@ This `iframe` element has an [explicit semantic role][] of `none`. [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' [marked as decorative]: #marked-as-decorative 'Definition of Marked as Decorative' [sequential focus navigation]: https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus-navigation -[user interface component]: https://www.w3.org/TR/WCAG21/#dfn-user-interface-components +[user interface component]: https://www.w3.org/TR/WCAG22/#dfn-user-interface-components [whitespace]: #whitespace 'Definition of whitespace' [explicit semantic role]: #explicit-role 'Definition of explicit semantic role' diff --git a/_rules/iframe-with-interactive-content-in-tab-order-akn7bn.md b/_rules/iframe-with-interactive-content-in-tab-order-akn7bn.md index 82a1b7ee9c3..ad9a6233eae 100644 --- a/_rules/iframe-with-interactive-content-in-tab-order-akn7bn.md +++ b/_rules/iframe-with-interactive-content-in-tab-order-akn7bn.md @@ -55,8 +55,8 @@ Each document, including documents inside an `iframe`, has its own [sequential f ### Bibliography -- [Understanding Success Criterion 2.1.1: Keyboard](https://www.w3.org/WAI/WCAG21/Understanding/keyboard) -- [WCAG Technique G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG21/Techniques/general/G202) +- [Understanding Success Criterion 2.1.1: Keyboard](https://www.w3.org/WAI/WCAG22/Understanding/keyboard) +- [WCAG Technique G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G202) ## Test Cases @@ -146,11 +146,11 @@ Once the "Privacy policy details" button is activated, the `iframe` element beco ``` @@ -162,7 +162,7 @@ Once the "Privacy policy details" button is activated, the `iframe` element beco [inert]: #inert 'Definition of Inert' [nested browsing context]: https://html.spec.whatwg.org/#nested-browsing-context 'HTML nested browsing context, 2020/12/18' [owner document]: https://dom.spec.whatwg.org/#dom-node-ownerdocument 'DOM node owner document property, 2020/12/18' -[sc211]: https://www.w3.org/TR/WCAG21/#keyboard 'WCAG 2.1 Success criterion 2.1.1 Keyboard' +[sc211]: https://www.w3.org/TR/WCAG22/#keyboard 'WCAG 2.2 Success criterion 2.1.1 Keyboard' [sequential focus navigation order]: https://html.spec.whatwg.org/multipage/#sequential-focus-navigation 'HTML sequential focus navigation, 2020/12/18' [tabindex-ordered focus navigation scope]: https://html.spec.whatwg.org/multipage/interaction.html#tabindex-ordered-focus-navigation-scope [visible]: #visible 'Definition of visible' diff --git a/_rules/image-accessible-name-descriptive-qt1vmo.md b/_rules/image-accessible-name-descriptive-qt1vmo.md index 363671389ec..aa304ce6c8b 100755 --- a/_rules/image-accessible-name-descriptive-qt1vmo.md +++ b/_rules/image-accessible-name-descriptive-qt1vmo.md @@ -64,10 +64,10 @@ Some popular browser / screen reader combinations do not pronounce the accessibl ### Bibliography -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) -- [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG21/Techniques/general/G94) -- [G95: Providing short text alternatives that provide a brief description of the non-text content](https://www.w3.org/WAI/WCAG21/Techniques/general/G95) -- [F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text)](https://www.w3.org/WAI/WCAG21/Techniques/failures/F30) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) +- [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G94) +- [G95: Providing short text alternatives that provide a brief description of the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G95) +- [F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text)](https://www.w3.org/WAI/WCAG22/Techniques/failures/F30) ## Test Cases @@ -85,7 +85,7 @@ This `img` element has an `alt` attribute that describes the image. #### Passed Example 2 -This `svg` element has an `aria-label` attribute that describes the HTML5 logo image. +This `svg` element has an `aria-label` attribute that describes the HTML5 logo image. ```html @@ -298,10 +298,10 @@ This is a `div` element with a background image. Background images must be teste [explicit semantic role]: #explicit-role [visible]: #visible 'Definition of visible' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[non-text content]: https://www.w3.org/TR/WCAG21/#dfn-non-text-content 'WCAG 2.1 definition of non-text content' +[non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content 'WCAG 2.2 definition of non-text content' [completely available]: https://html.spec.whatwg.org/#img-all 'HTML definition of Completely available, 2020/03/06' [current request]: https://html.spec.whatwg.org/#current-request 'HTML definition of Current request, 2020/03/06' [image request state]: https://html.spec.whatwg.org/#img-req-state 'HTML definition of Image request state, 2020/03/06' -[named from author]: https://www.w3.org/TR/wai-aria-1.1/#namecalculation 'WAI-ARIA definition of Named from author' +[named from author]: https://www.w3.org/TR/wai-aria-1.2/#namecalculation 'WAI-ARIA definition of Named from author' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'CSS Scoping definition of Flat tree, working draft' [ancestor]: https://dom.spec.whatwg.org/#concept-tree-ancestor 'DOM definition of ancestor, 2020/03/06' diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 667b10de333..9347034657e 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -49,7 +49,7 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor ## Assumptions -- This rule assumes that all image buttons are [user interface components as defined by WCAG 2](https://www.w3.org/TR/WCAG21/#dfn-user-interface-components). +- This rule assumes that all image buttons are [user interface components as defined by WCAG 2](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components). - This rule assumes that the default name for image buttons ("Submit Query"), as defined by the [HTML Accessibility API Mapping][html aam image button], is never descriptive. ## Accessibility Support @@ -66,9 +66,9 @@ Contrarily to `img` elements, an empty `alt` attribute (`alt=""`) does not make ### Bibliography -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html) -- [WCAG Technique H36: Using alt attributes on images used as submit buttons](https://www.w3.org/WAI/WCAG21/Techniques/html/H36) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html) +- [WCAG Technique H36: Using alt attributes on images used as submit buttons](https://www.w3.org/WAI/WCAG22/Techniques/html/H36) - [HTML Accessibility API Mappings for computing the accessible name of image buttons](https://www.w3.org/TR/html-aam-1.0/#input-type-image) ## Test Cases @@ -138,7 +138,7 @@ The image button has an `aria-labelledby` attribute, but the referenced element #### Inapplicable Example 1 -The `button` element is not an image button. [Success Criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG21/#non-text-content) can not fail text buttons. Only non-text content is applicable. +The `button` element is not an image button. [Success Criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG22/#non-text-content) can not fail text buttons. Only non-text content is applicable. ```html @@ -146,7 +146,7 @@ The `button` element is not an image button. [Success Criterion 1.1.1 Non-text C #### Inapplicable Example 2 -The `input` element with the `type` [attribute value][] of `button` is not an image button. [Success Criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG21/#non-text-content) can not fail text buttons. Only non-text content is applicable. +The `input` element with the `type` [attribute value][] of `button` is not an image button. [Success Criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG22/#non-text-content) can not fail text buttons. Only non-text content is applicable. ```html @@ -154,7 +154,7 @@ The `input` element with the `type` [attribute value][] of `button` is not an im #### Inapplicable Example 3 -The `button` element is tested separately from the `img` element. [Success Criterion 4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG21/#name-role-value) is applied to the button, whereas the image is tested under [Success Criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG21/#non-text-content) +The `button` element is tested separately from the `img` element. [Success Criterion 4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG22/#name-role-value) is applied to the button, whereas the image is tested under [Success Criterion 1.1.1 Non-text Content](https://www.w3.org/TR/WCAG22/#non-text-content) ```html @@ -162,7 +162,7 @@ The `button` element is tested separately from the `img` element. [Success Crite #### Inapplicable Example 4 -The `img` element is not a user interface component, and so is not tested for [Success Criterion 4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG21/#name-role-value). +The `img` element is not a user interface component, and so is not tested for [Success Criterion 4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG22/#name-role-value). ```html W3C logo diff --git a/_rules/image-filename-as-accessible-name-9eb3f6.md b/_rules/image-filename-as-accessible-name-9eb3f6.md index fbd0b0f74ee..5fd7bcdfa47 100755 --- a/_rules/image-filename-as-accessible-name-9eb3f6.md +++ b/_rules/image-filename-as-accessible-name-9eb3f6.md @@ -70,10 +70,10 @@ It is fairly common for content management systems (CMS) or other tools to defau ### Bibliography -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) -- [F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text)](https://www.w3.org/WAI/WCAG21/Techniques/failures/F30) -- [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG21/Techniques/general/G94) -- [G95: Providing short text alternatives that provide a brief description of the non-text content](https://www.w3.org/WAI/WCAG21/Techniques/general/G95) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) +- [F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text)](https://www.w3.org/WAI/WCAG22/Techniques/failures/F30) +- [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G94) +- [G95: Providing short text alternatives that provide a brief description of the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G95) ## Test Cases @@ -264,7 +264,7 @@ This `img` element has an [accessible name][] which is not equivalent to the fil [image button]: https://html.spec.whatwg.org/multipage/input.html#image-button-state-(type=image) 'Definition of the Image Button state' [image sources]: https://html.spec.whatwg.org/multipage/images.html#image-source 'Definition of image source' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[non-text content]: https://www.w3.org/TR/WCAG21/#dfn-non-text-content +[non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content [semantic role]: #semantic-role 'Definition of semantic role' [source set]: https://html.spec.whatwg.org/multipage/images.html#source-set 'Definition of source set' [whitespace]: #whitespace 'Definition of whitespace' diff --git a/_rules/image-no-text-0va7u6.md b/_rules/image-no-text-0va7u6.md index 2fd8b2df354..cc98e2b567a 100644 --- a/_rules/image-no-text-0va7u6.md +++ b/_rules/image-no-text-0va7u6.md @@ -242,11 +242,11 @@ This `svg` element does not have `image` element descendants. [essential]: #essential-text-presentation 'Definition of Essential (Text Presentation)' [insignificant]: #insignificant 'Definition of Insignificant' -[human language]: https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html#dfn-human-language 'WCAG 2.1, Definition of human language' +[human language]: https://www.w3.org/WAI/WCAG22/Understanding/images-of-text.html#dfn-human-language 'WCAG 2.2, Definition of human language' [image button]: https://html.spec.whatwg.org/multipage/input.html#image-button-state-(type=image) -[purely decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG 2.1, Purely decorative' +[purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG 2.2, Purely decorative' [rendered image resources]: #rendered-image-resource 'Definition of rendered image resource' -[sc1.4.5]: https://www.w3.org/WAI/WCAG21/Understanding/images-of-text -[sc1.4.9]: https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception +[sc1.4.5]: https://www.w3.org/WAI/WCAG22/Understanding/images-of-text +[sc1.4.9]: https://www.w3.org/WAI/WCAG22/Understanding/images-of-text-no-exception [visible]: #visible 'Definition of visible' [web page]: #web-page-html 'Definition of web page (HTML)' diff --git a/_rules/image-non-empty-accessible-name-23a2a8.md b/_rules/image-non-empty-accessible-name-23a2a8.md index 74a44e3c706..e4c27e4562b 100755 --- a/_rules/image-non-empty-accessible-name-23a2a8.md +++ b/_rules/image-non-empty-accessible-name-23a2a8.md @@ -60,15 +60,15 @@ There are no assumptions. ### Bibliography -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) -- [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG21/Techniques/general/G94) -- [G95: Providing short text alternatives that provide a brief description of the non-text content](https://www.w3.org/WAI/WCAG21/Techniques/general/G95) -- [H37: Using alt attributes on img elements](https://www.w3.org/WAI/WCAG21/Techniques/html/H37) -- [ARIA6: Using aria-label to provide labels for objects](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA6) -- [ARIA10: Using aria-labelledby to provide a text alternative for non-text content](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA10) -- [H67: Using null alt text and no title attribute on img elements for images that AT should ignore](https://www.w3.org/WAI/WCAG21/Techniques/html/H67) -- [F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them](https://www.w3.org/WAI/WCAG21/Techniques/failures/F38) -- [F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"](https://www.w3.org/WAI/WCAG21/Techniques/failures/F65) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) +- [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G94) +- [G95: Providing short text alternatives that provide a brief description of the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G95) +- [H37: Using alt attributes on img elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H37) +- [ARIA6: Using aria-label to provide labels for objects](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA6) +- [ARIA10: Using aria-labelledby to provide a text alternative for non-text content](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA10) +- [H67: Using null alt text and no title attribute on img elements for images that AT should ignore](https://www.w3.org/WAI/WCAG22/Techniques/html/H67) +- [F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them](https://www.w3.org/WAI/WCAG22/Techniques/failures/F38) +- [F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"](https://www.w3.org/WAI/WCAG22/Techniques/failures/F65) ## Test Cases @@ -247,7 +247,7 @@ This `img` element is hidden with `visibility: hidden`. [explicit role]: #explicit-role 'Definition of explicit role' [focusable]: #focusable 'Definition of focusable' [implicit role]: #implicit-role 'Definition of implicit role' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [programmatically hidden]: #programmatically-hidden 'Definition of Programmatically Hidden' [semantic role]: #semantic-role 'Definition of semantic role' [html]: #namespaced-element diff --git a/_rules/image-not-in-acc-tree-is-decorative-e88epe.md b/_rules/image-not-in-acc-tree-is-decorative-e88epe.md index 8640f32a4b6..bae30ea4335 100755 --- a/_rules/image-not-in-acc-tree-is-decorative-e88epe.md +++ b/_rules/image-not-in-acc-tree-is-decorative-e88epe.md @@ -49,13 +49,13 @@ This rule applies to any `img`, `canvas` or `svg` element that is [visible][] an Each test target is [purely decorative][]. -**Note**: It is relatively common for an informative image such as an icon to be marked up as decorative, if the text alternative is adjacent to the image. This is a [conforming alternative version][] for the image. This fails the rule but meets [conformance requirement 1 of WCAG 2.1](https://www.w3.org/TR/WCAG21/#cc1). +**Note**: It is relatively common for an informative image such as an icon to be marked up as decorative, if the text alternative is adjacent to the image. This is a [conforming alternative version][] for the image. This fails the rule but meets [conformance requirement 1 of WCAG 2.2](https://www.w3.org/TR/WCAG22/#cc1). ## Assumptions - `svg` elements with a [semantic role][] of `graphics-document` and with an empty (`""`) [accessible name][] are ignored by assistive technologies tested for this rule. If some assistive technology does not ignore these elements, and that assistive technology is required for conformance, passing this rule does not ensure all decorative `svg` elements can be ignored, and the [success criterion 1.1.1 Non-text content][] may still not be satisfied. The same is true for `canvas` elements with no [semantic role][] and an empty (`""`) [accessible name][]. -- A web page with informative images without an [accessible name][] may conform to WCAG 2.1 Level A when the information provided by that image is available elsewhere on the web page itself. For example if an equivalent text is adjacent to the image, or if the text alternative is included in the [accessible name][] of a parent element. +- A web page with informative images without an [accessible name][] may conform to WCAG 2.2 Level A when the information provided by that image is available elsewhere on the web page itself. For example if an equivalent text is adjacent to the image, or if the text alternative is included in the [accessible name][] of a parent element. ## Accessibility Support @@ -65,8 +65,8 @@ There are no accessibility support issues known. ### Bibliography -- [H67: Using null alt text and no title attribute on img elements for images that AT should ignore](https://www.w3.org/WAI/WCAG21/Techniques/html/H67.html) -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) +- [H67: Using null alt text and no title attribute on img elements for images that AT should ignore](https://www.w3.org/WAI/WCAG22/Techniques/html/H67.html) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) ## Test Cases @@ -311,12 +311,12 @@ This `img` element has an `src` attribute which will cause the [image request st [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the accessibility tree' [semantic role]: #semantic-role 'Definition of Semantic Role' [explicit semantic role]: #explicit-role 'Definition of Explicit semantic role' -[purely decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG definition of Pure decoration' -[success criterion 1.1.1 non-text content]: https://www.w3.org/TR/WCAG21/#non-text-content -[conforming alternative version]: https://www.w3.org/TR/WCAG21/#dfn-conforming-alternate-version 'WCAG definition of Conforming alternative version' +[purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure decoration' +[success criterion 1.1.1 non-text content]: https://www.w3.org/TR/WCAG22/#non-text-content +[conforming alternative version]: https://www.w3.org/TR/WCAG22/#dfn-conforming-alternate-version 'WCAG definition of Conforming alternative version' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'CSS Scoping definition of Flat tree, working draft' [ancestor]: https://dom.spec.whatwg.org/#concept-tree-ancestor 'DOM definition of ancestor, 2020/03/06' -[named from author]: https://www.w3.org/TR/wai-aria-1.1/#namecalculation 'WAI-ARIA definition of Named from author' +[named from author]: https://www.w3.org/TR/wai-aria-1.2/#namecalculation 'WAI-ARIA definition of Named from author' [current request]: https://html.spec.whatwg.org/#current-request 'HTML definition of Current request, 2020/03/06' [image request state]: https://html.spec.whatwg.org/#img-req-state 'HTML definition of Image request state, 2020/03/06' [completely available]: https://html.spec.whatwg.org/#img-all 'HTML definition of Completely available, 2020/03/06' diff --git a/_rules/important-letter-spacing-wide-enough-24afc2.md b/_rules/important-letter-spacing-wide-enough-24afc2.md index e5171598448..f30f2846ac5 100755 --- a/_rules/important-letter-spacing-wide-enough-24afc2.md +++ b/_rules/important-letter-spacing-wide-enough-24afc2.md @@ -57,7 +57,7 @@ CSS specifications define each declaration as being either [important][] (if it ### Bibliography -- [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html) +- [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html) - [CSS Text Module Level 3 - Spacing](https://www.w3.org/TR/css-text-3/#spacing) - [CSS Visual formatting model details](https://drafts.csswg.org/css2/visudet.html) @@ -296,8 +296,8 @@ The [computed][] value of the `letter-spacing` property of this `span` element i [important]: https://www.w3.org/TR/css-cascade-4/#importance 'CSS Cascading and Inheritance Level 4 (Working draft) - Importance' [inherited]: https://www.w3.org/TR/css-cascade-4/#inheriting 'CSS Cascading and Inheritance Level 4 (Working draft) - Inherited Values' [normal]: https://www.w3.org/TR/css-cascade-4/#normal 'CSS Cascading and Inheritance Level 4 (Working draft) - Normal declarations' -[sc1412]: https://www.w3.org/TR/WCAG21/#text-spacing 'Success Criterion 1.4.12 Text Spacing' -[sc148]: https://www.w3.org/TR/WCAG21/#visual-presentation 'Success Criterion 1.4.8 Visual Presentation' +[sc1412]: https://www.w3.org/TR/WCAG22/#text-spacing 'Success Criterion 1.4.12 Text Spacing' +[sc148]: https://www.w3.org/TR/WCAG22/#visual-presentation 'Success Criterion 1.4.8 Visual Presentation' [specified]: https://www.w3.org/TR/css-cascade-4/#specified 'CSS Cascading and Inheritance Level 4 (Working draft) - Specified Values' [specificity]: https://www.w3.org/TR/selectors/#specificity 'CSS Selectors Level 4 (Working draft) - Specificity' [text node]: https://dom.spec.whatwg.org/#text diff --git a/_rules/important-line-height-wide-enough-78fd32.md b/_rules/important-line-height-wide-enough-78fd32.md index 7e9767949e6..72021975b5e 100755 --- a/_rules/important-line-height-wide-enough-78fd32.md +++ b/_rules/important-line-height-wide-enough-78fd32.md @@ -57,7 +57,7 @@ This rule evaluates the [used][] value of the `line-height` property instead of ### Bibliography -- [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html) +- [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html) - [CSS Text Module Level 3 - Spacing](https://www.w3.org/TR/css-text-3/#spacing) - [CSS Visual formatting model details](https://drafts.csswg.org/css2/visudet.html) @@ -360,7 +360,7 @@ The [computed][] value of the `line-height` property of this `span` element is t [important]: https://www.w3.org/TR/css-cascade-4/#importance 'CSS Cascading and Inheritance Level 4 (Working draft) - Importance' [inherited]: https://www.w3.org/TR/css-cascade-4/#inheriting 'CSS Cascading and Inheritance Level 4 (Working draft) - Inherited Values' [normal]: https://www.w3.org/TR/css-cascade-4/#normal 'CSS Cascading and Inheritance Level 4 (Working draft) - Normal declarations' -[sc1412]: https://www.w3.org/TR/WCAG21/#text-spacing 'Success Criterion 1.4.12 Text Spacing' +[sc1412]: https://www.w3.org/TR/WCAG22/#text-spacing 'Success Criterion 1.4.12 Text Spacing' [soft wrap break]: https://www.w3.org/TR/css-text-3/#soft-wrap-break [specificity]: https://www.w3.org/TR/selectors/#specificity 'CSS Selectors Level 4 (Working draft) - Specificity' [specified]: https://www.w3.org/TR/css-cascade-4/#specified 'CSS Cascading and Inheritance Level 4 (Working draft) - Specified Values' diff --git a/_rules/important-word-spacing-wide-enough-9e45ec.md b/_rules/important-word-spacing-wide-enough-9e45ec.md index 4e3c031fda7..1ba764bb530 100755 --- a/_rules/important-word-spacing-wide-enough-9e45ec.md +++ b/_rules/important-word-spacing-wide-enough-9e45ec.md @@ -57,7 +57,7 @@ CSS specifications define each declaration as being either [important][] (if it ### Bibliography -- [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html) +- [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html) - [CSS Text Module Level 3 - Spacing](https://www.w3.org/TR/css-text-3/#spacing) - [CSS Visual formatting model details](https://drafts.csswg.org/css2/visudet.html) @@ -296,8 +296,8 @@ The [computed][] value of the `word-spacing` property of this `span` element is [important]: https://www.w3.org/TR/css-cascade-4/#importance 'CSS Cascading and Inheritance Level 4 (Working draft) - Importance' [inherited]: https://www.w3.org/TR/css-cascade-4/#inheriting 'CSS Cascading and Inheritance Level 4 (Working draft) - Inherited Values' [normal]: https://www.w3.org/TR/css-cascade-4/#normal 'CSS Cascading and Inheritance Level 4 (Working draft) - Normal declarations' -[sc1412]: https://www.w3.org/TR/WCAG21/#text-spacing 'Success Criterion 1.4.12 Text Spacing' -[sc148]: https://www.w3.org/TR/WCAG21/#visual-presentation 'Success Criterion 1.4.8 Visual Presentation' +[sc1412]: https://www.w3.org/TR/WCAG22/#text-spacing 'Success Criterion 1.4.12 Text Spacing' +[sc148]: https://www.w3.org/TR/WCAG22/#visual-presentation 'Success Criterion 1.4.8 Visual Presentation' [specificity]: https://www.w3.org/TR/selectors/#specificity 'CSS Selectors Level 4 (Working draft) - Specificity' [specified]: https://www.w3.org/TR/css-cascade-4/#specified 'CSS Cascading and Inheritance Level 4 (Working draft) - Specified Values' [text node]: https://dom.spec.whatwg.org/#text diff --git a/_rules/invalid-form-field-value-36b590.md b/_rules/invalid-form-field-value-36b590.md index 1797def5638..dbe5dbfc22c 100644 --- a/_rules/invalid-form-field-value-36b590.md +++ b/_rules/invalid-form-field-value-36b590.md @@ -84,9 +84,9 @@ A single test target can be related to multiple [form field error indicators][fo ### Bibliography -- [Understanding Success Criterion 3.3.1: Error Identification](https://www.w3.org/WAI/WCAG21/Understanding/error-identification) -- [G84: Providing a text description when the user provides information that is not in the list of allowed values](https://www.w3.org/WAI/WCAG21/Techniques/general/G84) -- [G85: Providing a text description when user input falls outside the required format or values](https://www.w3.org/WAI/WCAG21/Techniques/general/G85) +- [Understanding Success Criterion 3.3.1: Error Identification](https://www.w3.org/WAI/WCAG22/Understanding/error-identification) +- [G84: Providing a text description when the user provides information that is not in the list of allowed values](https://www.w3.org/WAI/WCAG22/Techniques/general/G84) +- [G85: Providing a text description when user input falls outside the required format or values](https://www.w3.org/WAI/WCAG22/Techniques/general/G85) ## Test Cases @@ -242,9 +242,9 @@ There are no elements with any of the required [semantic roles][semantic role]. [aria 1.2]: https://www.w3.org/TR/wai-aria-1.2/ [form field error indicator]: #form-field-error-indicator [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[non-text content]: https://www.w3.org/TR/WCAG21/#dfn-non-text-content -[presentation]: https://www.w3.org/TR/WCAG21/#dfn-presentation +[non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content +[presentation]: https://www.w3.org/TR/WCAG22/#dfn-presentation [semantic role]: #semantic-role 'Definition of semantic role' -[text]: https://www.w3.org/TR/WCAG21/#dfn-text +[text]: https://www.w3.org/TR/WCAG22/#dfn-text [visible]: #visible 'Definition of visible' [html element]: #namespaced-element diff --git a/_rules/link-alone-descriptive-aizyf1.md b/_rules/link-alone-descriptive-aizyf1.md index 7db0212e2dc..b4d5299adf7 100755 --- a/_rules/link-alone-descriptive-aizyf1.md +++ b/_rules/link-alone-descriptive-aizyf1.md @@ -51,11 +51,11 @@ Each test target has an [accessible name][] which describes its purpose. ### Bibliography - [Understanding Success Criterion 2.4.9: Link Purpose (Link Only)][usc249] -- [G91: Providing link text that describes the purpose of a link](https://www.w3.org/WAI/WCAG21/Techniques/general/G91) -- [H30: Providing link text that describes the purpose of a link for anchor elements](https://www.w3.org/WAI/WCAG21/Techniques/html/H30) -- [H24: Providing text alternatives for the area elements of image maps](https://www.w3.org/WAI/WCAG21/Techniques/html/H24) -- [ARIA7: Using aria-labelledby for link purpose](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA7) -- [ARIA8: Using aria-label for link purpose](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA8) +- [G91: Providing link text that describes the purpose of a link](https://www.w3.org/WAI/WCAG22/Techniques/general/G91) +- [H30: Providing link text that describes the purpose of a link for anchor elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H30) +- [H24: Providing text alternatives for the area elements of image maps](https://www.w3.org/WAI/WCAG22/Techniques/html/H24) +- [ARIA7: Using aria-labelledby for link purpose](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA7) +- [ARIA8: Using aria-label for link purpose](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA8) ## Test Cases @@ -219,8 +219,8 @@ There is no [inheriting semantic][] `link` in this document (`a` element without [accessible name]: #accessible-name 'Definition of Accessible Name' [explicit role]: #explicit-role 'Definition of Explicit Role' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' [semantic role]: #semantic-role 'Definition of Semantic Role' -[sc249]: https://www.w3.org/TR/WCAG21/#link-purpose-link-only 'Success Criterion 2.4.9: Link Purpose (Link Only)' -[usc249]: https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only.html 'Understanding Success Criterion 2.4.9: Link Purpose (Link Only)' +[sc249]: https://www.w3.org/TR/WCAG22/#link-purpose-link-only 'Success Criterion 2.4.9: Link Purpose (Link Only)' +[usc249]: https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html 'Understanding Success Criterion 2.4.9: Link Purpose (Link Only)' diff --git a/_rules/link-in-context-descriptive-5effbb.md b/_rules/link-in-context-descriptive-5effbb.md index 872541c7efc..58685819197 100755 --- a/_rules/link-in-context-descriptive-5effbb.md +++ b/_rules/link-in-context-descriptive-5effbb.md @@ -56,18 +56,18 @@ The [accessible name][] of each target element together with its [programmatical ### Bibliography -- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html) -- [Understanding Success Criterion 2.4.9: Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only.html) -- [G91: Providing link text that describes the purpose of a link](https://www.w3.org/WAI/WCAG21/Techniques/general/G91) -- [H30: Providing link text that describes the purpose of a link for anchor elements](https://www.w3.org/WAI/WCAG21/Techniques/html/H30) -- [H24: Providing text alternatives for the area elements of image maps](https://www.w3.org/WAI/WCAG21/Techniques/html/H24) +- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html) +- [Understanding Success Criterion 2.4.9: Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html) +- [G91: Providing link text that describes the purpose of a link](https://www.w3.org/WAI/WCAG22/Techniques/general/G91) +- [H30: Providing link text that describes the purpose of a link for anchor elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H30) +- [H24: Providing text alternatives for the area elements of image maps](https://www.w3.org/WAI/WCAG22/Techniques/html/H24) - [G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence](https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G53) -- [ARIA7: Using aria-labelledby for link purpose](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA7) -- [ARIA8: Using aria-label for link purpose](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA8) -- [H77: Identifying the purpose of a link using link text combined with its enclosing list item](https://www.w3.org/WAI/WCAG21/Techniques/html/H77) -- [H78: Identifying the purpose of a link using link text combined with its enclosing paragraph](https://www.w3.org/WAI/WCAG21/Techniques/html/H78) -- [H79: Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells](https://www.w3.org/WAI/WCAG21/Techniques/html/H79) -- [H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested](https://www.w3.org/WAI/WCAG21/Techniques/html/H81) +- [ARIA7: Using aria-labelledby for link purpose](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA7) +- [ARIA8: Using aria-label for link purpose](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA8) +- [H77: Identifying the purpose of a link using link text combined with its enclosing list item](https://www.w3.org/WAI/WCAG22/Techniques/html/H77) +- [H78: Identifying the purpose of a link using link text combined with its enclosing paragraph](https://www.w3.org/WAI/WCAG22/Techniques/html/H78) +- [H79: Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells](https://www.w3.org/WAI/WCAG22/Techniques/html/H79) +- [H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested](https://www.w3.org/WAI/WCAG22/Techniques/html/H81) ## Test Cases @@ -339,9 +339,9 @@ This `a` element is not a [semantic][semantic role] `link`, because it has no `h [accessible name]: #accessible-name 'Definition of Accessible Name' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [programmatically determined link context]: #programmatically-determined-link-context 'Definition of Programmatically Determined Link Context' [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' [semantic role]: #semantic-role 'Definition of Semantic Role' -[sc244]: https://www.w3.org/TR/WCAG21/#link-purpose-in-context 'Success Criterion 2.4.4 Link Purpose (In Context)' -[sc249]: https://www.w3.org/TR/WCAG21/#link-purpose-link-only 'Success Criterion 2.4.9 Link Purpose (Link Only)' +[sc244]: https://www.w3.org/TR/WCAG22/#link-purpose-in-context 'Success Criterion 2.4.4 Link Purpose (In Context)' +[sc249]: https://www.w3.org/TR/WCAG22/#link-purpose-link-only 'Success Criterion 2.4.9 Link Purpose (Link Only)' diff --git a/_rules/link-non-empty-accessible-name-c487ae.md b/_rules/link-non-empty-accessible-name-c487ae.md index b1d6bad8aff..9c1fd537c24 100755 --- a/_rules/link-non-empty-accessible-name-c487ae.md +++ b/_rules/link-non-empty-accessible-name-c487ae.md @@ -55,7 +55,7 @@ Each target element has an [accessible name][] that is not empty (`""`). ## Assumptions -The rule assumes that all links are [user interface components](https://www.w3.org/TR/WCAG21/#dfn-user-interface-components) as defined by WCAG 2. When the link role is used on elements that do not behave as links, failing this rule might not mean that the success criteria are failed. +The rule assumes that all links are [user interface components](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components) as defined by WCAG 2. When the link role is used on elements that do not behave as links, failing this rule might not mean that the success criteria are failed. ## Accessibility Support @@ -71,11 +71,11 @@ The rule assumes that all links are [user interface components](https://www.w3.o ### Bibliography -- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context) -- [ARIA7: Using aria-labelledby for link purpose](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA7) -- [ARIA8: Using aria-label for link purpose](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA8) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) -- [F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link](https://www.w3.org/WAI/WCAG21/Techniques/failures/F89) +- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context) +- [ARIA7: Using aria-labelledby for link purpose](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA7) +- [ARIA8: Using aria-label for link purpose](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA8) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link](https://www.w3.org/WAI/WCAG22/Techniques/failures/F89) ## Test Cases @@ -358,7 +358,7 @@ This `a` element does not have the role of link because it does not have an `hre [focusable]: #focusable 'Definition of focusable' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' [inheriting semantic]: #inheriting-semantic 'Definition of inheriting semantic role' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [semantic role]: #semantic-role 'Definition of Semantic Role' [attribute value]: #attribute-value 'Definition of Attribute value' [html element]: #namespaced-element diff --git a/_rules/links-identical-name-equivalent-purpose-b20e66.md b/_rules/links-identical-name-equivalent-purpose-b20e66.md index 1b171cf25c1..9ee15e68a7f 100755 --- a/_rules/links-identical-name-equivalent-purpose-b20e66.md +++ b/_rules/links-identical-name-equivalent-purpose-b20e66.md @@ -60,7 +60,7 @@ When followed, the links in each set of target elements resolve to the [same res ### Bibliography - [CSS Scoping Module Level 1 (editor's draft)](https://drafts.csswg.org/css-scoping/) -- [Understanding Success Criterion 2.4.9: Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only.html) +- [Understanding Success Criterion 2.4.9: Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html) - [HTML Specification - URL parsing](https://html.spec.whatwg.org/#resolving-urls) ## Test Cases @@ -350,7 +350,7 @@ These `a` and `area` elements have no `href` attribute. Thus they are not links These links have different [accessible names][accessible name]. The rule only applies to identical [accessible names][accessible name], not to identical link destinations. -**Note:** It is a best practice for [Success Criterion 2.4.9: Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only.html) that identical links have identical [accessible names][accessible name]. This is however not a requirement. +**Note:** It is a best practice for [Success Criterion 2.4.9: Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html) that identical links have identical [accessible names][accessible name]. This is however not a requirement. ```html @@ -384,9 +384,9 @@ These `span` elements do not have a [semantic role][] of `link`. They are not va [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' [light tree]: https://dom.spec.whatwg.org/#concept-light-tree 'Definition of light tree' [matching]: #matching-characters 'Definition of matching characters' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [same resource]: #same-resource 'Definition of same resource' -[sc249]: https://www.w3.org/TR/WCAG21/#link-purpose-link-only 'Success Criterion 2.4.9: Link Purpose (Link Only)' +[sc249]: https://www.w3.org/TR/WCAG22/#link-purpose-link-only 'Success Criterion 2.4.9: Link Purpose (Link Only)' [semantic role]: #semantic-role 'Definition of semantic role' [shadow tree]: https://dom.spec.whatwg.org/#shadow-tree 'Definition of shadow tree' [web page (html)]: #web-page-html 'Definition of web page (HTML)' diff --git a/_rules/links-with-identical-names-and-context-serve-equivalent-purpose-fd3a94.md b/_rules/links-with-identical-names-and-context-serve-equivalent-purpose-fd3a94.md index d8b228511c9..7674e95ef74 100755 --- a/_rules/links-with-identical-names-and-context-serve-equivalent-purpose-fd3a94.md +++ b/_rules/links-with-identical-names-and-context-serve-equivalent-purpose-fd3a94.md @@ -64,7 +64,7 @@ There is a difference between two contexts being the _same_ and being _identical ### Bibliography -- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html) +- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html) - [HTML Specification - URL parsing](https://html.spec.whatwg.org/#resolving-urls) ## Test Cases @@ -400,7 +400,7 @@ These two HTML `a` elements have the same [accessible name][] but different [pro [matching]: #matching-characters 'Definition of matching characters' [programmatically determined link context]: #programmatically-determined-link-context 'Definition of programmatically determined link context' [same resource]: #same-resource 'Definition of same resource' -[sc244]: https://www.w3.org/TR/WCAG21/#link-purpose-in-context 'Success Criterion 2.4.4: Link Purpose (In Context)' +[sc244]: https://www.w3.org/TR/WCAG22/#link-purpose-in-context 'Success Criterion 2.4.4: Link Purpose (In Context)' [semantic role]: #semantic-role 'Definition of semantic role' [shadow tree]: https://dom.spec.whatwg.org/#shadow-tree 'Definition of shadow tree' [web page (html)]: #web-page-html 'Definition of web page (HTML)' diff --git a/_rules/menuitem-non-empty-name-m6b1q3.md b/_rules/menuitem-non-empty-name-m6b1q3.md index 64b8c20120b..cf73f3bfdb6 100755 --- a/_rules/menuitem-non-empty-name-m6b1q3.md +++ b/_rules/menuitem-non-empty-name-m6b1q3.md @@ -33,7 +33,7 @@ Each target element has an [accessible name][] that is not empty (`""`). ## Assumptions -This rule assumes that all menuitems are [user interface components as defined by WCAG 2](https://www.w3.org/TR/WCAG21/#dfn-user-interface-components). If an element has a role of `menuitem` that would not be perceived as a single control by users, [4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG21/#name-role-value) would not apply and so failing this rule would not result in a conformance issue. +This rule assumes that all menuitems are [user interface components as defined by WCAG 2](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components). If an element has a role of `menuitem` that would not be perceived as a single control by users, [4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG22/#name-role-value) would not apply and so failing this rule would not result in a conformance issue. ## Accessibility Support @@ -43,9 +43,9 @@ Implementation of [Presentational Roles Conflict Resolution][] varies from one b ### Bibliography -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) -- [ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA14) -- [ARIA16: Using aria-labelledby to provide a name for user interface controls](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA16) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14) +- [ARIA16: Using aria-labelledby to provide a name for user interface controls](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA16) ## Test Cases @@ -161,6 +161,6 @@ This element with the `menuitem` role does not need an [accessible name][] becau [accessible name]: #accessible-name 'Definition of accessible name' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [semantic role]: #semantic-role 'Definition of Semantic Role' [html elements]: #namespaced-element diff --git a/_rules/meta-refresh-no-delay-bc659a.md b/_rules/meta-refresh-no-delay-bc659a.md index 29c6822aef7..dd0479b293b 100755 --- a/_rules/meta-refresh-no-delay-bc659a.md +++ b/_rules/meta-refresh-no-delay-bc659a.md @@ -53,7 +53,7 @@ For each target, the _time_ from the content [attribute value][] is either 0 or ## Assumptions - This rule assumes no functionality was provided by the website for the user to adjust the timer. -- This rule assumes that the refresh was not [essential](https://www.w3.org/TR/WCAG21/#dfn-essential), which is listed as a valid exception to [2.2.1 Time Adjustable][sc221]. +- This rule assumes that the refresh was not [essential](https://www.w3.org/TR/WCAG22/#dfn-essential), which is listed as a valid exception to [2.2.1 Time Adjustable][sc221]. ## Accessibility Support @@ -65,10 +65,10 @@ Because a refresh with a timing of 0 is a redirect, it is exempt from this rule. ### Bibliography -- [Understanding Success Criterion 2.2.1: Timing Adjustable](https://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable.html) -- [Understanding Success Criterion 2.2.4: Interruptions](https://www.w3.org/WAI/WCAG21/Understanding/interruptions.html) -- [Understanding Success Criterion 3.2.5: Change on Request](https://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html) -- [G110: Using an instant client-side redirect](https://www.w3.org/WAI/WCAG21/Techniques/general/G110) +- [Understanding Success Criterion 2.2.1: Timing Adjustable](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html) +- [Understanding Success Criterion 2.2.4: Interruptions](https://www.w3.org/WAI/WCAG22/Understanding/interruptions.html) +- [Understanding Success Criterion 3.2.5: Change on Request](https://www.w3.org/WAI/WCAG22/Understanding/change-on-request.html) +- [G110: Using an instant client-side redirect](https://www.w3.org/WAI/WCAG22/Techniques/general/G110) - [H76: Using meta refresh to create an instant client-side redirect](https://www.w3.org/TR/WCAG-TECHS/H76.html) - [F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit](https://www.w3.org/TR/WCAG-TECHS/F40.html) - [F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out](https://www.w3.org/TR/WCAG-TECHS/F41.html) @@ -271,5 +271,5 @@ This 'meta' element contains an invalid `content` attribute and will not refresh [attribute value]: #attribute-value 'Definition of Attribute Value' [meta refresh]: https://html.spec.whatwg.org/#attr-meta-http-equiv-refresh 'HTML specification of the meta refresh State' -[sc221]: https://www.w3.org/TR/WCAG21/#timing-adjustable 'WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable' +[sc221]: https://www.w3.org/TR/WCAG22/#timing-adjustable 'WCAG 2.2 Success Criterion 2.2.1 Timing Adjustable' [shared declarative refresh steps]: https://html.spec.whatwg.org/#shared-declarative-refresh-steps 'HTML specification of the Shared Declarative Refresh Steps' diff --git a/_rules/meta-refresh-no-delay-no-exception-bisz58.md b/_rules/meta-refresh-no-delay-no-exception-bisz58.md index ac2bbf6ea23..86d8288fd2e 100755 --- a/_rules/meta-refresh-no-delay-no-exception-bisz58.md +++ b/_rules/meta-refresh-no-delay-no-exception-bisz58.md @@ -65,10 +65,10 @@ Because a refresh with a timing of 0 is effectively a redirect, it is exempt fro ### Bibliography -- [Understanding Success Criterion 2.2.1: Timing Adjustable](https://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable.html) -- [Understanding Success Criterion 2.2.4: Interruptions](https://www.w3.org/WAI/WCAG21/Understanding/interruptions.html) -- [Understanding Success Criterion 3.2.5: Change on Request](https://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html) -- [G110: Using an instant client-side redirect](https://www.w3.org/WAI/WCAG21/Techniques/general/G110) +- [Understanding Success Criterion 2.2.1: Timing Adjustable](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html) +- [Understanding Success Criterion 2.2.4: Interruptions](https://www.w3.org/WAI/WCAG22/Understanding/interruptions.html) +- [Understanding Success Criterion 3.2.5: Change on Request](https://www.w3.org/WAI/WCAG22/Understanding/change-on-request.html) +- [G110: Using an instant client-side redirect](https://www.w3.org/WAI/WCAG22/Techniques/general/G110) - [H76: Using meta refresh to create an instant client-side redirect](https://www.w3.org/TR/WCAG-TECHS/H76.html) - [F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit](https://www.w3.org/TR/WCAG-TECHS/F40.html) - [F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out](https://www.w3.org/TR/WCAG-TECHS/F41.html) diff --git a/_rules/meta-viewport-b4f0c3.md b/_rules/meta-viewport-b4f0c3.md index 012b5948881..16a64c6974e 100755 --- a/_rules/meta-viewport-b4f0c3.md +++ b/_rules/meta-viewport-b4f0c3.md @@ -59,7 +59,7 @@ For each test target's [attribute value][], at least one of the following is tru Pages for which any of the following is true may satisfy Success Criteria [1.4.4 Resize text][sc144] and [1.4.10 Reflow][sc1410], even if the rule results in a failed outcome. - The [page][] has no [visible][] [content][]; or -- There is another [mechanism](https://www.w3.org/TR/WCAG21/#dfn-mechanism) available to resize the text content; or +- There is another [mechanism](https://www.w3.org/TR/WCAG22/#dfn-mechanism) available to resize the text content; or - The [content][] does not need to reflow in order to fit in an area of 320 by 256 [CSS pixels][]. ## Accessibility Support @@ -72,8 +72,8 @@ The exact way the `content` attribute should be parsed (notably, for error handl ### Bibliography -- [Understanding Success Criterion 1.4.4: Resize text](https://www.w3.org/WAI/WCAG21/Understanding/resize-text) -- [Understanding Success Criterion 1.4.10: Reflow](https://www.w3.org/WAI/WCAG21/Understanding/reflow) +- [Understanding Success Criterion 1.4.4: Resize text](https://www.w3.org/WAI/WCAG22/Understanding/resize-text) +- [Understanding Success Criterion 1.4.10: Reflow](https://www.w3.org/WAI/WCAG22/Understanding/reflow) - [HTML Specification - The `meta` element][meta] - [The initial-scale, minimum-scale, and maximum-scale properties][maximum-scale] - [The user-scalable property][user-scalable] @@ -375,13 +375,13 @@ This viewport `meta` element does not prevent user scaling because it does not s ``` [attribute value]: #attribute-value 'Definition of attribute value' -[content]: https://www.w3.org/TR/WCAG21/#dfn-content 'content (Web content)' +[content]: https://www.w3.org/TR/WCAG22/#dfn-content 'content (Web content)' [css pixels]: https://www.w3.org/TR/css3-values/#reference-pixel 'CSS 3 definition, reference pixel' [descriptor translation]: https://www.w3.org/TR/css-device-adapt-1/#translate-meta-to-at-viewport 'Translations of the content attribute into @viewport descriptors' [meta]: https://html.spec.whatwg.org/#the-meta-element 'The meta element' [maximum-scale]: https://www.w3.org/TR/css-device-adapt-1/#min-scale-max-scale 'The initial-scale, minimum-scale, and maximum-scale properties' -[page]: https://www.w3.org/TR/WCAG21/#dfn-web-page-s 'Web page' -[sc144]: https://www.w3.org/TR/WCAG21/#resize-text 'WCAG 2.1 Success Criterion 1.4.4 Resize text' -[sc1410]: https://www.w3.org/TR/WCAG21/#reflow 'WCAG 2.1 Success Criterion 1.4.10 Reflow' +[page]: https://www.w3.org/TR/WCAG22/#dfn-web-page-s 'Web page' +[sc144]: https://www.w3.org/TR/WCAG22/#resize-text 'WCAG 2.2 Success Criterion 1.4.4 Resize text' +[sc1410]: https://www.w3.org/TR/WCAG22/#reflow 'WCAG 2.2 Success Criterion 1.4.10 Reflow' [user-scalable]: https://www.w3.org/TR/css-device-adapt-1/#user-scalable 'The user-scalable property' [visible]: #visible 'Definition of visible' diff --git a/_rules/non-visual-reference-alternative-9bd38c.md b/_rules/non-visual-reference-alternative-9bd38c.md index 9cc77d8b904..f054381ad0e 100755 --- a/_rules/non-visual-reference-alternative-9bd38c.md +++ b/_rules/non-visual-reference-alternative-9bd38c.md @@ -62,10 +62,10 @@ The identified web content does not have to be positioned on the same web page a ### Bibliography -- [WCAG 2.1 - Understanding Success Criterion 1.3.3: Sensory Characteristics](https://www.w3.org/WAI/WCAG21/Understanding/sensory-characteristics.html) -- [G96: Providing textual identification of items that otherwise rely only on sensory information to be understood](https://www.w3.org/WAI/WCAG21/Techniques/general/G96) -- [F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location](https://www.w3.org/WAI/WCAG21/Techniques/failures/F14) -- [F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information](https://www.w3.org/WAI/WCAG21/Techniques/failures/F26) +- [WCAG 2.2 - Understanding Success Criterion 1.3.3: Sensory Characteristics](https://www.w3.org/WAI/WCAG22/Understanding/sensory-characteristics.html) +- [G96: Providing textual identification of items that otherwise rely only on sensory information to be understood](https://www.w3.org/WAI/WCAG22/Techniques/general/G96) +- [F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location](https://www.w3.org/WAI/WCAG22/Techniques/failures/F14) +- [F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information](https://www.w3.org/WAI/WCAG22/Techniques/failures/F26) ## Test Cases @@ -492,13 +492,13 @@ This document contains no [text node][] that is either [visible][] or [included [accessible name]: #accessible-name 'Definition of Accessible Name' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' -[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationships' -[sc133]: https://www.w3.org/TR/WCAG21/#sensory-characteristics 'Success Criterion 1.3.3 Sensory Characteristics' +[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationships' +[sc133]: https://www.w3.org/TR/WCAG22/#sensory-characteristics 'Success Criterion 1.3.3 Sensory Characteristics' [text node]: https://dom.spec.whatwg.org/#text 'Specification of Text Node' [visible]: #visible 'Definition of Visible' [visible text content]: #visible-text-content 'Definition of Visible Text Content' [visual reference words]: #visual-reference-words 'Definition of Visual Reference Words' [visual reference word]: #visual-reference-words 'Definition of Visual Reference Words' -[text]: https://www.w3.org/TR/WCAG21/#dfn-text 'WCAG definition of Text' -[web content]: https://www.w3.org/TR/WCAG21/#dfn-content 'WCAG definition of Web Content' -[web page]: https://www.w3.org/TR/WCAG21/#dfn-web-page-s 'WCAG definition of Web Page' +[text]: https://www.w3.org/TR/WCAG22/#dfn-text 'WCAG definition of Text' +[web content]: https://www.w3.org/TR/WCAG22/#dfn-content 'WCAG definition of Web Content' +[web page]: https://www.w3.org/TR/WCAG22/#dfn-web-page-s 'WCAG definition of Web Page' diff --git a/_rules/object-has-accessible-name-8fc3b6.md b/_rules/object-has-accessible-name-8fc3b6.md index 9805075f53a..f5e7cdb189f 100644 --- a/_rules/object-has-accessible-name-8fc3b6.md +++ b/_rules/object-has-accessible-name-8fc3b6.md @@ -58,7 +58,7 @@ When the object resource is not loaded, the fallback content is rendered as show ### Bibliography -- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) ## Test Cases diff --git a/_rules/presentational-children-no-focusable-content-307n5z.md b/_rules/presentational-children-no-focusable-content-307n5z.md index 0385a7d541f..a5e541cbbd7 100755 --- a/_rules/presentational-children-no-focusable-content-307n5z.md +++ b/_rules/presentational-children-no-focusable-content-307n5z.md @@ -48,8 +48,8 @@ Elements with a [semantic role][] that has [presentational children][] will not ### Bibliography -- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships) -- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) - [WAI-ARIA 1.2 Presentational Children][presentational children] - [Element with aria-hidden has no focusable content](aria-hidden-no-focusable-content-6cfa84.md) diff --git a/_rules/printable-characters-shortcut-ffbc54.md b/_rules/printable-characters-shortcut-ffbc54.md index a7d44ed4aa6..d5fe63d00bf 100644 --- a/_rules/printable-characters-shortcut-ffbc54.md +++ b/_rules/printable-characters-shortcut-ffbc54.md @@ -47,15 +47,15 @@ Currently [keyboard events][keyboard event] only support the types `keydown` and ## Background The [instruments][instrument] used to pass this rule (if any), must meet all level A Success Criteria in order to fully satisfy [Success Criterion 2.1.4: Character Key Shortcuts][sc2.1.4]. These extra requirements are left out of this rule, and should be tested separately. -This rule allows [changes to the content][changes in content] when a [user interface component](https://www.w3.org/TR/WCAG21/#dfn-user-interface-components) has focus to meet the "Active only on focus" requirement from [Success Criterion 2.1.4][sc2.1.4]. As explained in the [Event dispatch and DOM event flow section](https://www.w3.org/TR/uievents/#event-flow) of the [UI Events Working Draft](https://www.w3.org/TR/uievents/), each [keyboard event][] is dispatched to an [event target][]. The [event target][] is the element that has focus. As such, the "Active only on focus" requirement from [Success Criterion 2.1.4][sc2.1.4] is implied by saying that the [event target][] is an [inheriting semantic][] `widget`. +This rule allows [changes to the content][changes in content] when a [user interface component](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components) has focus to meet the "Active only on focus" requirement from [Success Criterion 2.1.4][sc2.1.4]. As explained in the [Event dispatch and DOM event flow section](https://www.w3.org/TR/uievents/#event-flow) of the [UI Events Working Draft](https://www.w3.org/TR/uievents/), each [keyboard event][] is dispatched to an [event target][]. The [event target][] is the element that has focus. As such, the "Active only on focus" requirement from [Success Criterion 2.1.4][sc2.1.4] is implied by saying that the [event target][] is an [inheriting semantic][] `widget`. The "Turn off" and "Remap" requirements from [Success Criterion 2.1.4][sc2.1.4] are combined in the **disable/remap** item of the Expectation section. For the disable requirement, [changes in content][] that are made through [keyboard events][keyboard event] with a [printable character][] value for the `key` attribute and a `getModifierState` return value of `false` for each of the [valid modifier keys][] effectively need to be [blocked][blocked event] (in other words, turned off or disabled). The remap requirement unblocks the events if the `getModifierState` query returns `true` for at least one of the [valid modifier keys][]. Once the `getModifierState` returns `true` for at least one of the [valid modifier keys][] of a [keyboard event][], such [keyboard event][] is no longer applicable for the rule and it passes the "Remap" requirement from [Success Criterion 2.1.4][sc2.1.4]. ### Bibliography - [Understanding Success Criterion 2.1.4: Character Key Shortcuts][sc2.1.4] -- [G217 Providing a mechanism to allow users to remap or turn off character key shortcuts](https://www.w3.org/WAI/WCAG21/Techniques/general/G217) -- [F99 Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that cannot be turned off or remapped](https://www.w3.org/WAI/WCAG21/Techniques/failures/F99) +- [G217 Providing a mechanism to allow users to remap or turn off character key shortcuts](https://www.w3.org/WAI/WCAG22/Techniques/general/G217) +- [F99 Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that cannot be turned off or remapped](https://www.w3.org/WAI/WCAG22/Techniques/failures/F99) ## Test Cases @@ -378,6 +378,6 @@ This [HTML document][] has a [keyboard event][] [dispatched][] to an [event targ [legacy keyboard events]: https://www.w3.org/TR/uievents/#legacy-keyboardevent-events [printable character]: #printable-characters 'Definition of printable characters' [same key events]: #same-key-events 'Definition of same key events' -[sc2.1.4]: https://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html +[sc2.1.4]: https://www.w3.org/WAI/WCAG22/Understanding/character-key-shortcuts.html [set of clearly labeled instruments]: #set-of-clearly-labeled-instruments 'Definition of set of clearly labeled instruments' [valid modifier keys]: https://www.w3.org/TR/uievents-key/#keys-modifier 'Definition of modifier keys' diff --git a/_rules/role-required-states-and-properties-4e8ab6.md b/_rules/role-required-states-and-properties-4e8ab6.md index 0384762a134..0d98e6f2f25 100755 --- a/_rules/role-required-states-and-properties-4e8ab6.md +++ b/_rules/role-required-states-and-properties-4e8ab6.md @@ -55,7 +55,7 @@ This rule is testing author built components that specify [explicit semantic rol ### Bibliography -- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA5) +- [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA5) - [WAI-ARIA required states and properties](https://www.w3.org/TR/wai-aria-1.2/#requiredState) - [RFC 3986](https://www.ietf.org/rfc/rfc3986.txt) diff --git a/_rules/scrollable-element-keyboard-accessible-0ssw9k.md b/_rules/scrollable-element-keyboard-accessible-0ssw9k.md index 1ecffcd1c78..c23d3f03d32 100755 --- a/_rules/scrollable-element-keyboard-accessible-0ssw9k.md +++ b/_rules/scrollable-element-keyboard-accessible-0ssw9k.md @@ -59,8 +59,8 @@ This rule only applies to elements who scroll content in the same document. Elem ### Bibliography -- [Understanding Success Criterion 2.1.1: Keyboard](https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html) -- [G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG21/Techniques/general/G202) +- [Understanding Success Criterion 2.1.1: Keyboard](https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html) +- [G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G202) ## Test Cases @@ -92,7 +92,7 @@ This [scrollable][] `section` element contains a link that is included in [seque ```html

- + WCAG 2.1 Abstract

@@ -186,7 +186,7 @@ This `section` element has a [scroll distance][scrollable] of 0 in both directio ```html

- + WCAG 2.1 Abstract

@@ -199,7 +199,7 @@ This `section` element is not [scrollable][] because it has a [computed][] [over ```html

- + WCAG 2.1 Abstract

@@ -251,7 +251,7 @@ This `section` element has a [horizontal scroll distance][scrollable] that is le This `iframe` element is not a scrollable element, but instead contains a nested browsing context that is scrollable. These must be tested separately. ```html - + ``` [visible]: #visible @@ -268,6 +268,6 @@ This `iframe` element is not a scrollable element, but instead contains a nested [padding-right]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-right [padding-top]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-top [padding-bottom]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-bottom -[purely decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration -[success criterion 2.1.1 keyboard]: https://www.w3.org/TR/WCAG21/#keyboard +[purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration +[success criterion 2.1.1 keyboard]: https://www.w3.org/TR/WCAG22/#keyboard [html element]: #namespaced-element diff --git a/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md b/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md index f561f0d8d97..e9bb08cddeb 100755 --- a/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md +++ b/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md @@ -116,7 +116,7 @@ Each of these three [focusable][] elements has a blue square in front of it when class="no-focus-default" onfocus="toggleActivation('indicator-wcag'); toggleActivation('indicator-w3c')" onblur="toggleActivation('indicator-wcag'); toggleActivation('indicator-w3c')" - href="https://www.w3.org/TR/WCAG21/" + href="https://www.w3.org/TR/WCAG22/" >WCAG @@ -158,17 +158,17 @@ None of the [focusable][] elements in this document are part of [sequential focu ```html ACT rules -WCAG +WCAG ``` [focusable]: #focusable 'Definition of Focusable' [focused]: #focused 'Definition of Focused' -[sc247]: https://www.w3.org/TR/WCAG21/#focus-visible 'Success Criterion 2.4.7 Focus Visible' +[sc247]: https://www.w3.org/TR/WCAG22/#focus-visible 'Success Criterion 2.4.7 Focus Visible' [sc2411]: https://www.w3.org/TR/WCAG22/#focus-appearance 'Success Criterion 2.4.11 Focus Appearance' [sc2412]: https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum 'Success Criterion 2.4.12 Focus Not Obscured (Minimum)' [scrolling area]: https://drafts.csswg.org/cssom-view/#scrolling-area 'CSS specification of Scrolling Area' [sequential focus navigation]: https://html.spec.whatwg.org/#sequential-focus-navigation 'HTML specification of Sequential focus navigation' -[usc247]: https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html 'Understanding Success Criterion 2.4.7: Focus Visible' +[usc247]: https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html 'Understanding Success Criterion 2.4.7: Focus Visible' [usc2411]: https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html 'Understanding Success Criterion 2.4.11: Focus Appearance' [usc2412]: https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html 'Understanding Success Criterion 2.4.12: Focus Not Obscured (Minimum)' [viewport]: https://drafts.csswg.org/css2/#viewport 'CSS definition of Viewport' diff --git a/_rules/table-header-cell-has-assigned-cells-d0f69e.md b/_rules/table-header-cell-has-assigned-cells-d0f69e.md index d7c896a4a2e..ac2beeef340 100755 --- a/_rules/table-header-cell-has-assigned-cells-d0f69e.md +++ b/_rules/table-header-cell-has-assigned-cells-d0f69e.md @@ -17,7 +17,7 @@ input_aspects: acknowledgments: authors: - Audrey Maniez - - Helen Burge + - Helen Burge - Jey Nandakumar funding: - WAI-Tools @@ -52,7 +52,7 @@ The roles inheriting from `cell` are `columnheader`, `gridcell`, and `rowheader` ### Bibliography - [Understanding Success Criterion 1.3.1: Information and relationships][sc1.3.1] -- [H43: Using id and headers attributes to associate data cells with header cells in data tables](https://www.w3.org/WAI/WCAG21/Techniques/html/H43) +- [H43: Using id and headers attributes to associate data cells with header cells in data tables](https://www.w3.org/WAI/WCAG22/Techniques/html/H43) - [Forming relationships between data cells and header cells][assigned] ## Test Cases @@ -347,13 +347,13 @@ This `th` element is part of a table which is not [included in the accessibility [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' [assigned]: https://html.spec.whatwg.org/multipage/tables.html#header-and-data-cell-semantics 'Forming relationships between data cells and header cells' -[cell]: https://www.w3.org/TR/wai-aria-1.1/#cell 'ARIA cell role' +[cell]: https://www.w3.org/TR/wai-aria-1.2/#cell 'ARIA cell role' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree' -[table]: https://www.w3.org/TR/wai-aria-1.1/#table 'ARIA table role' -[grid]: https://www.w3.org/TR/wai-aria-1.1/#grid 'ARIA grid role' -[columnheader]: https://www.w3.org/TR/wai-aria-1.1/#columnheader 'ARIA columnheader role' -[rowheader]: https://www.w3.org/TR/wai-aria-1.1/#rowheader 'ARIA rowheader role' +[table]: https://www.w3.org/TR/wai-aria-1.2/#table 'ARIA table role' +[grid]: https://www.w3.org/TR/wai-aria-1.2/#grid 'ARIA grid role' +[columnheader]: https://www.w3.org/TR/wai-aria-1.2/#columnheader 'ARIA columnheader role' +[rowheader]: https://www.w3.org/TR/wai-aria-1.2/#rowheader 'ARIA rowheader role' [explicit role]: #explicit-role 'Definition of Explicit Role' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' -[sc1.3.1]: https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html 'Understanding Success Criterion 1.3.1: Info and Relationships' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[sc1.3.1]: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html 'Understanding Success Criterion 1.3.1: Info and Relationships' [html element]: #namespaced-element diff --git a/_rules/table-headers-attribute-refer-to-data-cells-a25f45.md b/_rules/table-headers-attribute-refer-to-data-cells-a25f45.md index d8a076085db..4827ce44796 100755 --- a/_rules/table-headers-attribute-refer-to-data-cells-a25f45.md +++ b/_rules/table-headers-attribute-refer-to-data-cells-a25f45.md @@ -56,9 +56,9 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html) -- [H43: Using id and headers attributes to associate data cells with header cells in data tables](https://www.w3.org/WAI/WCAG21/Techniques/html/H43) -- [F90: Incorrectly associating table headers and content via the headers and id attributes](https://www.w3.org/WAI/WCAG21/Techniques/failures/F90) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) +- [H43: Using id and headers attributes to associate data cells with header cells in data tables](https://www.w3.org/WAI/WCAG22/Techniques/html/H43) +- [F90: Incorrectly associating table headers and content via the headers and id attributes](https://www.w3.org/WAI/WCAG22/Techniques/failures/F90) * `headers` attribute referencing elements that are non-existent or not in the table are ignored when [assigning header cells (step 3, first case, point 2)](https://html.spec.whatwg.org/multipage/tables.html#algorithm-for-assigning-header-cells). * `headers` attribute referencing to the cell itself are ignored when [assigning header cells (step 3, first case, point 2)](https://html.spec.whatwg.org/multipage/tables.html#algorithm-for-assigning-header-cells). @@ -416,5 +416,5 @@ This `table` doesn't have a role of `table`, `grid` or `treegrid`. [set of space separated tokens]: https://html.spec.whatwg.org/#set-of-space-separated-tokens 'Space separated tokens' [`table`]: https://html.spec.whatwg.org/#concept-table 'Definition of table' [computes an adequate fallback header]: https://html.spec.whatwg.org/multipage/tables.html#header-and-data-cell-semantics 'Forming relationships between data cells and header cells' -[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships 'WCAG 2.1 success criterion 1.3.1 Info and Relationships' +[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships 'WCAG 2.2 success criterion 1.3.1 Info and Relationships' [semantic role]: #semantic-role 'Definition of semantic role' diff --git a/_rules/text-contrast-afw4f7.md b/_rules/text-contrast-afw4f7.md index b6edb3d368c..5b74a6e332b 100755 --- a/_rules/text-contrast-afw4f7.md +++ b/_rules/text-contrast-afw4f7.md @@ -59,11 +59,11 @@ When the text color or background color is not specified in the web page, colors ### Bibliography -- [Understanding Success Criterion 1.4.3: Contrast (Minimum)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html) -- [Understanding Success Criterion 1.4.6: Contrast (Enhanced)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced.html) -- [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG21/Techniques/general/G18) -- [G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG21/Techniques/general/G145) -- [F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text)](https://www.w3.org/WAI/WCAG21/Techniques/failures/F83) +- [Understanding Success Criterion 1.4.3: Contrast (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html) +- [Understanding Success Criterion 1.4.6: Contrast (Enhanced)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-enhanced.html) +- [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG22/Techniques/general/G18) +- [G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG22/Techniques/general/G145) +- [F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text)](https://www.w3.org/WAI/WCAG22/Techniques/failures/F83) - [CSS Scoping Module Level 1 (Editor's Draft)](https://drafts.csswg.org/css-scoping/) ## Test Cases @@ -417,20 +417,20 @@ This text is part of a [disabled][] widget because it is a child of an element w [accessible name]: #accessible-name 'Definition of Accessible Name' [ancestor]: https://dom.spec.whatwg.org/#concept-shadow-including-ancestor 'DOM, ancestor, 2020/07/23' -[assistive technology]: https://www.w3.org/TR/WCAG21/#dfn-assistive-technologies 'WCAG definition of Assistive Technologies' +[assistive technology]: https://www.w3.org/TR/WCAG22/#dfn-assistive-technologies 'WCAG definition of Assistive Technologies' [background colors]: #background-colors-of-text 'Definition of Background color of text' [child]: https://dom.spec.whatwg.org/#concept-tree-child 'DOM, child, 2020/07/23' [disabled]: #disabled-element 'Definition of Disabled' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'CSS draft, flat tree, 2020/07/23' [foreground colors]: #foreground-colors-of-text 'Definition of Foreground color of text' [highest possible contrast]: #highest-possible-contrast 'Definition of Highest possible contrast' -[human language]: https://www.w3.org/TR/WCAG21/#dfn-human-language-s 'WCAG 2.1, Human language' +[human language]: https://www.w3.org/TR/WCAG22/#dfn-human-language-s 'WCAG 2.2, Human language' [large scale text]: #large-scale-text 'Definition of Large scale text' [origins]: https://www.w3.org/TR/css3-cascade/#cascading-origins 'CSS 3, origin' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'WAI-ARIA, Presentational Roles Conflict Resolution' -[purely decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG 2.1, Purely decorative' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'WAI-ARIA, Presentational Roles Conflict Resolution' +[purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG 2.2, Purely decorative' [text node]: https://dom.spec.whatwg.org/#text 'DOM, text node, 2020/07/23' -[sc143]: https://www.w3.org/TR/WCAG21/#contrast-minimum 'WCAG 2.1, Success criterion 1.4.3 Contrast (Minimum)' +[sc143]: https://www.w3.org/TR/WCAG22/#contrast-minimum 'WCAG 2.2, Success criterion 1.4.3 Contrast (Minimum)' [semantic role]: #semantic-role 'Definition of Semantic Role' [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' [user origin]: https://www.w3.org/TR/css3-cascade/#cascade-origin-user 'CSS 3, user origin' diff --git a/_rules/text-contrast-enhanced-09o5cg.md b/_rules/text-contrast-enhanced-09o5cg.md index c52fa2bfff2..7a30c9f135b 100644 --- a/_rules/text-contrast-enhanced-09o5cg.md +++ b/_rules/text-contrast-enhanced-09o5cg.md @@ -70,10 +70,10 @@ This rule is closely related to [success criterion 1.4.3 Contrast (Minimum)][sc1 ### Bibliography -- [Understanding Success Criterion 1.4.6: Contrast (Enhanced)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced.html) -- [G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG21/Techniques/general/G17) -- [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG21/Techniques/general/G18) -- [F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text)](https://www.w3.org/WAI/WCAG21/Techniques/failures/F83) +- [Understanding Success Criterion 1.4.6: Contrast (Enhanced)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-enhanced.html) +- [G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG22/Techniques/general/G17) +- [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG22/Techniques/general/G18) +- [F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text)](https://www.w3.org/WAI/WCAG22/Techniques/failures/F83) - [CSS Scoping Module Level 1 (Editor's Draft)](https://drafts.csswg.org/css-scoping/) ## Test Cases @@ -447,23 +447,23 @@ This text is part of a [disabled][] widget because it is a child of an element w [accessible name]: #accessible-name 'Definition of Accessible Name' [ancestor]: https://dom.spec.whatwg.org/#concept-shadow-including-ancestor 'DOM, ancestor, 2020/07/23' -[assistive technology]: https://www.w3.org/TR/WCAG21/#dfn-assistive-technologies 'WCAG definition of Assistive Technologies' +[assistive technology]: https://www.w3.org/TR/WCAG22/#dfn-assistive-technologies 'WCAG definition of Assistive Technologies' [background colors]: #background-colors-of-text 'Definition of Background color of text' [child]: https://dom.spec.whatwg.org/#concept-tree-child 'DOM, child, 2020/07/23' [disabled]: #disabled-element 'Definition of Disabled' [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'CSS draft, flat tree, 2020/07/23' [foreground colors]: #foreground-colors-of-text 'Definition of Foreground color of text' [highest possible contrast]: #highest-possible-contrast 'Definition of Highest possible contrast' -[human language]: https://www.w3.org/TR/WCAG21/#dfn-human-language-s 'WCAG 2.1, Human language' +[human language]: https://www.w3.org/TR/WCAG22/#dfn-human-language-s 'WCAG 2.2, Human language' [large scale text]: #large-scale-text 'Definition of Large scale text' [origins]: https://www.w3.org/TR/css3-cascade/#cascading-origins 'CSS 3, origin' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'WAI-ARIA, Presentational Roles Conflict Resolution' -[purely decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG 2.1, Purely decorative' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'WAI-ARIA, Presentational Roles Conflict Resolution' +[purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG 2.2, Purely decorative' [text node]: https://dom.spec.whatwg.org/#text 'DOM, text node, 2020/07/23' -[sc146]: https://www.w3.org/TR/WCAG21/#contrast-enhanced 'WCAG 2.1, Success criterion 1.4.6 Contrast (Enhanced)' +[sc146]: https://www.w3.org/TR/WCAG22/#contrast-enhanced 'WCAG 2.2, Success criterion 1.4.6 Contrast (Enhanced)' [semantic role]: #semantic-role 'Definition of Semantic role' [inheriting semantic]: #inheriting-semantic 'Definition of Inheriting Semantic Role' [user origin]: https://www.w3.org/TR/css3-cascade/#cascade-origin-user 'CSS 3, user origin' [visible]: #visible 'Definition of Visible' [html element]: #namespaced-element -[sc143]: https://www.w3.org/TR/WCAG21/#contrast-minimum +[sc143]: https://www.w3.org/TR/WCAG22/#contrast-minimum diff --git a/_rules/video-alternative-for-auditory-eac66b.md b/_rules/video-alternative-for-auditory-eac66b.md index 20899b858ce..20de5710d73 100755 --- a/_rules/video-alternative-for-auditory-eac66b.md +++ b/_rules/video-alternative-for-auditory-eac66b.md @@ -62,10 +62,10 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.2.2: Captions (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded) -- [G93: Providing open (always visible) captions](https://www.w3.org/WAI/WCAG21/Techniques/general/G93) -- [G87: Providing closed captions](https://www.w3.org/WAI/WCAG21/Techniques/general/G87) -- [H95: Using the track element to provide captions](https://www.w3.org/WAI/WCAG21/Techniques/html/H95) +- [Understanding Success Criterion 1.2.2: Captions (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/captions-prerecorded) +- [G93: Providing open (always visible) captions](https://www.w3.org/WAI/WCAG22/Techniques/general/G93) +- [G87: Providing closed captions](https://www.w3.org/WAI/WCAG22/Techniques/general/G87) +- [H95: Using the track element to provide captions](https://www.w3.org/WAI/WCAG22/Techniques/html/H95) ## Test Cases diff --git a/_rules/video-alternative-for-visual-c5a4ea.md b/_rules/video-alternative-for-visual-c5a4ea.md index 8987c059bb2..8da247c9a1d 100755 --- a/_rules/video-alternative-for-visual-c5a4ea.md +++ b/_rules/video-alternative-for-visual-c5a4ea.md @@ -70,16 +70,16 @@ For each test target, the [outcome](#outcome) of at least one of the following r ## Accessibility Support -The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/html/H96) can not be relied upon to conform to [1.2.3: Audio Description or Media Alternative (Prerecorded)][sc123]. +The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/html/H96) can not be relied upon to conform to [1.2.3: Audio Description or Media Alternative (Prerecorded)][sc123]. ## Background ### Bibliography -- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.html) -- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G78) -- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G173) -- [G8: Providing a movie with extended audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G8) +- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded.html) +- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) +- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G173) +- [G8: Providing a movie with extended audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G8) ## Test Cases @@ -214,4 +214,4 @@ A video element that is not [visible][]. ``` [visible]: #visible 'Definition of visible' -[sc123]: https://www.w3.org/TR/WCAG21/#audio-description-or-media-alternative-prerecorded 'WCAG 2.1, Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)' +[sc123]: https://www.w3.org/TR/WCAG22/#audio-description-or-media-alternative-prerecorded 'WCAG 2.2, Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)' diff --git a/_rules/video-as-media-alternative-ab4d13.md b/_rules/video-as-media-alternative-ab4d13.md index 96f55c2a14b..d6b4e34cc5e 100755 --- a/_rules/video-as-media-alternative-ab4d13.md +++ b/_rules/video-as-media-alternative-ab4d13.md @@ -44,9 +44,9 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded) -- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded) -- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G78) +- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded) +- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded) +- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) ## Test Cases diff --git a/_rules/video-audio-description-1ea59c.md b/_rules/video-audio-description-1ea59c.md index 443ce518722..bef49f87699 100755 --- a/_rules/video-audio-description-1ea59c.md +++ b/_rules/video-audio-description-1ea59c.md @@ -56,10 +56,10 @@ There are only a few implementations of video players (without third party techn ### Bibliography -- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded) -- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G78) -- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G173) -- [G8: Providing a movie with extended audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G8) +- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded) +- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) +- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G173) +- [G8: Providing a movie with extended audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G8) ## Test Cases diff --git a/_rules/video-captions-f51b46.md b/_rules/video-captions-f51b46.md index a36044157c7..fe969269b0e 100755 --- a/_rules/video-captions-f51b46.md +++ b/_rules/video-captions-f51b46.md @@ -43,7 +43,7 @@ This rule applies to every [non-streaming](#non-streaming-media-element) `video` ## Expectation -For each test target, audio information that is not conveyed visually in the video, is available through [captions](https://www.w3.org/TR/WCAG21/#dfn-captions). +For each test target, audio information that is not conveyed visually in the video, is available through [captions](https://www.w3.org/TR/WCAG22/#dfn-captions). **Note:** Captions can be either embedded in the video file itself or can be made available trough a separate track. @@ -59,10 +59,10 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.2.2: Captions (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded) -- [G93: Providing open (always visible) captions](https://www.w3.org/WAI/WCAG21/Techniques/general/G93) -- [G87: Providing closed captions](https://www.w3.org/WAI/WCAG21/Techniques/general/G87) -- [H95: Using the track element to provide captions](https://www.w3.org/WAI/WCAG21/Techniques/html/H95) +- [Understanding Success Criterion 1.2.2: Captions (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/captions-prerecorded) +- [G93: Providing open (always visible) captions](https://www.w3.org/WAI/WCAG22/Techniques/general/G93) +- [G87: Providing closed captions](https://www.w3.org/WAI/WCAG22/Techniques/general/G87) +- [H95: Using the track element to provide captions](https://www.w3.org/WAI/WCAG22/Techniques/html/H95) ## Test Cases diff --git a/_rules/video-description-track-f196ce.md b/_rules/video-description-track-f196ce.md index e6f181b155d..228577925a5 100755 --- a/_rules/video-description-track-f196ce.md +++ b/_rules/video-description-track-f196ce.md @@ -57,10 +57,10 @@ This means that the rule can only provide a pass for these success criteria if a ### Bibliography -- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded) -- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded) -- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G78) -- [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/html/H96) +- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded) +- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded) +- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) +- [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/html/H96) ## Test Cases diff --git a/_rules/video-only-alternative-for-visual-c3232f.md b/_rules/video-only-alternative-for-visual-c3232f.md index c9ee633518d..7be3b45db54 100755 --- a/_rules/video-only-alternative-for-visual-c3232f.md +++ b/_rules/video-only-alternative-for-visual-c3232f.md @@ -60,15 +60,15 @@ For each test target, the [outcome](#outcome) of at least one of the following r ## Accessibility Support -The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/html/H96) can not be relied upon to conform to [1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/TR/WCAG21/#audio-only-and-video-only-prerecorded). +The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/html/H96) can not be relied upon to conform to [1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/TR/WCAG22/#audio-only-and-video-only-prerecorded). ## Background ### Bibliography -- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) -- [G159: Providing an alternative for time-based media for video-only content](https://www.w3.org/WAI/WCAG21/Techniques/general/G159.html) -- [G166: Providing audio that describes the important video content and describing it as such](https://www.w3.org/WAI/WCAG21/Techniques/general/G166.html) +- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) +- [G159: Providing an alternative for time-based media for video-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G159.html) +- [G166: Providing audio that describes the important video content and describing it as such](https://www.w3.org/WAI/WCAG22/Techniques/general/G166.html) ## Test Cases diff --git a/_rules/video-only-as-media-alternative-fd26cf.md b/_rules/video-only-as-media-alternative-fd26cf.md index 5fcc3fabff0..71a749f1549 100755 --- a/_rules/video-only-as-media-alternative-fd26cf.md +++ b/_rules/video-only-as-media-alternative-fd26cf.md @@ -42,11 +42,11 @@ There are no accessibility support issues known. ## Background -The term [label](https://www.w3.org/TR/WCAG21/#dfn-labels) used in expectations 2 and 3 does not refer to the `label` element. +The term [label](https://www.w3.org/TR/WCAG22/#dfn-labels) used in expectations 2 and 3 does not refer to the `label` element. ### Bibliography -- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) +- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) ## Test Cases diff --git a/_rules/video-only-audio-track-d7ba54.md b/_rules/video-only-audio-track-d7ba54.md index 7c988b2174d..e912d77bcb6 100755 --- a/_rules/video-only-audio-track-d7ba54.md +++ b/_rules/video-only-audio-track-d7ba54.md @@ -45,8 +45,8 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) -- [G166: Providing audio that describes the important video content and describing it as such](https://www.w3.org/WAI/WCAG21/Techniques/general/G166) +- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) +- [G166: Providing audio that describes the important video content and describing it as such](https://www.w3.org/WAI/WCAG22/Techniques/general/G166) ## Test Cases diff --git a/_rules/video-only-description-track-ac7dc6.md b/_rules/video-only-description-track-ac7dc6.md index 342ce4d3637..3b7d5e21e9e 100755 --- a/_rules/video-only-description-track-ac7dc6.md +++ b/_rules/video-only-description-track-ac7dc6.md @@ -50,8 +50,8 @@ Multiple description `track` elements may be useful for different languages, but ### Bibliography -- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) -- [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/html/H96) +- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) +- [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/html/H96) ## Test Cases diff --git a/_rules/video-only-transcript-ee13b5.md b/_rules/video-only-transcript-ee13b5.md index 4ffc9090366..91d134dc0f0 100755 --- a/_rules/video-only-transcript-ee13b5.md +++ b/_rules/video-only-transcript-ee13b5.md @@ -48,12 +48,12 @@ There are no accessibility support issues known. ## Background -A "text transcript" in the context of this rule is defined in WCAG 2 as an [alternative for time based media](https://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media). +A "text transcript" in the context of this rule is defined in WCAG 2 as an [alternative for time based media](https://www.w3.org/TR/WCAG22/#dfn-alternative-for-time-based-media). ### Bibliography -- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded) -- [G159: Providing an alternative for time-based media for video-only content](https://www.w3.org/WAI/WCAG21/Techniques/general/G159) +- [Understanding Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) +- [G159: Providing an alternative for time-based media for video-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G159) ## Test Cases diff --git a/_rules/video-strict-alternative-for-visual-1ec09b.md b/_rules/video-strict-alternative-for-visual-1ec09b.md index 765b2ba76f6..bb83b4d63e4 100755 --- a/_rules/video-strict-alternative-for-visual-1ec09b.md +++ b/_rules/video-strict-alternative-for-visual-1ec09b.md @@ -57,16 +57,16 @@ For each test target, the [outcome](#outcome) of at least one of the following r ## Accessibility Support -The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/html/H96) can not be relied upon to conform to [1.2.5: Audio Description (Prerecorded)](https://www.w3.org/TR/WCAG21/#audio-description-prerecorded). +The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/html/H96) can not be relied upon to conform to [1.2.5: Audio Description (Prerecorded)](https://www.w3.org/TR/WCAG22/#audio-description-prerecorded). ## Background ### Bibliography -- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.html) -- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G78) -- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G173) -- [G8: Providing a movie with extended audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G8) +- [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded.html) +- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) +- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G173) +- [G8: Providing a movie with extended audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G8) ## Test Cases diff --git a/_rules/video-transcript-1a02b0.md b/_rules/video-transcript-1a02b0.md index ec22c23733f..bf66b19e91b 100755 --- a/_rules/video-transcript-1a02b0.md +++ b/_rules/video-transcript-1a02b0.md @@ -43,7 +43,7 @@ This rule applies to every [non-streaming](#non-streaming-media-element) `video` The visual information of each test target is available through a text transcript that is [visible][], [included in the accessibility tree][], and is either on the page or linked. -**Note:** A "text transcript" in the context of this rule is defined in WCAG 2 as an [alternative for time based media](https://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media). +**Note:** A "text transcript" in the context of this rule is defined in WCAG 2 as an [alternative for time based media](https://www.w3.org/TR/WCAG22/#dfn-alternative-for-time-based-media). ## Assumptions @@ -57,11 +57,11 @@ There are no accessibility support issues known. ### Bibliography -- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded) -- [Understanding Success Criterion 1.2.8: Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG21/Understanding/media-alternative-prerecorded) -- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G78) -- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG21/Techniques/general/G173) -- [G203: Using a static text alternative to describe a talking head video](https://www.w3.org/WAI/WCAG21/Techniques/general/G203) +- [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded) +- [Understanding Success Criterion 1.2.8: Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/media-alternative-prerecorded) +- [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) +- [G173: Providing a version of a movie with audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G173) +- [G203: Using a static text alternative to describe a talking head video](https://www.w3.org/WAI/WCAG22/Techniques/general/G203) ## Test Cases diff --git a/_rules/visible-label-in-accessible-name-2ee8b8.md b/_rules/visible-label-in-accessible-name-2ee8b8.md index 0b5d195890c..570437a592c 100755 --- a/_rules/visible-label-in-accessible-name-2ee8b8.md +++ b/_rules/visible-label-in-accessible-name-2ee8b8.md @@ -57,7 +57,7 @@ The understanding document of [2.5.3 Label in Name][understand253] use the term ### Bibliography - [Understanding Success Criterion 2.5.3: Label in Name][understand253] -- [G208: Including the text of the visible label as part of the accessible name](https://www.w3.org/WAI/WCAG21/Techniques/general/G208) +- [G208: Including the text of the visible label as part of the accessible name](https://www.w3.org/WAI/WCAG22/Techniques/general/G208) ## Test Cases @@ -137,7 +137,7 @@ This button has [visible][] text that is only partially contained within the [ac #### Failed Example 3 -This link has [visible][] text with mathematical symbols, that does not match the [accessible name][] because the mathematical symbols were written out in the accessible name. This is [explicitly mentioned in WCAG](https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#mathematical-expressions-and-formulae). +This link has [visible][] text with mathematical symbols, that does not match the [accessible name][] because the mathematical symbols were written out in the accessible name. This is [explicitly mentioned in WCAG](https://www.w3.org/WAI/WCAG22/Understanding/label-in-name#mathematical-expressions-and-formulae). ```html Proof of 2×2=4 @@ -198,13 +198,13 @@ This link has no [visible text content][]. [accessible name]: #accessible-name 'Definition of accessible name' [match characters]: #matching-characters 'Definition of matching characters' -[non-text content]: https://www.w3.org/TR/WCAG21/#dfn-non-text-content 'WCAG Definition of Non-text content' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content 'WCAG Definition of Non-text content' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [semantic role]: #semantic-role 'Definition of Semantic role' -[supports name from content]: https://www.w3.org/TR/wai-aria-1.1/#namefromcontent 'Definition of Supports name from contents' +[supports name from content]: https://www.w3.org/TR/wai-aria-1.2/#namefromcontent 'Definition of Supports name from contents' [visible]: #visible 'Definition of visible' [visible text content]: #visible-text-content 'Definition of Visible text content' [whitespace]: #whitespace 'Definition of Whitespace' -[widget role]: https://www.w3.org/TR/wai-aria-1.1/#widget_roles 'Definition of Widget role' +[widget role]: https://www.w3.org/TR/wai-aria-1.2/#widget_roles 'Definition of Widget role' [text nodes]: https://dom.spec.whatwg.org/#text 'DOM text, 2020/08/18' -[understand253]: https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html +[understand253]: https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html diff --git a/_rules/zoom-text-no-overflow-clipping-59br37.md b/_rules/zoom-text-no-overflow-clipping-59br37.md index 7895235adeb..c9506e26d43 100755 --- a/_rules/zoom-text-no-overflow-clipping-59br37.md +++ b/_rules/zoom-text-no-overflow-clipping-59br37.md @@ -43,13 +43,13 @@ Each test target is not [vertically clipped by overflow][vertically clipped] of ## Assumptions -If any of the following assumptions is true, failing this rule may not result in a failure of [success criterion 1.4.4 Resize text](https://www.w3.org/TR/WCAG21/#resize-text): +If any of the following assumptions is true, failing this rule may not result in a failure of [success criterion 1.4.4 Resize text](https://www.w3.org/TR/WCAG22/#resize-text): - There is no other mechanism for resizing text available on the page, that can be used to resize text to 200% without loss of information or functionality. This includes font resizing in the browser, or a javascript mechanism of resizing in the page. - [Text nodes][text node] can not be [horizontally][horizontally clipped] or [vertically clipped by overflow][vertically clipped] without loss of information, except for [text nodes][text node] with an [ancestor][] with `aria-hidden` set to `true`, or when specific styles have been applied to ensure text is clipped cleanly (text-overflow, line wrapping or hidden text). -- While [success criterion 1.4.4 Resize text](https://www.w3.org/TR/WCAG21/#resize-text) does not explicitly mention which viewport size has to be resized up to 200%, it is assumed that a [viewport size][] of 1280 by 1024 is applicable. A 1280 by 1024 [viewport size][] is explicitly mentioned under [success criterion 1.4.10 Reflow](https://www.w3.org/TR/WCAG21/#reflow). +- While [success criterion 1.4.4 Resize text](https://www.w3.org/TR/WCAG22/#resize-text) does not explicitly mention which viewport size has to be resized up to 200%, it is assumed that a [viewport size][] of 1280 by 1024 is applicable. A 1280 by 1024 [viewport size][] is explicitly mentioned under [success criterion 1.4.10 Reflow](https://www.w3.org/TR/WCAG22/#reflow). ## Accessibility Support @@ -61,8 +61,8 @@ When the [computed][] value of the `line-height` property is `normal`, the [used ### Bibliography -- [Understanding Success Criterion 1.4.4: Resize text](https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html) -- [G42: Using a technology that has commonly-available user agents that support zoom](https://www.w3.org/WAI/WCAG21/Techniques/general/G142) +- [Understanding Success Criterion 1.4.4: Resize text](https://www.w3.org/WAI/WCAG22/Understanding/resize-text.html) +- [G42: Using a technology that has commonly-available user agents that support zoom](https://www.w3.org/WAI/WCAG22/Techniques/general/G142) ## Test Cases diff --git a/pages/about.md b/pages/about.md index b5b66072261..ea9677c4afd 100644 --- a/pages/about.md +++ b/pages/about.md @@ -13,9 +13,9 @@ ACT-R is not set up to remove differences or impose changes on accessibility tes ## Why it matters -Accessibility compliance is becoming a legal requirement all around the world. This makes it increasingly important for organizations to understand exactly what they need to do to be compliant. Accessibility requirements such as WCAG 2.1 are often written in technology agnostic language. Interpretation exactly what those requirements mean for a specific technology requires interpretation. This interpretation can be different between different testers, between different organizations and in different regions around the world. +Accessibility compliance is becoming a legal requirement all around the world. This makes it increasingly important for organizations to understand exactly what they need to do to be compliant. Accessibility requirements such as WCAG 2.2 are often written in technology agnostic language. Interpretation exactly what those requirements mean for a specific technology requires interpretation. This interpretation can be different between different testers, between different organizations and in different regions around the world. -Knowing the interpretation that will be used to assess compliance to legal requirements is essential for organizations. Without this it is impossible for them to know whether or not they can be sued or fined. For those operating in different countries, consistency of that interpretation is also important. Inconsistent interpretations can lead to an overload of requirements, possibly even mutually exclusive requirements. The principle is simple, a website that is considered to conform to WCAG 2.1 Level AA in the US, should also be compliant in the EU. +Knowing the interpretation that will be used to assess compliance to legal requirements is essential for organizations. Without this it is impossible for them to know whether or not they can be sued or fined. For those operating in different countries, consistency of that interpretation is also important. Inconsistent interpretations can lead to an overload of requirements, possibly even mutually exclusive requirements. The principle is simple, a website that is considered to conform to WCAG 2.2 Level AA in the US, should also be compliant in the EU. ## Who We Are diff --git a/pages/design/definition-of-done.md b/pages/design/definition-of-done.md index 50d64fa0121..7e97eb886fe 100644 --- a/pages/design/definition-of-done.md +++ b/pages/design/definition-of-done.md @@ -15,14 +15,14 @@ The Definition of "Done" is a living document, and might change as the rule writ ## The Definition of "Done" - The relation between the rule and its accessibility requirements is as described in the [ACT Rules Format](https://www.w3.org/TR/act-rules-format/) under [Accessibility Requirements](https://www.w3.org/TR/act-rules-format/#structure-accessibility-requirements). - - Remember to also check that the rule is in line with supporting documentation, e.g. [Understanding WCAG 2.1](https://www.w3.org/WAI/WCAG21/Understanding/) and [Techniques for WCAG 2.1](https://www.w3.org/WAI/WCAG21/Techniques/) + - Remember to also check that the rule is in line with supporting documentation, e.g. [Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/) and [Techniques for WCAG 2.2](https://www.w3.org/WAI/WCAG22/Techniques/) - Applicability (for [atomic](https://www.w3.org/TR/act-rules-format/#test-applicability) / [composed rules](https://www.w3.org/TR/act-rules-format/#aggregation-applicability)) and Expectations (for [atomic](https://www.w3.org/TR/act-rules-format/#test-expectations) / [composed rules](https://www.w3.org/TR/act-rules-format/#aggregation-expectations)) live up to the requirements for these sections in the [ACT Rules Format](https://www.w3.org/TR/act-rules-format/) - Requirements for use of atomic and composed rules are followed, see [Rule Types](https://www.w3.org/TR/act-rules-format/#rule-types) in the [ACT Rules Format](https://www.w3.org/TR/act-rules-format/) - The rule follows the WCAG-ACT-RULES-CG [rule template](/design/rule-template.html), especially in relation to headings, styling, test case descriptions, etc. - The rule is using WCAG-ACT-RULES-CG [Glossary terms](https://act-rules.github.io/glossary) whenever possible. Be particularly aware of the following much-used algorithms: - For the Applicability, consider if the definitions [included in the accessibility tree](#included-in-the-accessibility-tree) and [visible on the page](#visible-on-the-page) should be used to narrow down the scope of the rule. - For the Applicability and Expectations, consider if the definition for [semantic role](#semantic-role) (including specifics of explicit and implicit semantic role) could be used to describe the targets of the rule. -- The rule links to any relevant documentation, e.g. [Understanding WCAG 2.1](https://www.w3.org/WAI/WCAG21/Understanding/) and [Techniques for WCAG 2.1](https://www.w3.org/WAI/WCAG21/Techniques/), specifications used, etc. +- The rule links to any relevant documentation, e.g. [Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/) and [Techniques for WCAG 2.2](https://www.w3.org/WAI/WCAG22/Techniques/), specifications used, etc. - The name of the rule is written in plain language, with capitalized initial letter - The file name of the rule follows the WCAG-ACT-RULES-CG naming convention - The rule has been spellchecked diff --git a/pages/design/rule-design.md b/pages/design/rule-design.md index 122d2e50939..1a3353779c5 100755 --- a/pages/design/rule-design.md +++ b/pages/design/rule-design.md @@ -76,10 +76,9 @@ Accessibility requirements should be listed as secondary if the requirement is r 1. The requirement is related to, but different from the rule. This often happens when there is overlap between two accessibility requirements. If this occurs, and some but not all the failed examples of the rule fail the accessibility requirement, the following text should be used: > This success criterion is **related** to this rule. This {is because / happens for} {reason}. Most failed examples satisfy this success criterion. +1) Atomic rules used in composite rules should list the requirements from the composite rule as "more strict" secondary requirements. -1. Atomic rules used in composite rules should list the requirements from the composite rule as "more strict" secondary requirements. - -Secondary requirements are optional and are only necessary when a requirement fails some of the passed examples or passes some of the failed examples. If there are no such examples, it is generally not necessary to include secondary requirements. +Secondary requirements are optional and are only necessary when a requirement fails some of the passed examples or passes some of the failed examples. If there are no such examples, it is generally not necessary to include secondary requirements. **Note**: When linking to WCAG or other sources that may have several versions, use the version number where the relevant requirement was first introduced. @@ -130,7 +129,7 @@ Many accessibility evaluations (especially automated tools) make assumptions abo While most assumptions relate to the rule itself, there are some assumptions that apply at other stages of the evaluation: -- It is assumed that the tested web page is the one that has to conform to WCAG 2.1 and that there is no [conforming alternative version](https://www.w3.org/TR/WCAG21/#dfn-conforming-alternate-version). +- It is assumed that the tested web page is the one that has to conform to WCAG 2.2 and that there is no [conforming alternative version](https://www.w3.org/TR/WCAG22/#dfn-conforming-alternate-version). - It is assumed that the following technologies are accessibility supported: HTML, CSS, WAI-ARIA, ... (See also WCAG-ACT-RULES-CG's [explanation on Accessibility Support](accessibility-support.html)). diff --git a/pages/design/rule-template.md b/pages/design/rule-template.md index 6f11233b2b8..e1b808f4387 100755 --- a/pages/design/rule-template.md +++ b/pages/design/rule-template.md @@ -67,11 +67,11 @@ There are no accessibility support issues known. ## Background -- Links to Techniques for WCAG 2.0 -- Latest version: Techniques for WCAG 2.0 W3C Working Group Note 8 April 2014 +- Links to Techniques for WCAG 2.2 +- Latest version: Techniques for WCAG 2.2 W3C Working Group Note 8 April 2014 - Link to other methodologies, test specifications or tools - Links to test cases, test suites, unit tests, etc. -- The WCAG 2.0 Techniques already contain examples and code snippets to illustrate which content passes or fails the test. Whenever possible WCAG-ACT-RULES-CG refers to those. Another source for test cases is the W3C Before and After Demonstration. +- The WCAG 2.2 Techniques already contain examples and code snippets to illustrate which content passes or fails the test. Whenever possible WCAG-ACT-RULES-CG refers to those. Another source for test cases is the W3C Before and After Demonstration. - Other references ## Test Cases @@ -187,11 +187,11 @@ There are no accessibility support issues known. ## Background -- Links to Techniques for WCAG 2.0 -- Latest version: Techniques for WCAG 2.0 W3C Working Group Note 8 April 2014 +- Links to Techniques for WCAG 2.2 +- Latest version: Techniques for WCAG 2.2 W3C Working Group Note 8 April 2014 - Link to other methodologies, test specifications or tools - Links to test cases, test suites, unit tests, etc. -- The WCAG 2.0 Techniques already contain examples and code snippets to illustrate which content passes or fails the test. Whenever possible WCAG-ACT-RULES-CG refers to those. Another source for test cases is the W3C Before and After Demonstration. +- The WCAG 2.2 Techniques already contain examples and code snippets to illustrate which content passes or fails the test. Whenever possible WCAG-ACT-RULES-CG refers to those. Another source for test cases is the W3C Before and After Demonstration. - Other references ## Test Cases diff --git a/pages/design/test-cases.md b/pages/design/test-cases.md index a6f3b662549..5901540acd3 100644 --- a/pages/design/test-cases.md +++ b/pages/design/test-cases.md @@ -37,11 +37,11 @@ When writing test cases, it is important to look at conditional logic. For examp ## Consistency With Accessibility Requirements -In order for the mapping of implementations to the rules to work, test cases need to be consistent with the accessibility requirement. This requires that **passed and inapplicable test cases should satisfy the accessibility requirements** of the rule, as well as the accessibility requirement of any composite rule this rule is designed for. Inapplicable conditions that do not satisfy the accessibility requirements should not be included. For example when testing [2.4.2 Page Titled](https://www.w3.org/TR/WCAG21/#page-titled), a rule that tests that titles are descriptive can not have an inapplicable example of a page that should have a title but does not. +In order for the mapping of implementations to the rules to work, test cases need to be consistent with the accessibility requirement. This requires that **passed and inapplicable test cases should satisfy the accessibility requirements** of the rule, as well as the accessibility requirement of any composite rule this rule is designed for. Inapplicable conditions that do not satisfy the accessibility requirements should not be included. For example when testing [2.4.2 Page Titled](https://www.w3.org/TR/WCAG22/#page-titled), a rule that tests that titles are descriptive can not have an inapplicable example of a page that should have a title but does not. Related to this, failed test cases should only fail the accessibility requirements for one reason. A failed test case for 4.1.2 Name, Role, Value should not have issues with both the accessible name, and the role. If the rule is about accessible names, the role and value must be correct. -Because mapping of implementations makes little difference between inapplicable and passed results, it is often better to have an inapplicable test case that "looks bad" but is actually satisfying the accessibility requirements. That way, tools that don't implement the Applicability correctly would fail this test case. For example, when testing [1.4.3 Contrast (minimum)](https://www.w3.org/TR/WCAG21/#contrast-minimum), a rule may be inapplicable to disabled buttons (since this matches the second exception in the Success Criterion); an inapplicable test case for this condition is better if it includes a disabled button whose text has a 2.0:1 contrast ratio with its background, than if it includes a disabled button with a 5.0:1 contrast ratio (in this second case, a tool that doesn't ignore disabled buttons would pass the test case and can still claim a correct implementation of the rule). Depending on the part of Applicability which a case tests, it is not always possible to have an inapplicable example that "looks bad". +Because mapping of implementations makes little difference between inapplicable and passed results, it is often better to have an inapplicable test case that "looks bad" but is actually satisfying the accessibility requirements. That way, tools that don't implement the Applicability correctly would fail this test case. For example, when testing [1.4.3 Contrast (minimum)](https://www.w3.org/TR/WCAG22/#contrast-minimum), a rule may be inapplicable to disabled buttons (since this matches the second exception in the Success Criterion); an inapplicable test case for this condition is better if it includes a disabled button whose text has a 2.0:1 contrast ratio with its background, than if it includes a disabled button with a 5.0:1 contrast ratio (in this second case, a tool that doesn't ignore disabled buttons would pass the test case and can still claim a correct implementation of the rule). Depending on the part of Applicability which a case tests, it is not always possible to have an inapplicable example that "looks bad". ## Small Test Cases diff --git a/pages/glossary/attribute-value.md b/pages/glossary/attribute-value.md index 893ede2b40c..49066d5ac5b 100755 --- a/pages/glossary/attribute-value.md +++ b/pages/glossary/attribute-value.md @@ -30,4 +30,4 @@ The attribute value of an [IDL attribute][] [numbers]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#numbers 'HTML Specification of Number Parsing' [reflect]: https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#reflecting-content-attributes-in-idl-attributes 'HTML specification of Reflecting Content Attributes in IDL Attributes' [space separated]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#space-separated-tokens 'HTML Specification of Space Separated Tokens' -[wai-aria specification]: https://www.w3.org/TR/wai-aria-1.1/#propcharacteristic_value 'WAI-ARIA Specification of States and Properties Value' +[wai-aria specification]: https://www.w3.org/TR/wai-aria-1.2/#propcharacteristic_value 'WAI-ARIA Specification of States and Properties Value' diff --git a/pages/glossary/clearly-labeled-location.md b/pages/glossary/clearly-labeled-location.md index 78f25320d46..ddb0bff3b4d 100644 --- a/pages/glossary/clearly-labeled-location.md +++ b/pages/glossary/clearly-labeled-location.md @@ -19,5 +19,5 @@ A [web page][] changes state when the [document's body][body] changes without a [url]: https://url.spec.whatwg.org/#concept-url [instrument]: #instrument-to-achieve-an-objective 'Definition of instrument to achieve an objective' [semantic role]: #semantic-role 'Definition of semantic role' -[text alternative]: https://www.w3.org/TR/WCAG21/#dfn-text-alternative 'Definition of text alternative' +[text alternative]: https://www.w3.org/TR/WCAG22/#dfn-text-alternative 'Definition of text alternative' [web page]: #web-page-html 'Definition of web page' diff --git a/pages/glossary/disabled-element.md b/pages/glossary/disabled-element.md index 2fb7ca2e185..6d4e3cff7ef 100755 --- a/pages/glossary/disabled-element.md +++ b/pages/glossary/disabled-element.md @@ -18,7 +18,7 @@ An element is _disabled_ when it has been rendered [inoperable][] in one or more This definition assumes that when the `aria-disabled` attribute is specified on an element, this element has also been disabled for users that do not rely on [assistive technology][]. For example, this can be done by disabling pointer events using the `pointer-events` property and by disabling keyboard interactions using the `tabindex` attribute. If this is not the case, the definition will produce incorrect results. [actually disabled]: https://html.spec.whatwg.org/multipage/semantics-other.html#concept-element-disabled 'HTML definition of Actually Disabled' -[assistive technology]: https://www.w3.org/TR/WCAG21/#dfn-assistive-technologies 'WCAG definition of Assistive Technologies' +[assistive technology]: https://www.w3.org/TR/WCAG22/#dfn-assistive-technologies 'WCAG definition of Assistive Technologies' [attribute value]: #attribute-value 'Definition of Attribute Value' [disabled pseudo-class]: https://drafts.csswg.org/selectors/#disabled-pseudo "CSS Selectors Level 4 (Editor's Draft), definition of the :disabled pseudo-class" [inoperable]: https://www.w3.org/TR/wai-aria/#dfn-operable diff --git a/pages/glossary/essential-text-presentation.md b/pages/glossary/essential-text-presentation.md index c3a2b390d3c..4b7d783aedb 100644 --- a/pages/glossary/essential-text-presentation.md +++ b/pages/glossary/essential-text-presentation.md @@ -21,4 +21,4 @@ Examples of text for which the presentation is essential include: 4. A bar chart, diagram, or maps with place names 5. An image showing a font, or showing the difference between font-weights -**Note:** WCAG includes a generic definition of "[essential](https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html#dfn-essential)". +**Note:** WCAG includes a generic definition of "[essential](https://www.w3.org/WAI/WCAG22/Understanding/images-of-text.html#dfn-essential)". diff --git a/pages/glossary/form-field-error-indicator.md b/pages/glossary/form-field-error-indicator.md index 6d2332e64bc..a96fee6bb87 100644 --- a/pages/glossary/form-field-error-indicator.md +++ b/pages/glossary/form-field-error-indicator.md @@ -15,6 +15,6 @@ Any [text][], or [non-text content][], or an element that has [presentation][] i **Note**: An error indicator can be a separate element in the page, but it can also be part of a form control. For example a red outline on a form control is often used to indicate an error. Not all red outlines are indicators of an error though. This depends on the presentation of the form control in relation to other elements on the page. -[non-text content]: https://www.w3.org/TR/WCAG21/#dfn-non-text-content -[presentation]: https://www.w3.org/TR/WCAG21/#dfn-presentation -[text]: https://www.w3.org/TR/WCAG21/#dfn-text +[non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content +[presentation]: https://www.w3.org/TR/WCAG22/#dfn-presentation +[text]: https://www.w3.org/TR/WCAG22/#dfn-text diff --git a/pages/glossary/highest-possible-contrast.md b/pages/glossary/highest-possible-contrast.md index f5243521602..4c17311215f 100644 --- a/pages/glossary/highest-possible-contrast.md +++ b/pages/glossary/highest-possible-contrast.md @@ -7,4 +7,4 @@ objective: true The highest value of the [contrast ratios][contrast ratio] between two sets of colors (A and B). That is, the highest [contrast ratio][] between either the darkest color in A and the brightest color in B, or the brightest color in A and the darkest color in B. -[contrast ratio]: https://www.w3.org/TR/WCAG21/#dfn-contrast-ratio 'WCAG definition of Contrast Ratio' +[contrast ratio]: https://www.w3.org/TR/WCAG22/#dfn-contrast-ratio 'WCAG definition of Contrast Ratio' diff --git a/pages/glossary/inheriting-semantic-role.md b/pages/glossary/inheriting-semantic-role.md index 81d57827ff4..2202de7ec2c 100644 --- a/pages/glossary/inheriting-semantic-role.md +++ b/pages/glossary/inheriting-semantic-role.md @@ -12,7 +12,7 @@ An element with an _inheriting semantic role_ of X is any element with a non-[ab **Example**: An "inheriting semantic link" is any element that either has the [semantic role][] of [`link`][link] or a [semantic role][] that inherits from the [`link`][link] role, such as [doc-biblioref][]. -[abstract]: https://www.w3.org/TR/wai-aria-1.1/#isAbstract 'ARIA Definition for Abstract Roles' +[abstract]: https://www.w3.org/TR/wai-aria-1.2/#isAbstract 'ARIA Definition for Abstract Roles' [semantic role]: #semantic-role 'Definition of Semantic Role' [link]: https://www.w3.org/TR/wai-aria/#link 'ARIA Definition of the link Role' [doc-biblioref]: https://www.w3.org/TR/dpub-aria-1.0/#doc-biblioref 'DPUB ARIA Definition of doc-biblioref' diff --git a/pages/glossary/insignificant.md b/pages/glossary/insignificant.md index 3bc649307ba..7be09f85857 100644 --- a/pages/glossary/insignificant.md +++ b/pages/glossary/insignificant.md @@ -10,4 +10,4 @@ Content that is neither [purely decorative][], nor required for understanding th **Example**: A picture of New York's Time Square may include taxis, a famous pizza restaurant, and theater advertisements, etc. None of these are purely decorative. They provide clues as to where the picture was taken. But neither are any of these required to understand the picture as a whole. Even if the picture itself is significant, the taxis in the picture are not. -[purely decorative]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG 2.1, Purely decorative' +[purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG 2.2, Purely decorative' diff --git a/pages/glossary/instrument.md b/pages/glossary/instrument.md index c9c692341fe..d7088b5d887 100755 --- a/pages/glossary/instrument.md +++ b/pages/glossary/instrument.md @@ -15,6 +15,6 @@ This definition is a more restrictive version of WCAG's definition of [mechanism [activated]: https://html.spec.whatwg.org/#activation [html element]: https://html.spec.whatwg.org/multipage/dom.html#htmlelement -[mechanism]: https://www.w3.org/TR/WCAG21/#dfn-mechanism 'WCAG Definition of Mechanism' -[sc211]: https://www.w3.org/TR/WCAG21/#keyboard 'Success Criterion 2.1.1 Keyboard' -[sc412]: https://www.w3.org/TR/WCAG21/#name-role-value 'Success Criterion 4.1.2 Name, Role, Value' +[mechanism]: https://www.w3.org/TR/WCAG22/#dfn-mechanism 'WCAG Definition of Mechanism' +[sc211]: https://www.w3.org/TR/WCAG22/#keyboard 'Success Criterion 2.1.1 Keyboard' +[sc412]: https://www.w3.org/TR/WCAG22/#name-role-value 'Success Criterion 4.1.2 Name, Role, Value' diff --git a/pages/glossary/marked-as-decorative.md b/pages/glossary/marked-as-decorative.md index 7a328b3195f..ba13b744ee2 100755 --- a/pages/glossary/marked-as-decorative.md +++ b/pages/glossary/marked-as-decorative.md @@ -17,6 +17,6 @@ Elements are marked as decorative as a way to convey the intention of the author Elements can also be ignored by assistive technologies if they are [programmatically hidden][]. This is different from marking the element as decorative and does not convey the same intention. Notably, being [programmatically hidden][] may change as users interact with the page (showing and hiding elements) while being marked as decorative should stay the same through all states of the page. [explicit role]: #explicit-role 'Definition of Explicit Role' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [programmatically hidden]: #programmatically-hidden 'Definition of Programmatically Hidden' -[pure decoration]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG definition of Pure Decoration' +[pure decoration]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure Decoration' diff --git a/pages/glossary/owned-by.md b/pages/glossary/owned-by.md index 8a19bd4e00b..1c4f4844992 100755 --- a/pages/glossary/owned-by.md +++ b/pages/glossary/owned-by.md @@ -11,6 +11,6 @@ An element A is _owned by_ element B if element A is a child of element B in the Being a child in the [accessibility tree][] is different from being a child in the DOM tree. Some DOM nodes have no corresponding node in the [accessibility tree][] (for example, because they are marked with `role="presentation"`). A child in the [accessibility tree][] can thus correspond to a descendant in the DOM tree. Additionally, the use of `aria-owns` attribute can change the tree structure to something which is not a subtree of the DOM tree. -This definition is different from the definition of ["owned element" in WAI-ARIA](https://www.w3.org/TR/wai-aria-1.1/#dfn-owned-element). Because browsers have different accessibility trees, which element owns which other elements can vary between browsers. Until there is a standard accessibility tree, testing with multiple accessibility trees may be necessary. +This definition is different from the definition of ["owned element" in WAI-ARIA](https://www.w3.org/TR/wai-aria-1.2/#dfn-owned-element). Because browsers have different accessibility trees, which element owns which other elements can vary between browsers. Until there is a standard accessibility tree, testing with multiple accessibility trees may be necessary. [accessibility tree]: https://www.w3.org/TR/act-rules-aspects/#input-aspects-accessibility 'Definition of accessibility tree' diff --git a/pages/glossary/perceivable-content.md b/pages/glossary/perceivable-content.md index 59de29ca9ba..200bd5487d7 100755 --- a/pages/glossary/perceivable-content.md +++ b/pages/glossary/perceivable-content.md @@ -23,7 +23,7 @@ This definition assumes that elements with a [semantic role][] of `none` or `pre [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree' [palpable content]: https://html.spec.whatwg.org/multipage/dom.html#palpable-content 'HTML specification of palpable content' -[pure decoration]: https://www.w3.org/TR/WCAG21/#dfn-pure-decoration 'WCAG definition of pure decoration' -[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships 'Success Criterion 1.3.1: Info and Relationship' +[pure decoration]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of pure decoration' +[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships 'Success Criterion 1.3.1: Info and Relationship' [semantic role]: #semantic-role 'Definition of semantic role' [visible]: #visible 'Definition of visible' diff --git a/pages/glossary/programmatically-determined-link-context.md b/pages/glossary/programmatically-determined-link-context.md index b0261b55532..547901014c5 100755 --- a/pages/glossary/programmatically-determined-link-context.md +++ b/pages/glossary/programmatically-determined-link-context.md @@ -16,7 +16,7 @@ The _programmatically determined context_ of a link (or _programmatically determ - being a header cell [assigned][] to the closest [ancestor][] of the link in the [flat tree][] that has a [semantic role][] of `cell` or `gridcell`; or - being referenced by an `aria-describedby` attribute of the link. -This definition is based on (but not equivalent to) the [WCAG definition of programmatically determined link context](https://www.w3.org/TR/WCAG21/#dfn-programmatically-determined-link-context). +This definition is based on (but not equivalent to) the [WCAG definition of programmatically determined link context](https://www.w3.org/TR/WCAG22/#dfn-programmatically-determined-link-context). This definition assumes that the HTML document with the link is a document using HTML according to the specification. diff --git a/pages/glossary/semantic-role.md b/pages/glossary/semantic-role.md index f6ad3124417..ba31c16fb2a 100755 --- a/pages/glossary/semantic-role.md +++ b/pages/glossary/semantic-role.md @@ -25,5 +25,5 @@ This definition can be used in expressions such as "semantic `button`" meaning a [implicit role]: #implicit-role 'Definition of Implicit Role' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [marked as decorative]: #marked-as-decorative 'Definition of Marked as Decorative' -[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.1/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [programmatically hidden]: #programmatically-hidden 'Definition of Programmatically Hidden' diff --git a/pages/glossary/visible.md b/pages/glossary/visible.md index 5a327290008..edddc042df0 100755 --- a/pages/glossary/visible.md +++ b/pages/glossary/visible.md @@ -12,6 +12,6 @@ Content perceivable through sight. Content is considered _visible_ if making it fully transparent would result in a difference in the pixels rendered for any part of the document that is currently within the viewport or can be brought into the viewport via scrolling. -[Content is defined in WCAG](https://www.w3.org/TR/WCAG21/#dfn-content). +[Content is defined in WCAG](https://www.w3.org/TR/WCAG22/#dfn-content). For more details, see [examples of visible](https://act-rules.github.io/pages/examples/visible/). diff --git a/pages/glossary/web-page-html.md b/pages/glossary/web-page-html.md index c7fac42d29d..a2ace9ad303 100755 --- a/pages/glossary/web-page-html.md +++ b/pages/glossary/web-page-html.md @@ -7,10 +7,10 @@ input_aspects: - DOM tree --- -An _HTML [web page](https://www.w3.org/TR/WCAG21/#dfn-web-page-s)_ is the set of all [fully active](https://html.spec.whatwg.org/#fully-active) [documents](https://dom.spec.whatwg.org/#concept-document) which share the same [top-level browsing context](https://html.spec.whatwg.org/#top-level-browsing-context). +An _HTML [web page](https://www.w3.org/TR/WCAG22/#dfn-web-page-s)_ is the set of all [fully active](https://html.spec.whatwg.org/#fully-active) [documents](https://dom.spec.whatwg.org/#concept-document) which share the same [top-level browsing context](https://html.spec.whatwg.org/#top-level-browsing-context). **Note:** Nesting of browsing context mostly happens with `iframe` and `object`. Thus a web page will most of the time be a "top-level" document and all its `iframe` and `object` (recursively). -**Note:** [Web pages](https://www.w3.org/TR/WCAG21/#dfn-web-page-s) as defined by WCAG are not restricted to the HTML technology but can also include, _e.g._, PDF or DOCX documents. +**Note:** [Web pages](https://www.w3.org/TR/WCAG22/#dfn-web-page-s) as defined by WCAG are not restricted to the HTML technology but can also include, _e.g._, PDF or DOCX documents. **Note:** Although web pages as defined here are sets of [documents](https://dom.spec.whatwg.org/#concept-document) (and do not contain other kind of nodes), one can abusively write that any node is "in a web page" if it is a [shadow-including descendant](https://dom.spec.whatwg.org/#concept-shadow-including-descendant) of a [document](https://dom.spec.whatwg.org/#concept-document) that is part of that web page. diff --git a/pages/implementations/earl-reports.md b/pages/implementations/earl-reports.md index e4168393bc1..6efe8cd1dbe 100644 --- a/pages/implementations/earl-reports.md +++ b/pages/implementations/earl-reports.md @@ -137,6 +137,6 @@ Alternatively, it is possible to specify WCAG 2 success criteria by number inste } ``` -The format of the `title` property in the `isPartOf` array is fairly permissive. To be recognized as a success criterion, the string `WCAG 2` or `WCAG2`, and the success criterion number (separated with dots) must be included. For example `WCAG 2.1 criterion 1.1.1 Non-text content` would be recognized. To explicitly add the success criterion ID the `@id` property can be used. +The format of the `title` property in the `isPartOf` array is fairly permissive. To be recognized as a success criterion, the string `WCAG 2` or `WCAG2`, and the success criterion number (separated with dots) must be included. For example `WCAG 2.2 criterion 1.1.1 Non-text content` would be recognized. To explicitly add the success criterion ID the `@id` property can be used. **Advanced**: All required properties map to [EARL](http://www.w3.org/ns/earl#), except for `isPartOf`, `title`, and `source` which are properties of [Dublin Core](http://purl.org/dc/terms/). Property names can be anything, as long as they can be expanded to the correct URL.