diff --git a/_rules/aria-attr-defined-5f99a7.md b/_rules/aria-attr-defined-5f99a7.md index 5c3aea66dee..6f51d24fe7c 100755 --- a/_rules/aria-attr-defined-5f99a7.md +++ b/_rules/aria-attr-defined-5f99a7.md @@ -39,7 +39,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/aria-hidden-no-focusable-content-6cfa84.md b/_rules/aria-hidden-no-focusable-content-6cfa84.md index 5fc72986855..06853779160 100755 --- a/_rules/aria-hidden-no-focusable-content-6cfa84.md +++ b/_rules/aria-hidden-no-focusable-content-6cfa84.md @@ -57,7 +57,7 @@ Some user agents treat the value of `aria-hidden` attribute as case-sensitive. - [Element with presentational children has no focusable content](https://www.w3.org/WAI/standards-guidelines/act/rules/307n5z/) -### Bibliography +### Other Resources - [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/WCAG22/Understanding/info-and-relationships) diff --git a/_rules/aria-required-context-role-ff89c9.md b/_rules/aria-required-context-role-ff89c9.md index de507f85413..479de5f25d0 100755 --- a/_rules/aria-required-context-role-ff89c9.md +++ b/_rules/aria-required-context-role-ff89c9.md @@ -58,7 +58,7 @@ The rule assumes that the [explicit role][] of the applicable elements is approp - `aria-owns` has limited support in some user agents. - There exist some combination of popular browsers and assistive technologies who do not announce correctly relationships based on a mix of [implicit][implicit role] and [explicit][explicit role] roles. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) - [Required Context Role][] diff --git a/_rules/aria-required-id-references-in6db8.md b/_rules/aria-required-id-references-in6db8.md index 29bfe68372e..4ba010633b4 100644 --- a/_rules/aria-required-id-references-in6db8.md +++ b/_rules/aria-required-id-references-in6db8.md @@ -47,7 +47,7 @@ There are no assumptions. Some user agents treat the value of `aria-*` attribute as case-sensitive (even when these are not IDs) while some treat them as case-insensitive. -### Bibliography +### Other Resources - [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) diff --git a/_rules/aria-required-owned-element-bc4a75.md b/_rules/aria-required-owned-element-bc4a75.md index 5f36b4de5b9..6d54cbe3223 100755 --- a/_rules/aria-required-owned-element-bc4a75.md +++ b/_rules/aria-required-owned-element-bc4a75.md @@ -54,7 +54,7 @@ If the [semantic role][] on the target element is incorrectly used, and any rela - Assistive technologies are not consistent in how they handle situations where a [required owned element][] has a missing or incorrect role. This can lead to situations where inaccurate owned elements behave as expected in one assistive technology, but not in another. - Some user agents treat the value of `aria-busy` as case-sensitive. -### Bibliography +### Other Resources - [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) diff --git a/_rules/aria-state-or-property-permitted-5c01ea.md b/_rules/aria-state-or-property-permitted-5c01ea.md index 4713f583f7d..156993b0501 100755 --- a/_rules/aria-state-or-property-permitted-5c01ea.md +++ b/_rules/aria-state-or-property-permitted-5c01ea.md @@ -73,7 +73,7 @@ Implementation of [Presentational Roles Conflict Resolution][] varies from one b - [ARIA state or property has valid value](https://www.w3.org/WAI/standards-guidelines/act/rules/6a7281/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/aria-state-or-property-valid-value-6a7281.md b/_rules/aria-state-or-property-valid-value-6a7281.md index 53fd6a787c6..b6fdfff06a7 100755 --- a/_rules/aria-state-or-property-valid-value-6a7281.md +++ b/_rules/aria-state-or-property-valid-value-6a7281.md @@ -56,7 +56,7 @@ Some user agents treat the value of `aria-*` attribute as case-sensitive (even w - [ARIA state or property is permitted](https://www.w3.org/WAI/standards-guidelines/act/rules/5c01ea/) - [ARIA required ID references exist](https://www.w3.org/WAI/standards-guidelines/act/rules/in6db8/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/attr-not-duplicated-e6952f.md b/_rules/attr-not-duplicated-e6952f.md index cd79fa268f0..64ccb33b714 100755 --- a/_rules/attr-not-duplicated-e6952f.md +++ b/_rules/attr-not-duplicated-e6952f.md @@ -54,7 +54,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [H94: Ensuring that elements do not contain duplicate attributes](https://www.w3.org/WAI/WCAG22/Techniques/html/H94) diff --git a/_rules/audio-as-media-alternative-afb423.md b/_rules/audio-as-media-alternative-afb423.md index 9c6e527c125..d71e1ebe1b3 100755 --- a/_rules/audio-as-media-alternative-afb423.md +++ b/_rules/audio-as-media-alternative-afb423.md @@ -46,7 +46,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding SC 1.2.1: Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) 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 50338f8b821..e83f42c6f64 100755 --- a/_rules/audio-or-video-avoids-automatically-playing-audio-80f0bf.md +++ b/_rules/audio-or-video-avoids-automatically-playing-audio-80f0bf.md @@ -82,7 +82,7 @@ The native `video` and `audio` controls in several browser and assistive technol User agents do not always automatically play media, even when an `autoplay` attribute is present. This is done to avoid autoplaying media interrupting the user when they do not want to, especially when the media is likely to contain sound. The decision to respect the `autoplay` attribute or not depends on user settings and previous behavior (interaction with the site). Therefore, some media files may fail this rule but satisfy [Success Criterion 1.4.2 Audio Control][sc142] on some combination of User Agent and user settings. The rule considers that the presence of the `autoplay` attribute is an indication of the author intention to have automatically playing media, and therefore requires the author to provide a mechanism to control the sound. -### Bibliography +### Other Resources - [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) diff --git a/_rules/audio-text-alternative-e7aa44.md b/_rules/audio-text-alternative-e7aa44.md index eda9c88f450..62de9823179 100755 --- a/_rules/audio-text-alternative-e7aa44.md +++ b/_rules/audio-text-alternative-e7aa44.md @@ -55,7 +55,7 @@ This rule assumes that the language of each test target can be correctly determi There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/audio-transcript-2eb176.md b/_rules/audio-transcript-2eb176.md index 5c9d87f52f7..43a04e15f70 100755 --- a/_rules/audio-transcript-2eb176.md +++ b/_rules/audio-transcript-2eb176.md @@ -44,7 +44,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) 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 a13b8528554..c526a9f45c5 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 @@ -52,7 +52,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/auto-play-audio-has-control-mechanism-4c31df.md b/_rules/auto-play-audio-has-control-mechanism-4c31df.md index 7e3648fe84f..0cd1627a10a 100755 --- a/_rules/auto-play-audio-has-control-mechanism-4c31df.md +++ b/_rules/auto-play-audio-has-control-mechanism-4c31df.md @@ -58,7 +58,7 @@ There are no assumptions. The native `video` and `audio` controls in several browser and assistive technology combinations are not keyboard accessible and the `video` or `audio` element itself may not be announced. Authors are recommended to use custom controls for keyboard navigation and cross browser accessibility support in general. -### Bibliography +### Other Resources - [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) diff --git a/_rules/auto-update-text-efbfc7.md b/_rules/auto-update-text-efbfc7.md index 26319d588b3..8bf9dfee3c4 100755 --- a/_rules/auto-update-text-efbfc7.md +++ b/_rules/auto-update-text-efbfc7.md @@ -66,7 +66,7 @@ The [instruments][instrument] used to pass this rule (if any), must meet all lev There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding Success Criterion 2.2.2: Pause, Stop, Hide][sc 2.2.2] - [G186: Using a control in the Web page that stops moving, blinking, or auto-updating content][g186] diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index d744e7b60ca..68c72e99136 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -71,7 +71,7 @@ The purpose of a control is programmatically identifiable even when its `autocom - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have a [semantic role][] of `none` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. - Authors may assign inappropriate `autocomplete` attribute values. Moreover, HTML specifications restrict certain `autocomplete` attribute values to specific form controls. Mismatches between `autocomplete` attribute values and form control types may or may not lead to a failure of [success criterion 1.3.5 Identify Input Purpose](https://www.w3.org/TR/WCAG22/#identify-input-purpose). However, this rule focuses exclusively on validating valid `autocomplete` attribute values, disregarding their contextual appropriateness. -### Bibliography +### Other Resources - [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) diff --git a/_rules/block-collapsible-3e12e1.md b/_rules/block-collapsible-3e12e1.md index c726743fb63..9233760ac55 100755 --- a/_rules/block-collapsible-3e12e1.md +++ b/_rules/block-collapsible-3e12e1.md @@ -47,7 +47,7 @@ Usually the same [instrument][] removes both [visibility][visible] and [inclusio There are no accessibility support issues known. -### Bibliography +### Other Resources - [Technique SCR28: Using an expandable and collapsible menu to bypass block of content][tech scr28] diff --git a/_rules/button-non-empty-accessible-name-97a4e1.md b/_rules/button-non-empty-accessible-name-97a4e1.md index ba2e8077c08..e2319dcc5ea 100755 --- a/_rules/button-non-empty-accessible-name-97a4e1.md +++ b/_rules/button-non-empty-accessible-name-97a4e1.md @@ -49,7 +49,7 @@ This rule considers an exception for "image buttons" (i.e., `input` elements wit - [Image button has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/59796f/) -### Bibliography +### Other Resources - [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/WCAG22/Understanding/name-role-value) diff --git a/_rules/bypass-blocks-cf77f2.md b/_rules/bypass-blocks-cf77f2.md index 7be99e26bd7..e63df918530 100755 --- a/_rules/bypass-blocks-cf77f2.md +++ b/_rules/bypass-blocks-cf77f2.md @@ -85,7 +85,7 @@ If the [instruments][instrument] used to pass some of the atomic rules are not k 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. -### Bibliography +### Other Resources - [Understanding Success Criterion 2.4.1: Bypass Blocks][usc241] - Creating links to skip blocks of content: diff --git a/_rules/css-restrict-orientation-b33eff.md b/_rules/css-restrict-orientation-b33eff.md index 7c4239caa52..85d6e1e5bb2 100755 --- a/_rules/css-restrict-orientation-b33eff.md +++ b/_rules/css-restrict-orientation-b33eff.md @@ -60,7 +60,7 @@ This rule does not consider and may produce incorrect results for: There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/device-motion-disabled-c249d5.md b/_rules/device-motion-disabled-c249d5.md index 6b93b979638..84c1c4a3977 100755 --- a/_rules/device-motion-disabled-c249d5.md +++ b/_rules/device-motion-disabled-c249d5.md @@ -56,7 +56,7 @@ The [instruments][instrument] used to pass this rule (if any), must meet all lev There are no accessibility support issues known. -### Bibliography +### Other Resources - [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/WCAG22/Techniques/general/G213.html) diff --git a/_rules/device-motion-user-interface-7677a9.md b/_rules/device-motion-user-interface-7677a9.md index e0150076389..5f036be6753 100755 --- a/_rules/device-motion-user-interface-7677a9.md +++ b/_rules/device-motion-user-interface-7677a9.md @@ -53,7 +53,7 @@ The [instruments][instrument] used to pass this rule (if any), must meet all lev There are no accessibility support issues known. -### Bibliography +### Other Resources - [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/WCAG22/Techniques/general/G213.html) 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 ba8679c0f06..7c13a4dcaa9 100755 --- a/_rules/document-has-headings-for-non-repeated-content-047fe0.md +++ b/_rules/document-has-headings-for-non-repeated-content-047fe0.md @@ -54,7 +54,7 @@ Neither this rule, nor technique [H69: Providing heading elements at the beginni - 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][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]. -### Bibliography +### Other Resources - [Understanding Success Criterion 2.4.1: Bypass Blocks][usc241] - [H69: Providing heading elements at the beginning of each section of content][h69] 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 54b449d7669..ed176bacabc 100755 --- a/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md +++ b/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md @@ -57,7 +57,7 @@ This rule assumes that there is at least one [block of repeated content][] befor There are no accessibility support issues known. -### Bibliography +### Other Resources - [Technique G1: Adding a link at the top of each page that goes directly to the main content area][tech g1] - [Technique G123: Adding a link at the beginning of a block of repeated content to go to the end of the block][tech g123] 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 058a77e8fbe..fe97ad1e492 100755 --- a/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md +++ b/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md @@ -47,7 +47,7 @@ Most of the time, this rule passes by enclosing the primary content of the page Marking content with landmarks is sufficient to pass [Success Criterion 2.4.1 Bypass blocks][sc241]. However, this will only benefit users who can actually navigate using landmark roles (such a functionality is usually provided by assistive technologies, but could also be provided by browsers or browsers plugins). Users without any possibility for landmarks 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. -### Bibliography +### Other Resources - [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) diff --git a/_rules/element-lang-matches-default-language-off6ek.md b/_rules/element-lang-matches-default-language-off6ek.md index ecaa5226686..bb6f033f299 100644 --- a/_rules/element-lang-matches-default-language-off6ek.md +++ b/_rules/element-lang-matches-default-language-off6ek.md @@ -65,7 +65,7 @@ There are no accessibility support issues known. - [_Element with `lang` Attribute Has Valid Language Tag_](https://www.w3.org/WAI/standards-guidelines/act/rules/de46e4/) -### Bibliography +### Other Resources - [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/WCAG22/Techniques/html/H58) diff --git a/_rules/element-lang-valid-de46e4.md b/_rules/element-lang-valid-de46e4.md index 4d02b8a261e..8ab2249ddf9 100755 --- a/_rules/element-lang-valid-de46e4.md +++ b/_rules/element-lang-valid-de46e4.md @@ -56,7 +56,7 @@ For each test target, the `lang` [attribute value][] has a [known primary langua There are differences in how assistive technologies handle unknown and invalid language tags. Some will default to the language of the page, whereas others will default to the closest ancestor with a valid lang attribute. -### Bibliography +### Other Resources - [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/WCAG22/Techniques/html/H58) 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 122ece8958a..b5b3bf671c2 100755 --- a/_rules/explicit-SVG-image-non-empty-accessible-name-7d6734.md +++ b/_rules/explicit-SVG-image-non-empty-accessible-name-7d6734.md @@ -45,7 +45,7 @@ Browser and assistive technology support for SVG `` and `<desc>` elements Until browser support for the [SVG Accessibility API Mappings][] is more consistent it is recommended to explicitly remove decorative `<svg>` elements from the accessibility tree. -### Bibliography +### Other Resources - [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] diff --git a/_rules/focusable-no-keyboard-trap-80af7b.md b/_rules/focusable-no-keyboard-trap-80af7b.md index f7064aed87f..67fd165a68f 100755 --- a/_rules/focusable-no-keyboard-trap-80af7b.md +++ b/_rules/focusable-no-keyboard-trap-80af7b.md @@ -57,7 +57,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) 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 c4709b57ea7..697ca913775 100755 --- a/_rules/focusable-no-keyboard-trap-non-standard-nav-ebe86a.md +++ b/_rules/focusable-no-keyboard-trap-non-standard-nav-ebe86a.md @@ -53,7 +53,7 @@ For each target element focus can cycle to the browser UI by using the method ad Some browsers have settings that will immediately cycle focus back to the web document. This fulfills the expectation because focus can cycle to the browser UI and the browser UI cycles focus back to the web document. -### Bibliography +### Other Resources - [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) diff --git a/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md b/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md index 9fd2efdc157..10a546fcdbc 100755 --- a/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md +++ b/_rules/focusable-no-keyboard-trap-standard-nav-a1b64e.md @@ -46,7 +46,7 @@ This rule only requires navigation in one direction (either forward or backward) Some browsers have settings that will immediately cycle focus back to the web document. This fulfills the expectation because focus can cycle to the browser UI and the browser UI cycles focus back to the web document. -### Bibliography +### Other Resources - [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) @@ -88,43 +88,43 @@ use [standard keyboard navigation](#standard-keyboard-navigation) using the Esca ```html <div>Main page content with <a href="#">some link</a></div> <div aria-hidden="true"> - <a href="#" id="sentinelBefore" style="position:absolute; top:-999em" - >Upon receiving focus, this focus sentinel should wrap focus to the bottom of the modal</a - > + <a href="#" id="sentinelBefore" style="position:absolute; top:-999em" + >Upon receiving focus, this focus sentinel should wrap focus to the bottom of the modal</a + > </div> <div - id="sampleModal" - role="dialog" - aria-label="Sample Modal" - aria-modal="true" - style="border: solid black 1px; padding: 1rem;" + id="sampleModal" + role="dialog" + aria-label="Sample Modal" + aria-modal="true" + style="border: solid black 1px; padding: 1rem;" > - <label>First and last name <input id="dialogFirst"/></label><br /> - <button id="closeButton">Close button</button> + <label>First and last name <input id="dialogFirst"/></label><br /> + <button id="closeButton">Close button</button> </div> <div aria-hidden="true"> - <a href="#" id="sentinelAfter" style="position:absolute; top:-999em" - >Upon receiving focus, this focus sentinel should wrap focus to the top of the modal</a - > + <a href="#" id="sentinelAfter" style="position:absolute; top:-999em" + >Upon receiving focus, this focus sentinel should wrap focus to the top of the modal</a + > </div> <script> - window.addEventListener('load', () => { - document.getElementById('dialogFirst').focus(); - }) - document.getElementById('sentinelBefore').addEventListener('focus', () => { - document.getElementById('closeButton').focus() - }) - document.getElementById('sentinelAfter').addEventListener('focus', () => { - document.getElementById('dialogFirst').focus() - }) - document.getElementById('closeButton').addEventListener('click', () => { - document.getElementById('sampleModal').style.display = 'none' - }) - document.getElementById('sampleModal').addEventListener('keydown', (evt) => { - if (evt.key === "Escape") { - document.getElementById('sampleModal').style.display = 'none'; - } - }) + window.addEventListener('load', () => { + document.getElementById('dialogFirst').focus() + }) + document.getElementById('sentinelBefore').addEventListener('focus', () => { + document.getElementById('closeButton').focus() + }) + document.getElementById('sentinelAfter').addEventListener('focus', () => { + document.getElementById('dialogFirst').focus() + }) + document.getElementById('closeButton').addEventListener('click', () => { + document.getElementById('sampleModal').style.display = 'none' + }) + document.getElementById('sampleModal').addEventListener('keydown', evt => { + if (evt.key === 'Escape') { + document.getElementById('sampleModal').style.display = 'none' + } + }) </script> ``` diff --git a/_rules/form-field-label-descriptive-cc0f0a.md b/_rules/form-field-label-descriptive-cc0f0a.md index a2262cfce73..68f21afe75f 100755 --- a/_rules/form-field-label-descriptive-cc0f0a.md +++ b/_rules/form-field-label-descriptive-cc0f0a.md @@ -76,7 +76,7 @@ Having a [label][] which is not included in the [accessible name][] is a violati - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have one of the applicable [semantic roles][semantic role] and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [Accessible Rich Internet Applications (WAI-ARIA) 1.2][aria12] - [Understanding Success Criterion 2.4.6: Headings and Labels][usc246] diff --git a/_rules/form-field-non-empty-accessible-name-e086e5.md b/_rules/form-field-non-empty-accessible-name-e086e5.md index 62f2a04264f..ed79f5ce6ca 100755 --- a/_rules/form-field-non-empty-accessible-name-e086e5.md +++ b/_rules/form-field-non-empty-accessible-name-e086e5.md @@ -55,7 +55,7 @@ There are no assumptions. - Several assistive technologies have a functionality to list all form fields on a page, including the `disabled` ones. Therefore this rule is still applicable to `disabled` form fields. If an assistive technology consistently ignores `disabled` form fields in all its interactions, then it is possible to have a `disabled` form field with no accessible name without creating accessibility issues for the user. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have one of the applicable [semantic roles][] and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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) diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md index f8a6309a891..eaf960b2233 100755 --- a/_rules/heading-descriptive-b49b2e.md +++ b/_rules/heading-descriptive-b49b2e.md @@ -50,7 +50,7 @@ This rule also assumes that the content the heading is intended to describe is [ Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `heading` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) - [Understanding Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html) diff --git a/_rules/heading-non-empty-accessible-name-ffd0e9.md b/_rules/heading-non-empty-accessible-name-ffd0e9.md index c2168460c13..98ce1dc668d 100755 --- a/_rules/heading-non-empty-accessible-name-ffd0e9.md +++ b/_rules/heading-non-empty-accessible-name-ffd0e9.md @@ -48,7 +48,7 @@ There are no assumptions. - The [accessible name and description computation][] suggests that if an `aria-labelledby` attribute refers to an existing but empty element, the computation should stop and return an empty name without defaulting to the next steps. Several user agents and assistive technologies chose to use the next step in the computation in this case (ultimately defaulting to the content). -### Bibliography +### Other Resources - [Understanding Success Criterion 1.3.1: Info and Relationships][usc131] - [Technique H42: Using h1-h6 to identify headings][tech h42] diff --git a/_rules/html-page-lang-b5c3f8.md b/_rules/html-page-lang-b5c3f8.md index 548c8fa6647..9c841774a0c 100755 --- a/_rules/html-page-lang-b5c3f8.md +++ b/_rules/html-page-lang-b5c3f8.md @@ -55,7 +55,7 @@ There are no accessibility support issues known. - [HTML page `lang` attribute has valid language tag](https://www.w3.org/WAI/standards-guidelines/act/rules/bf051a/) - [HTML page language subtag matches default language](https://www.w3.org/WAI/standards-guidelines/act/rules/ucwvc8/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/html-page-lang-matches-default-ucwvc8.md b/_rules/html-page-lang-matches-default-ucwvc8.md index 62ebdc26ecc..9ef0a024091 100755 --- a/_rules/html-page-lang-matches-default-ucwvc8.md +++ b/_rules/html-page-lang-matches-default-ucwvc8.md @@ -68,7 +68,7 @@ There are no accessibility support issues known. - [HTML page has `lang` attribute](https://www.w3.org/WAI/standards-guidelines/act/rules/b5c3f8/) - [HTML page `lang` attribute has valid language tag](https://www.w3.org/WAI/standards-guidelines/act/rules/bf051a/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/html-page-lang-valid-bf051a.md b/_rules/html-page-lang-valid-bf051a.md index 9fbe23637ce..9d29d4aad50 100755 --- a/_rules/html-page-lang-valid-bf051a.md +++ b/_rules/html-page-lang-valid-bf051a.md @@ -60,7 +60,7 @@ This rule is only applicable to non-embedded HTML pages. HTML pages embedded int - [HTML page has `lang` attribute](https://www.w3.org/WAI/standards-guidelines/act/rules/b5c3f8/) - [HTML page language subtag matches default language](https://www.w3.org/WAI/standards-guidelines/act/rules/ucwvc8/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/html-page-lang-xml-lang-match-5b7ae0.md b/_rules/html-page-lang-xml-lang-match-5b7ae0.md index 2a4940fc8f7..995079fb377 100755 --- a/_rules/html-page-lang-xml-lang-match-5b7ae0.md +++ b/_rules/html-page-lang-xml-lang-match-5b7ae0.md @@ -55,7 +55,7 @@ This rule is only applicable to non-embedded HTML pages. HTML pages embedded int Since most assistive technologies will consistently use `lang` over `xml:lang` when both are used, violation of this rule may not necessarily be a violation of WCAG 2. Only when there are inconsistencies between assistive technologies as to which attribute is used to determine the language does this lead to a violation of SC 3.1.1. -### Bibliography +### Other Resources - [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) diff --git a/_rules/html-page-non-empty-title-2779a5.md b/_rules/html-page-non-empty-title-2779a5.md index 0e62b601972..ce0df56c3ac 100755 --- a/_rules/html-page-non-empty-title-2779a5.md +++ b/_rules/html-page-non-empty-title-2779a5.md @@ -68,7 +68,7 @@ There are no accessibility support issues known. - [HTML page title is descriptive](https://www.w3.org/WAI/standards-guidelines/act/rules/c4a8a4/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/html-page-title-descriptive-c4a8a4.md b/_rules/html-page-title-descriptive-c4a8a4.md index 62f45617df4..2763d6fe29a 100755 --- a/_rules/html-page-title-descriptive-c4a8a4.md +++ b/_rules/html-page-title-descriptive-c4a8a4.md @@ -65,7 +65,7 @@ There are currently no assumptions. - [HTML page has non-empty title](https://www.w3.org/WAI/standards-guidelines/act/rules/2779a5/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/id-value-unique-3ea0c8.md b/_rules/id-value-unique-3ea0c8.md index 2f084ff6652..39fd1b3d8ea 100755 --- a/_rules/id-value-unique-3ea0c8.md +++ b/_rules/id-value-unique-3ea0c8.md @@ -54,7 +54,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md b/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md index c1c481d68c0..3572542fc8a 100755 --- a/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md +++ b/_rules/iframe-identical-name-equivalent-purpose-4b1c6c.md @@ -48,7 +48,7 @@ This rule assumes that, within the context of the test subject, the description This rule assumes that assistive technologies are exposing all `iframe` elements on the page in the same way no matter which [document tree](https://dom.spec.whatwg.org/#document-trees) they are in. If an assistive technology requires the user to "enter" an `iframe` or a [shadow tree][] before exposing its content (notably nested `iframe`), then it is possible for two `iframe` to have identical name but embed different resources without failing [Success Criterion 4.1.2: Name, Role, Value][sc412] (if said `iframe` are in separate [documents][document] or [shadow trees][shadow tree]) -### Bibliography +### Other Resources - [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/WCAG22/Techniques/html/H64) diff --git a/_rules/iframe-non-empty-accessible-name-cae760.md b/_rules/iframe-non-empty-accessible-name-cae760.md index 7cb2d8673e0..419f611af93 100755 --- a/_rules/iframe-non-empty-accessible-name-cae760.md +++ b/_rules/iframe-non-empty-accessible-name-cae760.md @@ -52,7 +52,7 @@ If an `iframe` is not perceived by the user as a single control, it does not qua - Some browsers instantly redirect focus from `iframe` elements to the first focusable element inside that iframe. This redirect makes it appear as though the `iframe` never receives focus. This occurs even if the `iframe` has a non-negative `tabindex` [attribute value][]. - Not all browsers redirect focus on `iframe` elements. This ensures that the contents of `iframe` elements can be scrolled and accessed by using the keyboard. This must not be circumvented by using a negative tabindex, as this will make the `iframe` completely inaccessible for keyboard navigation. -### Bibliography +### Other Resources - [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) 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 a7aba70ff3b..0bd260da84d 100644 --- a/_rules/iframe-with-interactive-content-in-tab-order-akn7bn.md +++ b/_rules/iframe-with-interactive-content-in-tab-order-akn7bn.md @@ -59,7 +59,7 @@ This rule assumes that interactive content inside `iframe` elements is used to p There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/image-accessible-name-descriptive-qt1vmo.md b/_rules/image-accessible-name-descriptive-qt1vmo.md index c0be12afbb5..b677f2f10b0 100755 --- a/_rules/image-accessible-name-descriptive-qt1vmo.md +++ b/_rules/image-accessible-name-descriptive-qt1vmo.md @@ -63,7 +63,7 @@ There are no assumptions. Some popular browser / screen reader combinations do not pronounce the accessible names of `svg` elements. This can be resolved by adding an [explicit semantic role][] of `img` to the `svg` element. -### Bibliography +### Other Resources - [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) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 1561bc5e4df..e0ae3f3170d 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -65,7 +65,7 @@ The [input type="image" Accessible Name Computation algorithm](https://www.w3.or - [Button has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/97a4e1/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/image-filename-as-accessible-name-9eb3f6.md b/_rules/image-filename-as-accessible-name-9eb3f6.md index e5ce2987db7..db4698a2f5e 100755 --- a/_rules/image-filename-as-accessible-name-9eb3f6.md +++ b/_rules/image-filename-as-accessible-name-9eb3f6.md @@ -69,7 +69,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/image-no-text-0va7u6.md b/_rules/image-no-text-0va7u6.md index c45938d06e6..5f8ad5e278d 100644 --- a/_rules/image-no-text-0va7u6.md +++ b/_rules/image-no-text-0va7u6.md @@ -57,7 +57,7 @@ This rule is designed specifically for [SC 1.4.5 Images of Text][sc1.4.5]. There There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.4.5: Images of Text][sc1.4.5] - [Understanding Success Criterion 1.4.9: Images of Text (No Exception)][sc1.4.9] diff --git a/_rules/image-non-empty-accessible-name-23a2a8.md b/_rules/image-non-empty-accessible-name-23a2a8.md index 6365dce684a..a508172806d 100755 --- a/_rules/image-non-empty-accessible-name-23a2a8.md +++ b/_rules/image-non-empty-accessible-name-23a2a8.md @@ -59,7 +59,7 @@ There are no assumptions. - Images can have their role set to `presentation` through an empty `alt` attribute. [Presentational Roles Conflict Resolution][] does not specify what to do if such an image is [focusable][] (it only specifies what to do in case of explicit `role="none"` or `role="presentation"`). Some browsers expose these images and some don't. Thus, this rule may fail for technologies that expose these without creating an accessibility issue for users of other technologies. - `svg` elements have an [implicit role][] of `graphics-document` in [svg-aam](https://www.w3.org/TR/svg-aam-1.0/#details-id-66). There are popular browsers that do not follow [svg-aam](https://www.w3.org/TR/svg-aam-1.0/#details-id-66) and instead expose SVG elements with a different [semantic role][], such as `image`, `generic` or `SvgRoot`. -### Bibliography +### Other Resources - [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) 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 3d2a8ad4cf1..0582fd2e36d 100755 --- a/_rules/image-not-in-acc-tree-is-decorative-e88epe.md +++ b/_rules/image-not-in-acc-tree-is-decorative-e88epe.md @@ -66,7 +66,7 @@ According to the [WAI-ARIA Graphics Module](https://www.w3.org/TR/graphics-aria- However, browser implementations vary. Some browsers expose `<svg>` elements without accessible names as images without alternative text. To address this, in the passed and inapplicable examples where the `<svg>` element is intended to be purely decorative, the `role="none"` attribute has been added. -### Bibliography +### Other Resources - [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) diff --git a/_rules/important-letter-spacing-wide-enough-24afc2.md b/_rules/important-letter-spacing-wide-enough-24afc2.md index 900a0d7fc95..fccbd79d8c4 100755 --- a/_rules/important-letter-spacing-wide-enough-24afc2.md +++ b/_rules/important-letter-spacing-wide-enough-24afc2.md @@ -56,7 +56,7 @@ CSS specifications define each declaration as being either [important][] (if it While some assistive technologies are able to set [user origin][] or [user agent origin][] styles, others, such as browser extensions, are only able to set styles with the [author origin][]. Such assistive technologies cannot create styles "winning" the [cascade sort][] over a `style` attribute with an [important][] declaration. -### Bibliography +### Other Resources - [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) diff --git a/_rules/important-line-height-wide-enough-78fd32.md b/_rules/important-line-height-wide-enough-78fd32.md index 9d0d59bd71e..7ec5465c905 100755 --- a/_rules/important-line-height-wide-enough-78fd32.md +++ b/_rules/important-line-height-wide-enough-78fd32.md @@ -56,7 +56,7 @@ This rule evaluates the [used][] value of the `line-height` property instead of While some assistive technologies are able to set [user origin][] or [user agent origin][] styles, others, such as browser extensions, are only able to set styles with the [author origin][]. Such assistive technologies cannot create styles "winning" the [cascade sort][] over a `style` attribute with an [important][] declaration. -### Bibliography +### Other Resources - [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) diff --git a/_rules/important-word-spacing-wide-enough-9e45ec.md b/_rules/important-word-spacing-wide-enough-9e45ec.md index 50c9fbe3f25..c7b489da616 100755 --- a/_rules/important-word-spacing-wide-enough-9e45ec.md +++ b/_rules/important-word-spacing-wide-enough-9e45ec.md @@ -56,7 +56,7 @@ CSS specifications define each declaration as being either [important][] (if it While some assistive technologies are able to set [user origin][] or [user agent origin][] styles, others, such as browser extensions, are only able to set styles with the [author origin][]. Such assistive technologies cannot create styles "winning" the [cascade sort][] over a `style` attribute with an [important][] declaration. -### Bibliography +### Other Resources - [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) diff --git a/_rules/invalid-form-field-value-36b590.md b/_rules/invalid-form-field-value-36b590.md index 9e47362566a..4bdf1ad7804 100644 --- a/_rules/invalid-form-field-value-36b590.md +++ b/_rules/invalid-form-field-value-36b590.md @@ -83,7 +83,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/link-alone-descriptive-aizyf1.md b/_rules/link-alone-descriptive-aizyf1.md index 3ff86cde400..9a881a2e9dc 100755 --- a/_rules/link-alone-descriptive-aizyf1.md +++ b/_rules/link-alone-descriptive-aizyf1.md @@ -49,7 +49,7 @@ Each test target has an [accessible name][] which describes its purpose. - [Link has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/c487ae/) -### Bibliography +### Other Resources - [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/WCAG22/Techniques/general/G91) diff --git a/_rules/link-in-context-descriptive-5effbb.md b/_rules/link-in-context-descriptive-5effbb.md index 94ddc76ed4a..9d8b41336db 100755 --- a/_rules/link-in-context-descriptive-5effbb.md +++ b/_rules/link-in-context-descriptive-5effbb.md @@ -55,7 +55,7 @@ The [accessible name][] of each target element together with its [programmatical - [Link has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/c487ae/) - [Link is descriptive](https://www.w3.org/WAI/standards-guidelines/act/rules/aizyf1/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/link-non-empty-accessible-name-c487ae.md b/_rules/link-non-empty-accessible-name-c487ae.md index e4a2daa3212..3e34393876a 100755 --- a/_rules/link-non-empty-accessible-name-c487ae.md +++ b/_rules/link-non-empty-accessible-name-c487ae.md @@ -70,7 +70,7 @@ The rule assumes that all links are [user interface components](https://www.w3.o - [Link in context is descriptive](https://www.w3.org/WAI/standards-guidelines/act/rules/5effbb/) -### Bibliography +### Other Resources - [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) diff --git a/_rules/links-identical-name-equivalent-purpose-b20e66.md b/_rules/links-identical-name-equivalent-purpose-b20e66.md index 9a00a48dd31..45224db96df 100755 --- a/_rules/links-identical-name-equivalent-purpose-b20e66.md +++ b/_rules/links-identical-name-equivalent-purpose-b20e66.md @@ -58,7 +58,7 @@ When followed, the links in each set of target elements resolve to the [same res - This rule assumes that assistive technologies are exposing all links on the page in the same way no matter which [document tree](https://dom.spec.whatwg.org/#document-trees) they are in. If an assistive technology requires the user to "enter" an `iframe` or a [shadow tree][] before exposing its links, then it is possible for two links to have identical name but resolve to different resources without failing [Success Criterion 2.4.9 Link Purpose (Link Only)][sc249] (if said links are in separate [documents][document] or [shadow trees][shadow tree]). - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [inheriting semantic][] `link` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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/WCAG22/Understanding/link-purpose-link-only.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 7c1ee735f9a..17e9a5e2fb2 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 @@ -72,7 +72,7 @@ Pages with links that are not [ambiguous to users in general][], but are ambiguo There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/menuitem-non-empty-name-m6b1q3.md b/_rules/menuitem-non-empty-name-m6b1q3.md index 8de8c6b96b8..cfd3b66f414 100755 --- a/_rules/menuitem-non-empty-name-m6b1q3.md +++ b/_rules/menuitem-non-empty-name-m6b1q3.md @@ -42,7 +42,7 @@ This rule assumes that all menuitems are [user interface components as defined b Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `menuitem` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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) diff --git a/_rules/meta-refresh-no-delay-bc659a.md b/_rules/meta-refresh-no-delay-bc659a.md index 74244afef4d..624bad32e2a 100755 --- a/_rules/meta-refresh-no-delay-bc659a.md +++ b/_rules/meta-refresh-no-delay-bc659a.md @@ -68,7 +68,7 @@ Because a refresh with a timing of 0 is a redirect, it is exempt from this rule. Not all major web browsers parse the value of the `content` attribute in the same way. Some major browsers, when they are unable to parse the value, default to a 0 seconds delay, whereas others will not redirect at all. This can cause some pages to be inapplicable for this rule, while still having a redirect in a minority of web browsers. -### Bibliography +### Other Resources - [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) diff --git a/_rules/meta-refresh-no-delay-no-exception-bisz58.md b/_rules/meta-refresh-no-delay-no-exception-bisz58.md index b140c3d10a3..37711d50e5c 100755 --- a/_rules/meta-refresh-no-delay-no-exception-bisz58.md +++ b/_rules/meta-refresh-no-delay-no-exception-bisz58.md @@ -68,7 +68,7 @@ Because a refresh with a timing of 0 is effectively a redirect, it is exempt fro Not all major web browsers parse the value of the `content` attribute in the same way. Some major browsers, when they are unable to parse the value, default to a 0 seconds delay, whereas others will not redirect at all. This can cause some pages to be inapplicable for this rule, while still having a redirect in a minority of web browsers. -### Bibliography +### Other Resources - [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) diff --git a/_rules/meta-viewport-b4f0c3.md b/_rules/meta-viewport-b4f0c3.md index 8bc2bcf5d3e..aebce45a810 100755 --- a/_rules/meta-viewport-b4f0c3.md +++ b/_rules/meta-viewport-b4f0c3.md @@ -71,7 +71,7 @@ Desktop browsers ignore the viewport `meta` element, and most modern mobile brow The exact way the `content` attribute should be parsed (notably, for error handling) is not fully specified. CSS specification includes a [non-normative parsing algorithm](https://www.w3.org/TR/css-device-adapt-1/#parsing-algorithm). Different user agents may behave differently in some cases. -### Bibliography +### Other Resources - [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) diff --git a/_rules/non-visual-reference-alternative-9bd38c.md b/_rules/non-visual-reference-alternative-9bd38c.md index d4999458f3a..c94f63a0b63 100755 --- a/_rules/non-visual-reference-alternative-9bd38c.md +++ b/_rules/non-visual-reference-alternative-9bd38c.md @@ -61,7 +61,7 @@ This rule assumes that [visual reference words][] are forms of information conve There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/object-has-accessible-name-8fc3b6.md b/_rules/object-has-accessible-name-8fc3b6.md index 71ec088ddba..a85e339d577 100644 --- a/_rules/object-has-accessible-name-8fc3b6.md +++ b/_rules/object-has-accessible-name-8fc3b6.md @@ -53,7 +53,7 @@ Some screen readers announce `object` elements even if they do not have an acces The [MIME type][] of the resource embedded in the `data` attribute impacts how the [accessible name][] of the `object` is computed. For example, `object` embedding [image MIME type][] may use their `alt` attribute to compute their [accessible name][], but `object` embedding [audio or video MIME types][] may not. An `object` does not officially support the use of an `alt` so this may behave differently according to the browser used. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) diff --git a/_rules/presentational-children-no-focusable-content-307n5z.md b/_rules/presentational-children-no-focusable-content-307n5z.md index bedc34b82b8..6c2d285c774 100755 --- a/_rules/presentational-children-no-focusable-content-307n5z.md +++ b/_rules/presentational-children-no-focusable-content-307n5z.md @@ -43,13 +43,13 @@ This rule assumes that elements that are part of [sequential focus navigation][] Several major browsers ignore the WAI-ARIA requirements on [presentational children][] for most or sometimes all roles, or in presence of focusable content. Since some browsers implement presentational children while others do not, pages failing this rule may only be problematic with some browsers. -This rule is often misunderstood as applying to elements with an _explicit_ role of `presentation`. In fact, this rule only applies to elements which have been given an _implicit_ role of `presentation` through the [presentational children][] mechanism. Similarly, this rule does not apply to elements with `aria-hidden="true"`. +This rule is often misunderstood as applying to elements with an _explicit_ role of `presentation`. In fact, this rule only applies to elements which have been given an _implicit_ role of `presentation` through the [presentational children][] mechanism. Similarly, this rule does not apply to elements with `aria-hidden="true"`. ### Related rules - [Element with aria-hidden has no content in sequential focus navigation](https://www.w3.org/WAI/standards-guidelines/act/rules/6cfa84/) -### Bibliography +### Other Resources - [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) @@ -97,13 +97,12 @@ This element with the `menuitemcheckbox` role has an `input` element as a descen #### Passed Example 4 -This `<button>` element has an `a` element as a [child][]. The `a` element has no `href` attribute, so it isn't included in [sequential focus navigation][]. So this `button` element passes the rule. +This `<button>` element has an `a` element as a [child][]. The `a` element has no `href` attribute, so it isn't included in [sequential focus navigation][]. So this `button` element passes the rule. ```html <button><a>button/link</a></button> ``` - ### Failed #### Failed Example 1 @@ -140,7 +139,7 @@ This element with the `menuitemcheckbox` role has a checkbox as a child. Because #### Failed Example 4 -This element with the `tab` role contains an `a` element. The `tab` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `tab` role fails the rule. (This tablist implementation is non-functional for users. It's not meant to function - it's only meant to show roles.) +This element with the `tab` role contains an `a` element. The `tab` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `tab` role fails the rule. (This tablist implementation is non-functional for users. It's not meant to function - it's only meant to show roles.) ```html <ul role="tablist"> @@ -152,7 +151,7 @@ This element with the `tab` role contains an `a` element. The `tab` role has [p #### Failed Example 5 -This element with the `img` role contains an `a` element. The `img` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `img` role fails the rule. +This element with the `img` role contains an `a` element. The `img` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `img` role fails the rule. ```html <span role="img" aria-label="some ASCII art">****** This ASCII art ******* <a href="#">contains a link.</a></span> @@ -162,7 +161,7 @@ This element with the `img` role contains an `a` element. The `img` role has [p #### Inapplicable Example 1 -None of the roles that build this semantic table structure (`table` for `table`, `row` for `tr`, `columnheader` for `th`, and `cell` for `td`) have [presentational children][]. So this rule does not apply to them. +None of the roles that build this semantic table structure (`table` for `table`, `row` for `tr`, `columnheader` for `th`, and `cell` for `td`) have [presentational children][]. So this rule does not apply to them. ```html <table> @@ -181,7 +180,7 @@ None of the roles that build this semantic table structure (`table` for `table`, #### Inapplicable Example 2 -This `a` element has a `link` role, which does not have [presentational children][]. So this `a` element does not fail this rule, because it's inapplicable. To have a "focusable element within a focusable element" like this is a bad practice, but this rule doesn't directly check for it. +This `a` element has a `link` role, which does not have [presentational children][]. So this `a` element does not fail this rule, because it's inapplicable. To have a "focusable element within a focusable element" like this is a bad practice, but this rule doesn't directly check for it. ```html <a href="https://w3.org"><span tabindex="0">W3C Website</span></a> diff --git a/_rules/printable-characters-shortcut-ffbc54.md b/_rules/printable-characters-shortcut-ffbc54.md index 0725841994e..46b653bff7e 100644 --- a/_rules/printable-characters-shortcut-ffbc54.md +++ b/_rules/printable-characters-shortcut-ffbc54.md @@ -52,7 +52,7 @@ The "Turn off" and "Remap" requirements from [Success Criterion 2.1.4][sc2.1.4] Currently [keyboard events][keyboard event] only support the types `keydown` and `keyup`. [Keyboard events][keyboard event] of type `keypressed` are considered [legacy keyboard events][] and are thus ignored by this rule. -### Bibliography +### Other Resources - [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/WCAG22/Techniques/general/G217) diff --git a/_rules/role-attribute-valid-value-674b10.md b/_rules/role-attribute-valid-value-674b10.md index 714bdba84b9..129bf76ff82 100755 --- a/_rules/role-attribute-valid-value-674b10.md +++ b/_rules/role-attribute-valid-value-674b10.md @@ -57,7 +57,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [List of WAI-ARIA Roles][wai-aria role] - [List of Graphics ARIA Roles](https://www.w3.org/TR/graphics-aria-1.0/#role_definitions) @@ -167,7 +167,7 @@ This `role` attribute is empty (""). This `role` attribute is only [ASCII whitespace][]. ```html -<input type="text" role=" " aria-label="field name"/> +<input type="text" role=" " aria-label="field name" /> ``` #### Inapplicable Example 5 diff --git a/_rules/role-required-states-and-properties-4e8ab6.md b/_rules/role-required-states-and-properties-4e8ab6.md index a07dfa9c6cf..5a25dc2b3d1 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 relies on browsers and assistive technologies to support leaving out [ **Note:** The required states and properties with implicit values can be found in the Core Accessibility API Mappings 1.1 [Overview of default values for missing required attributes](https://www.w3.org/TR/core-aam-1.1/#authorErrorDefaultValuesTable). -### Bibliography +### Other Resources - [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) @@ -121,7 +121,7 @@ This `combobox` has the required properties `aria-controls` and `aria-expanded`. ```html <label for="tag_combo" id="tag_label">Tag</label> -<input type="text" id="tag_combo" role="combobox" aria-expanded="true" aria-controls="popup_listbox"/> +<input type="text" id="tag_combo" role="combobox" aria-expanded="true" aria-controls="popup_listbox" /> <ul role="listbox" id="popup_listbox" aria-labelledby="tag_label"> <li role="option">Zebra</li> <li role="option" id="selected_option">Zoom</li> @@ -197,7 +197,7 @@ This `div` does not have a [semantic role](#semantic-role). This `checkbox` has an [implicit semantic role](#implicit-role) that is identical to the [explicit semantic role](#explicit-role). This allows native HTML `checked` attribute to apply. ```html -<input type="checkbox" role="checkbox" aria-label="Checkbox name"/> +<input type="checkbox" role="checkbox" aria-label="Checkbox name" /> ``` #### Inapplicable Example 3 diff --git a/_rules/scrollable-element-keyboard-accessible-0ssw9k.md b/_rules/scrollable-element-keyboard-accessible-0ssw9k.md index 7e0dc1fa011..2938bab8584 100755 --- a/_rules/scrollable-element-keyboard-accessible-0ssw9k.md +++ b/_rules/scrollable-element-keyboard-accessible-0ssw9k.md @@ -40,8 +40,9 @@ This rule applies to any [HTML element][] that has [visible][] [children][] in t ## Expectation -For each target element, at least one of the following is true: -- the element is included in [sequential focus navigation][]; or +For each target element, at least one of the following is true: + +- the element is included in [sequential focus navigation][]; or - the element has a [descendant][] in the [flat tree][] that is included in [sequential focus navigation][]; or - the element is [inert][]. @@ -61,7 +62,7 @@ Some browsers will automatically make any [scrollable element][scrollable] focus Some browsers restrict scrolling to the [content box](https://drafts.csswg.org/css-box-4/#content-box) of elements; while others allow to scroll the full [border box](https://drafts.csswg.org/css-box-4/#border-box), hence including the element's padding. This results in some elements being scrollable with a browser but not with another. -### Bibliography +### Other Resources - [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) @@ -119,7 +120,7 @@ This [scrollable][] `section` element is [inert][] because of the modal dialog, ```html <style> dialog:-internal-dialog-in-top-layer::backdrop { - background: rgba(1, 1, 1, 0.8); + background: rgba(1, 1, 1, 0.8); } </style> <section style="height: 100px; width: 500px; overflow: scroll;" tabindex="0"> @@ -144,11 +145,11 @@ This [scrollable][] `section` element is [inert][] because of the modal dialog, </dialog> <script> const openDialog = () => { - ppDialog.showModal(); + ppDialog.showModal() myFrame.tabIndex = '-1' } - ppDialog.addEventListener('close', () => myFrame.tabIndex = 0) - window.addEventListener('DOMContentLoaded', openDialog); + ppDialog.addEventListener('close', () => (myFrame.tabIndex = 0)) + window.addEventListener('DOMContentLoaded', openDialog) </script> ``` diff --git a/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md b/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md index 0bc18809990..9626c5c43dd 100755 --- a/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md +++ b/_rules/sequentially-focusable-element-has-visible-focus-oj04fd.md @@ -45,7 +45,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [Success Criterion 2.4.7 Focus Visible][sc247] - [Success Criterion 2.4.11 Focus Appearance][sc2411] diff --git a/_rules/summary-non-empty-accessible-name-2t702h.md b/_rules/summary-non-empty-accessible-name-2t702h.md index 16daefd47ff..b435ae447c4 100755 --- a/_rules/summary-non-empty-accessible-name-2t702h.md +++ b/_rules/summary-non-empty-accessible-name-2t702h.md @@ -48,7 +48,7 @@ The rule assumes that all `summary` elements are [user interface components as d There is a difference in how user agents expose the triangle indicating the control's expand state. As a result, some user agents include the triangle in the accessible name of the summary element. -### Bibliography +### Other Resources - [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) diff --git a/_rules/table-header-cell-has-assigned-cells-d0f69e.md b/_rules/table-header-cell-has-assigned-cells-d0f69e.md index 309ba623771..320b231a40f 100755 --- a/_rules/table-header-cell-has-assigned-cells-d0f69e.md +++ b/_rules/table-header-cell-has-assigned-cells-d0f69e.md @@ -50,7 +50,7 @@ This rule assumes that table header cells have a relationship conveyed through p - Table markup and header cell association is not well supported by some popular assistive technologies. Passing this rule can still cause issues for users of those assistive technologies. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have one of the applicable [semantic roles][semantic role] and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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/WCAG22/Techniques/html/H43) 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 b139316707a..15f79d82c01 100755 --- a/_rules/table-headers-attribute-refer-to-data-cells-a25f45.md +++ b/_rules/table-headers-attribute-refer-to-data-cells-a25f45.md @@ -55,7 +55,7 @@ Each target's [attribute value][] is a [set of space separated tokens][], and no There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/text-contrast-afw4f7.md b/_rules/text-contrast-afw4f7.md index 1fc8c5fead3..bc06aba3df9 100755 --- a/_rules/text-contrast-afw4f7.md +++ b/_rules/text-contrast-afw4f7.md @@ -58,7 +58,7 @@ When the text color or background color is not specified in the web page, colors - Different browsers have different levels of support for CSS. This can cause contrast issues in one browser that do not appear in another. Because of that, this rule can produce different results depending on the browser that is used. For example, a text that is positioned using CSS transform may be on a different background in a browser that does not support CSS transform. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have a [semantic role][] of `none` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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) diff --git a/_rules/text-contrast-enhanced-09o5cg.md b/_rules/text-contrast-enhanced-09o5cg.md index 25394bb2f1a..55fb23596f1 100644 --- a/_rules/text-contrast-enhanced-09o5cg.md +++ b/_rules/text-contrast-enhanced-09o5cg.md @@ -69,7 +69,7 @@ This rule is closely related to [success criterion 1.4.3 Contrast (Minimum)][sc1 - Different browsers have different levels of support for CSS. This can cause contrast issues in one browser that do not appear in another. Because of that, this rule can produce different results depending on the browser that is used. For example, a text that is positioned using CSS transform may be on a different background in a browser that does not support CSS transform. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have a [semantic role][] of `none` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-alternative-for-auditory-eac66b.md b/_rules/video-alternative-for-auditory-eac66b.md index f7a35420c6d..61dc9503d30 100755 --- a/_rules/video-alternative-for-auditory-eac66b.md +++ b/_rules/video-alternative-for-auditory-eac66b.md @@ -61,7 +61,7 @@ For each test target, the [outcome](#outcome) of at least one of the following r There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-alternative-for-visual-c5a4ea.md b/_rules/video-alternative-for-visual-c5a4ea.md index 243526d34e8..8f809851917 100755 --- a/_rules/video-alternative-for-visual-c5a4ea.md +++ b/_rules/video-alternative-for-visual-c5a4ea.md @@ -73,7 +73,7 @@ For each test target, the [outcome](#outcome) of at least one of the following r 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]. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-as-media-alternative-ab4d13.md b/_rules/video-as-media-alternative-ab4d13.md index f8546499bb4..02d75df8187 100755 --- a/_rules/video-as-media-alternative-ab4d13.md +++ b/_rules/video-as-media-alternative-ab4d13.md @@ -43,7 +43,7 @@ This rule assumes that a mechanism is available to start the video and that the There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-audio-description-1ea59c.md b/_rules/video-audio-description-1ea59c.md index 7294dfce180..601143f3f97 100755 --- a/_rules/video-audio-description-1ea59c.md +++ b/_rules/video-audio-description-1ea59c.md @@ -55,7 +55,7 @@ This rule assumes that a mechanism is available to start the video and that the There are only a few implementations of video players (without third party technologies) that support audio description tracks at the time of writing. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-captions-f51b46.md b/_rules/video-captions-f51b46.md index ddd65837378..42b4dcac6bb 100755 --- a/_rules/video-captions-f51b46.md +++ b/_rules/video-captions-f51b46.md @@ -58,7 +58,7 @@ This rule assumes that the video element is used to play a video (for example, n There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-description-track-f196ce.md b/_rules/video-description-track-f196ce.md index 1d067ea0c22..803e732a9f8 100755 --- a/_rules/video-description-track-f196ce.md +++ b/_rules/video-description-track-f196ce.md @@ -56,7 +56,7 @@ Currently the description track is not supported by most assistive technology. A This means that the rule can only provide a pass for these success criteria if assistive technology support the description track or if the video player that is used has implemented such a work around. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-only-alternative-for-visual-c3232f.md b/_rules/video-only-alternative-for-visual-c3232f.md index 00c194a28f3..9d2719ee94f 100755 --- a/_rules/video-only-alternative-for-visual-c3232f.md +++ b/_rules/video-only-alternative-for-visual-c3232f.md @@ -65,7 +65,7 @@ For each test target, the [outcome](#outcome) of at least one of the following r 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). -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-only-as-media-alternative-fd26cf.md b/_rules/video-only-as-media-alternative-fd26cf.md index 95c8d63a121..6e0a31082d1 100755 --- a/_rules/video-only-as-media-alternative-fd26cf.md +++ b/_rules/video-only-as-media-alternative-fd26cf.md @@ -45,7 +45,7 @@ A mechanism is available to start the video and that the video element is not si There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-only-audio-track-d7ba54.md b/_rules/video-only-audio-track-d7ba54.md index 04b1496aa81..1530efff274 100755 --- a/_rules/video-only-audio-track-d7ba54.md +++ b/_rules/video-only-audio-track-d7ba54.md @@ -44,7 +44,7 @@ This rule assumes that a mechanism is available to start the video and that the There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-only-description-track-ac7dc6.md b/_rules/video-only-description-track-ac7dc6.md index d7fc79c5fc6..df3b37bfad4 100755 --- a/_rules/video-only-description-track-ac7dc6.md +++ b/_rules/video-only-description-track-ac7dc6.md @@ -49,7 +49,7 @@ This rule assumes that a mechanism is available to start the video and that the Currently the description track is not supported by most assistive technologies. Video players may be able to work around the lack of support for the description track by using aria-live but few do this today. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-only-transcript-ee13b5.md b/_rules/video-only-transcript-ee13b5.md index 844fab02cca..666e77134c7 100755 --- a/_rules/video-only-transcript-ee13b5.md +++ b/_rules/video-only-transcript-ee13b5.md @@ -51,7 +51,7 @@ A mechanism is available to start the video and that the video element is not si There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-strict-alternative-for-visual-1ec09b.md b/_rules/video-strict-alternative-for-visual-1ec09b.md index 2eee0bdae2b..0d00191c8ae 100755 --- a/_rules/video-strict-alternative-for-visual-1ec09b.md +++ b/_rules/video-strict-alternative-for-visual-1ec09b.md @@ -62,7 +62,7 @@ For each test target, the [outcome](#outcome) of at least one of the following r 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). -### Bibliography +### Other Resources - [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) diff --git a/_rules/video-transcript-1a02b0.md b/_rules/video-transcript-1a02b0.md index 33dd7ac227f..44468be0b4c 100755 --- a/_rules/video-transcript-1a02b0.md +++ b/_rules/video-transcript-1a02b0.md @@ -56,7 +56,7 @@ This rule assumes that a mechanism is available to start the video and that the There are no accessibility support issues known. -### Bibliography +### Other Resources - [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) diff --git a/_rules/visible-label-in-accessible-name-2ee8b8.md b/_rules/visible-label-in-accessible-name-2ee8b8.md index 79056bf12f6..65daa251c21 100755 --- a/_rules/visible-label-in-accessible-name-2ee8b8.md +++ b/_rules/visible-label-in-accessible-name-2ee8b8.md @@ -55,7 +55,7 @@ This rule assumes that all resources needed for rendering the page are properly Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have one of the applicable [semantic roles][semantic role] and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [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/WCAG22/Techniques/general/G208) diff --git a/_rules/zoom-text-no-overflow-clipping-59br37.md b/_rules/zoom-text-no-overflow-clipping-59br37.md index 6f6e71acdc8..134c509d386 100755 --- a/_rules/zoom-text-no-overflow-clipping-59br37.md +++ b/_rules/zoom-text-no-overflow-clipping-59br37.md @@ -60,7 +60,7 @@ If any of the following assumptions is true, failing this rule may not result in Some user agents treat the value of the `aria-hidden` attribute as case-sensitive. -### Bibliography +### Other Resources - [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) diff --git a/pages/design/atomic-template-empty.md b/pages/design/atomic-template-empty.md index bdd1180c3ac..1be5d702a0a 100755 --- a/pages/design/atomic-template-empty.md +++ b/pages/design/atomic-template-empty.md @@ -65,7 +65,7 @@ There are no accessibility support issues known. - [rule name here](./abc123) -### Bibliography +### Other Resources <!-- This section is optional --> diff --git a/pages/design/composite-template-empty.md b/pages/design/composite-template-empty.md index 555d6d0f9f9..0fa976f7546 100755 --- a/pages/design/composite-template-empty.md +++ b/pages/design/composite-template-empty.md @@ -68,7 +68,7 @@ There are no accessibility support issues known. - [rule name here](./abc123) -### Bibliography +### Other Resources <!-- This section is optional --> diff --git a/pages/design/manual-template-empty.md b/pages/design/manual-template-empty.md index 337f676b9ce..367ec984bef 100644 --- a/pages/design/manual-template-empty.md +++ b/pages/design/manual-template-empty.md @@ -71,7 +71,7 @@ There are no accessibility support issues known. - [rule name here](./abc123) -### Bibliography +### Other Resources <!-- This section is optional --> diff --git a/pages/design/rule-template.md b/pages/design/rule-template.md index 0a74a8f820b..36f99920770 100755 --- a/pages/design/rule-template.md +++ b/pages/design/rule-template.md @@ -81,7 +81,7 @@ There are no accessibility support issues known. - [rule name here](./abc123) -### Bibliography +### Other Resources <!-- This section is optional --> @@ -214,7 +214,7 @@ There are no accessibility support issues known. - [rule name here](./abc123) -### Bibliography +### Other Resources <!-- This section is optional -->