diff --git a/_rules/aria-required-context-role-ff89c9.md b/_rules/aria-required-context-role-ff89c9.md index 67461d2e92f..1b8c8fb7437 100755 --- a/_rules/aria-required-context-role-ff89c9.md +++ b/_rules/aria-required-context-role-ff89c9.md @@ -42,6 +42,7 @@ The rule assumes that the [explicit role][] of the applicable elements is approp - User agents do not all have the same accessibility tree. This can lead to different results for this rule, depending on which accessibility tree is used as input. - `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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/aria-required-owned-element-bc4a75.md b/_rules/aria-required-owned-element-bc4a75.md index 828baa16c26..6902a54918c 100755 --- a/_rules/aria-required-owned-element-bc4a75.md +++ b/_rules/aria-required-owned-element-bc4a75.md @@ -44,6 +44,7 @@ If the [explicit semantic role][] on the target element is incorrectly used, and - `aria-owns` has limited support in some user agents. - 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/aria-state-or-property-permitted-5c01ea.md b/_rules/aria-state-or-property-permitted-5c01ea.md index e33da0e7dec..7a54d5cd976 100755 --- a/_rules/aria-state-or-property-permitted-5c01ea.md +++ b/_rules/aria-state-or-property-permitted-5c01ea.md @@ -56,7 +56,8 @@ There are no assumptions. ## Accessibility Support -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 their attributes fail this rule with some technologies but users of other technology would not experience any accessibility issue. +- 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 their attributes fail this rule with some technologies but users of other technology would not experience any accessibility issue. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 8ce17821e7d..1612d4338b8 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -58,6 +58,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. - Some user agents treat the value of the `aria-disabled` attribute as case-sensitive. - In some user agents, querying the value of the `autocomplete` property returns an empty string ("") even when the attribute was set according to the rule's expectations. It affects assistive technologies which rely on this property to personalize input fields collecting information about the user. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/block-collapsible-3e12e1.md b/_rules/block-collapsible-3e12e1.md index 54d169595c5..c22e50559fa 100755 --- a/_rules/block-collapsible-3e12e1.md +++ b/_rules/block-collapsible-3e12e1.md @@ -40,7 +40,7 @@ There are no assumptions. ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/button-non-empty-accessible-name-97a4e1.md b/_rules/button-non-empty-accessible-name-97a4e1.md index 253722c4477..e5a11e76b31 100755 --- a/_rules/button-non-empty-accessible-name-97a4e1.md +++ b/_rules/button-non-empty-accessible-name-97a4e1.md @@ -37,8 +37,8 @@ Each target element has an [accessible name][] that is not empty (`""`). ## Accessibility Support - 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 `button` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. - - Some elements have a role of `button` and a default accessible name defined by the [HTML Accessibility API Mapping][html aam input button], for example `input` elements whose `type` [attribute value][] is either `submit` or `reset`. This rule considers that these default names can be descriptive and therefore does not fail them. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/device-motion-disabled-c249d5.md b/_rules/device-motion-disabled-c249d5.md index 6fd8e663e79..671d77aefb6 100755 --- a/_rules/device-motion-disabled-c249d5.md +++ b/_rules/device-motion-disabled-c249d5.md @@ -49,7 +49,7 @@ For each registered [device orientation event][device orientation] or [device mo ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/device-motion-user-interface-7677a9.md b/_rules/device-motion-user-interface-7677a9.md index e3bea3a8deb..9913a2b081a 100755 --- a/_rules/device-motion-user-interface-7677a9.md +++ b/_rules/device-motion-user-interface-7677a9.md @@ -46,7 +46,7 @@ For each registered [device orientation event][device orientation] or [device mo ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background 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 32ccdeea247..1947ccc8786 100755 --- a/_rules/document-has-headings-for-non-repeated-content-047fe0.md +++ b/_rules/document-has-headings-for-non-repeated-content-047fe0.md @@ -46,6 +46,7 @@ In each test target, either there is no [non-repeated content after repeated con - 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]. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background 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 40e7d86d605..b825b317a5d 100755 --- a/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md +++ b/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md @@ -48,7 +48,7 @@ This rule assumes that there is at least one [block of repeated content][] befor ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background 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 51f64e77d02..acd0a54f9fb 100755 --- a/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md +++ b/_rules/document-has-landmark-with-non-repeated-content-b40fd1.md @@ -38,7 +38,8 @@ Within each test target, either there is no [non-repeated content after repeated ## Accessibility Support -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. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/element-lang-matches-default-language-off6ek.md b/_rules/element-lang-matches-default-language-off6ek.md index 193a6717220..17257d25d88 100644 --- a/_rules/element-lang-matches-default-language-off6ek.md +++ b/_rules/element-lang-matches-default-language-off6ek.md @@ -54,7 +54,7 @@ For each test target, the [primary language][] of its `lang` [attribute value][] ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/element-lang-valid-de46e4.md b/_rules/element-lang-valid-de46e4.md index 18baddbac22..b337de11af8 100755 --- a/_rules/element-lang-valid-de46e4.md +++ b/_rules/element-lang-valid-de46e4.md @@ -51,7 +51,8 @@ For each test target, the `lang` [attribute value][] has a [known primary langua ## Accessibility Support -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. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/element-marked-decorative-is-not-exposed-46ca7f.md b/_rules/element-marked-decorative-is-not-exposed-46ca7f.md index 3153f81e41b..78960b211dd 100755 --- a/_rules/element-marked-decorative-is-not-exposed-46ca7f.md +++ b/_rules/element-marked-decorative-is-not-exposed-46ca7f.md @@ -34,7 +34,8 @@ There are no assumptions. ## Accessibility Support -Implementation of the [Presentational Roles Conflict Resolution][] differs slightly from one user agent to the other. Hence, some elements might be exposed by one user agent and not by another, and consequently might create accessibility issues only for some users. Nevertheless, triggering the conflict is a bad practice. +- Implementation of the [Presentational Roles Conflict Resolution][] differs slightly from one user agent to the other. Hence, some elements might be exposed by one user agent and not by another, and consequently might create accessibility issues only for some users. Nevertheless, triggering the conflict is a bad practice. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/form-field-label-descriptive-cc0f0a.md b/_rules/form-field-label-descriptive-cc0f0a.md index dfbbf37bd89..ad1c7ec46c9 100755 --- a/_rules/form-field-label-descriptive-cc0f0a.md +++ b/_rules/form-field-label-descriptive-cc0f0a.md @@ -61,6 +61,7 @@ Each test target, together with its [visual context][], describes the purpose of ## Accessibility Support - 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/form-field-non-empty-accessible-name-e086e5.md b/_rules/form-field-non-empty-accessible-name-e086e5.md index d71625aff77..f09d99da240 100755 --- a/_rules/form-field-non-empty-accessible-name-e086e5.md +++ b/_rules/form-field-non-empty-accessible-name-e086e5.md @@ -38,6 +38,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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md index c7ed03f9d17..dcfac57f102 100755 --- a/_rules/heading-descriptive-b49b2e.md +++ b/_rules/heading-descriptive-b49b2e.md @@ -43,7 +43,8 @@ This rule also assumes that the content the heading is intended to describe is [ ## Accessibility Support -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. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/heading-non-empty-accessible-name-ffd0e9.md b/_rules/heading-non-empty-accessible-name-ffd0e9.md index 6431cb0b893..febf2c5fd36 100755 --- a/_rules/heading-non-empty-accessible-name-ffd0e9.md +++ b/_rules/heading-non-empty-accessible-name-ffd0e9.md @@ -38,10 +38,9 @@ There are no assumptions. ## Accessibility Support - Some assistive technologies may hide headings with empty [accessible name][] from the users. This depends on the user agent, on how the [accessible name][] was computed (the [accessible name and description computation][] is not clear concerning which characters should be trimmed), and on the assistive technology itself. Hence, there are cases where the outcome of this rule is _failed_, but users of certain assistive technology and browser combinations will not experience an issue. - - 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 because the same elements would have a [semantic role][] of `presentation` and be hidden for these users. - - 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). +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/html-page-lang-matches-default-ucwvc8.md b/_rules/html-page-lang-matches-default-ucwvc8.md index 9500634216b..8ccdce3cb9b 100755 --- a/_rules/html-page-lang-matches-default-ucwvc8.md +++ b/_rules/html-page-lang-matches-default-ucwvc8.md @@ -58,7 +58,7 @@ For each test target, the [known primary language tag][] of its `lang` attribute ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/image-accessible-name-descriptive-qt1vmo.md b/_rules/image-accessible-name-descriptive-qt1vmo.md index aa304ce6c8b..36fe4399ce2 100755 --- a/_rules/image-accessible-name-descriptive-qt1vmo.md +++ b/_rules/image-accessible-name-descriptive-qt1vmo.md @@ -58,7 +58,8 @@ There are no assumptions. ## Accessibility Support -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. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/image-filename-as-accessible-name-9eb3f6.md b/_rules/image-filename-as-accessible-name-9eb3f6.md index 5fd7bcdfa47..d5a2d6ef108 100755 --- a/_rules/image-filename-as-accessible-name-9eb3f6.md +++ b/_rules/image-filename-as-accessible-name-9eb3f6.md @@ -62,7 +62,7 @@ There are no assumptions. ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/image-non-empty-accessible-name-23a2a8.md b/_rules/image-non-empty-accessible-name-23a2a8.md index e4c27e4562b..b33797fad95 100755 --- a/_rules/image-non-empty-accessible-name-23a2a8.md +++ b/_rules/image-non-empty-accessible-name-23a2a8.md @@ -55,6 +55,7 @@ There are no assumptions. - There are several popular browsers that do not treat images with an empty `alt` attribute (`alt=""`) as having a role of `presentation` but instead add the `img` element to the accessibility tree with a [semantic role][] of either `img` or `graphic`. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `img` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. - 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background 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 bae30ea4335..a0425db46e5 100755 --- a/_rules/image-not-in-acc-tree-is-decorative-e88epe.md +++ b/_rules/image-not-in-acc-tree-is-decorative-e88epe.md @@ -59,7 +59,7 @@ Each test target is [purely decorative][]. ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/link-alone-descriptive-aizyf1.md b/_rules/link-alone-descriptive-aizyf1.md index b4d5299adf7..1bc71ff61e2 100755 --- a/_rules/link-alone-descriptive-aizyf1.md +++ b/_rules/link-alone-descriptive-aizyf1.md @@ -41,6 +41,7 @@ Each test target has an [accessible name][] which describes its purpose. ## Accessibility Support - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `link` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/link-in-context-descriptive-5effbb.md b/_rules/link-in-context-descriptive-5effbb.md index 58685819197..3e96a33612f 100755 --- a/_rules/link-in-context-descriptive-5effbb.md +++ b/_rules/link-in-context-descriptive-5effbb.md @@ -46,6 +46,7 @@ The [accessible name][] of each target element together with its [programmatical ## Accessibility Support - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `link` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/link-non-empty-accessible-name-c487ae.md b/_rules/link-non-empty-accessible-name-c487ae.md index 9c1fd537c24..1833d92c349 100755 --- a/_rules/link-non-empty-accessible-name-c487ae.md +++ b/_rules/link-non-empty-accessible-name-c487ae.md @@ -62,6 +62,7 @@ The rule assumes that all links are [user interface components](https://www.w3.o - For `area` elements that have an `href` attribute, but are not nested inside a `map` element, there are differences between browsers and assistive technology on if the `area` is [included in the accessibility tree][]. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `link` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue. - Accessibility support for some elements inheriting the semantic role of `link` (e.g. elements with `doc-*` attributes) may vary depending on the assistive technology in use. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/links-identical-name-equivalent-purpose-b20e66.md b/_rules/links-identical-name-equivalent-purpose-b20e66.md index 9ee15e68a7f..1c8485d6ada 100755 --- a/_rules/links-identical-name-equivalent-purpose-b20e66.md +++ b/_rules/links-identical-name-equivalent-purpose-b20e66.md @@ -54,6 +54,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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/menuitem-non-empty-name-m6b1q3.md b/_rules/menuitem-non-empty-name-m6b1q3.md index cf73f3bfdb6..02c1dd459bc 100755 --- a/_rules/menuitem-non-empty-name-m6b1q3.md +++ b/_rules/menuitem-non-empty-name-m6b1q3.md @@ -37,7 +37,8 @@ This rule assumes that all menuitems are [user interface components as defined b ## Accessibility Support -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. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/non-visual-reference-alternative-9bd38c.md b/_rules/non-visual-reference-alternative-9bd38c.md index f054381ad0e..7316459ebb7 100755 --- a/_rules/non-visual-reference-alternative-9bd38c.md +++ b/_rules/non-visual-reference-alternative-9bd38c.md @@ -50,7 +50,7 @@ This rule assumes that [visual reference words][] are forms of information conve ## Accessibility Support -There are no accessibility support issues known. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/object-has-accessible-name-8fc3b6.md b/_rules/object-has-accessible-name-8fc3b6.md index f5e7cdb189f..acd58e94959 100644 --- a/_rules/object-has-accessible-name-8fc3b6.md +++ b/_rules/object-has-accessible-name-8fc3b6.md @@ -42,9 +42,9 @@ _There are currently no assumptions_ ## Accessibility Support -Some screen readers announce `object` elements even if they do not have an accessible name, while other skip the element. If an `object` is used to render decorative content, to ensure it is [marked as decorative][] and can be ignored by all major screen readers a presentational role is necessary. - -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. +- Some screen readers announce `object` elements even if they do not have an accessible name, while other skip the element. If an `object` is used to render decorative content, to ensure it is [marked as decorative][] and can be ignored by all major screen readers a presentational role is necessary. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/table-header-cell-has-assigned-cells-d0f69e.md b/_rules/table-header-cell-has-assigned-cells-d0f69e.md index ac2beeef340..360041b0a3b 100755 --- a/_rules/table-header-cell-has-assigned-cells-d0f69e.md +++ b/_rules/table-header-cell-has-assigned-cells-d0f69e.md @@ -44,6 +44,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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/text-contrast-afw4f7.md b/_rules/text-contrast-afw4f7.md index 5b74a6e332b..6bdeb041c20 100755 --- a/_rules/text-contrast-afw4f7.md +++ b/_rules/text-contrast-afw4f7.md @@ -50,6 +50,7 @@ For each test target, the [highest possible contrast][] between the [foreground - 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/text-contrast-enhanced-09o5cg.md b/_rules/text-contrast-enhanced-09o5cg.md index 7a30c9f135b..e7d41981617 100644 --- a/_rules/text-contrast-enhanced-09o5cg.md +++ b/_rules/text-contrast-enhanced-09o5cg.md @@ -59,6 +59,7 @@ For each test target, the [highest possible contrast][] between the [foreground - 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background diff --git a/_rules/visible-label-in-accessible-name-2ee8b8.md b/_rules/visible-label-in-accessible-name-2ee8b8.md index 570437a592c..f555a1fac07 100755 --- a/_rules/visible-label-in-accessible-name-2ee8b8.md +++ b/_rules/visible-label-in-accessible-name-2ee8b8.md @@ -46,7 +46,8 @@ This rule assumes that all resources needed for rendering the page are properly ## Accessibility Support -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. +- 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. +- `aria-busy` exists but, currently, is not widely supported, so the rule ignores it. ## Background @@ -145,7 +146,7 @@ This link has [visible][] text with mathematical symbols, that does not match th #### Failed Example 4 -This link has [visible][] text does not match the [accessible name][] because there is a hyphen in the accessible name. +This link has [visible][] text does not match the [accessible name][] because there is a hyphen in the accessible name. ```html nonstandard @@ -153,7 +154,7 @@ This link has [visible][] text does not match the [accessible name][] because th #### Failed Example 5 -This link has [visible][] text does not match the [accessible name][] because there are extra spaces in the accessible name. +This link has [visible][] text does not match the [accessible name][] because there are extra spaces in the accessible name. ```html 123.456.7890