From 55769d5800e3bbba26d29998b7266a3bce8b4495 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 16 Jun 2022 15:09:59 +0200 Subject: [PATCH 01/15] Update image-button-non-empty-accessible-name-59796f.md Added: * failed example 3 * updated "Accessibility Support" section --- .../image-button-non-empty-accessible-name-59796f.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index f962b55cf92..fbe04b1d078 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -56,6 +56,8 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor There is a known combination of a popular browser and assistive technology that does not by default support `title` as an [accessible name][]. +The image button with non-empty `title` attribute but empty `alt` attribute results in a button with empty accessible name on many browsers. On Firefox, instead, the `title` attribute is used as fallback, resulting in a button with `title` attribute value as accessible name. + ## Background ### Related rules @@ -128,6 +130,14 @@ The image button has an empty `alt` attribute, and no other attributes that can #### Failed Example 3 +The image button has a non-empty `title` attribute, but an empty `alt` attribute, hence its name is the default "Submit Query". + +```html + +``` + +#### Failed Example 4 + The image button has an `aria-labelledby` attribute, but the referenced element does not exist. This gives the button the default [accessible name][] of "Submit Query". ```html From 0f08f4d72714ef8e24954bef98b19696a7fd121f Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 16 Jun 2022 22:07:43 +0200 Subject: [PATCH 02/15] Update image-button-non-empty-accessible-name-59796f.md --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index fbe04b1d078..fde4cb60977 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -56,7 +56,7 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor There is a known combination of a popular browser and assistive technology that does not by default support `title` as an [accessible name][]. -The image button with non-empty `title` attribute but empty `alt` attribute results in a button with empty accessible name on many browsers. On Firefox, instead, the `title` attribute is used as fallback, resulting in a button with `title` attribute value as accessible name. +The image button with non-empty `title` attribute but empty `alt` attribute results in a button with empty accessible name on many browsers. There is a known popular browser instead, that uses the `title` attribute as fallback even with empty `alt`, resulting in a button with `title` attribute value as accessible name. ## Background From c187abdd3ecaf5fae1805872ba7aa2261298031b Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 16 Jun 2022 22:16:13 +0200 Subject: [PATCH 03/15] Update _rules/image-button-non-empty-accessible-name-59796f.md Co-authored-by: Carlos Duarte --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index fde4cb60977..cc45b1af30e 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -56,7 +56,7 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor There is a known combination of a popular browser and assistive technology that does not by default support `title` as an [accessible name][]. -The image button with non-empty `title` attribute but empty `alt` attribute results in a button with empty accessible name on many browsers. There is a known popular browser instead, that uses the `title` attribute as fallback even with empty `alt`, resulting in a button with `title` attribute value as accessible name. +The image button with non-empty `title` attribute but empty `alt` attribute results in a button with empty accessible name on many browsers. There is a known popular browser that uses the `title` attribute as fallback even with empty `alt`, resulting in a button with `title` attribute value as accessible name. ## Background From 6522306f44d2b820f8b0e3bee5af21ca5c630cef Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 16 Jun 2022 22:29:31 +0200 Subject: [PATCH 04/15] Update image-button-non-empty-accessible-name-59796f.md My mistake; the resulting accessible name of Failed example 3 is empty (except for Firefox), not default "submit query". --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index cc45b1af30e..769d4ea51ae 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -130,7 +130,7 @@ The image button has an empty `alt` attribute, and no other attributes that can #### Failed Example 3 -The image button has a non-empty `title` attribute, but an empty `alt` attribute, hence its name is the default "Submit Query". +The image button has a non-empty `title` attribute, but an empty `alt` attribute. This gives the button an empty [accessible name][]. ```html From 0bcbfa9641511ed1b17ae468fb92437938fbf3cf Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 23 Jun 2022 14:28:08 +0200 Subject: [PATCH 05/15] Update _rules/image-button-non-empty-accessible-name-59796f.md Co-authored-by: Jean-Yves Moyen --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 769d4ea51ae..46ff7493f37 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -130,7 +130,7 @@ The image button has an empty `alt` attribute, and no other attributes that can #### Failed Example 3 -The image button has a non-empty `title` attribute, but an empty `alt` attribute. This gives the button an empty [accessible name][]. +This image button has a non-empty `title` attribute, but an empty `alt` attribute. This gives the button an empty [accessible name][]. ```html From 1de8b68cc1709c8675d552961af9dd3a224cfe7a Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 23 Jun 2022 14:28:48 +0200 Subject: [PATCH 06/15] Update _rules/image-button-non-empty-accessible-name-59796f.md Co-authored-by: Jean-Yves Moyen --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 46ff7493f37..df29150e152 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -56,7 +56,7 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor There is a known combination of a popular browser and assistive technology that does not by default support `title` as an [accessible name][]. -The image button with non-empty `title` attribute but empty `alt` attribute results in a button with empty accessible name on many browsers. There is a known popular browser that uses the `title` attribute as fallback even with empty `alt`, resulting in a button with `title` attribute value as accessible name. +An image button with non-empty `title` attribute but empty `alt` attribute results in a button with an empty accessible name on many browsers. There is a known popular browser that uses the `title` attribute as fallback even with empty `alt`, resulting in a button with `title` attribute value as accessible name. ## Background From 5337c5b83fc8dd7d5f9a5016d3daa02065f159df Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Fri, 8 Jul 2022 09:52:08 +0200 Subject: [PATCH 07/15] Update image-button-non-empty-accessible-name-59796f.md --- ...button-non-empty-accessible-name-59796f.md | 21 +++++++++++-------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index df29150e152..60708d5083f 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -56,10 +56,13 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor There is a known combination of a popular browser and assistive technology that does not by default support `title` as an [accessible name][]. -An image button with non-empty `title` attribute but empty `alt` attribute results in a button with an empty accessible name on many browsers. There is a known popular browser that uses the `title` attribute as fallback even with empty `alt`, resulting in a button with `title` attribute value as accessible name. +The [input type="image" Accessible Name Computation algorithm](https://www.w3.org/TR/html-aam/#input-type-image-accessible-name-computation) uses the first non-empty name, but some AU/AT stop at the first existing one, even if empty. ## Background +Empty `alt` does not provide a "usable string" for `input` element with a `type` [attribute value][] of `image`. +Therefore, contrarily to images, empty `alt` does not make image button decorative. Image buttons have a button role and therefore are exposed as interactive elements. + ### Related rules - [Button has non-empty accessible name](https://act-rules.github.io/rules/97a4e1) @@ -110,6 +113,14 @@ The image button has an [accessible name][] through the `aria-labelledby` attrib
Search
``` +#### Passed Example 5 + +This image button has an empty `alt` attribute, but a non-empty `title` attribute. This gives the button an non-empty [accessible name][] through the `title` attribute. + +```html + +``` + ### Failed #### Failed Example 1 @@ -128,14 +139,6 @@ The image button has an empty `alt` attribute, and no other attributes that can ``` -#### Failed Example 3 - -This image button has a non-empty `title` attribute, but an empty `alt` attribute. This gives the button an empty [accessible name][]. - -```html - -``` - #### Failed Example 4 The image button has an `aria-labelledby` attribute, but the referenced element does not exist. This gives the button the default [accessible name][] of "Submit Query". From f9ff94a0a420443f96ad9f213dfd3d9783b1fc79 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Fri, 8 Jul 2022 09:52:35 +0200 Subject: [PATCH 08/15] Update image-button-non-empty-accessible-name-59796f.md --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 60708d5083f..91314ed2557 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -139,7 +139,7 @@ The image button has an empty `alt` attribute, and no other attributes that can ``` -#### Failed Example 4 +#### Failed Example 3 The image button has an `aria-labelledby` attribute, but the referenced element does not exist. This gives the button the default [accessible name][] of "Submit Query". From d1da8542d38324c2d177e9963bf9ec03c0a87781 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Mon, 8 Aug 2022 09:23:40 +0200 Subject: [PATCH 09/15] Apply suggestions from code review Co-authored-by: Jean-Yves Moyen --- _rules/image-button-non-empty-accessible-name-59796f.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 91314ed2557..9d948301b29 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -56,12 +56,11 @@ Each target element has an [accessible name][] that is neither empty (`""`), nor There is a known combination of a popular browser and assistive technology that does not by default support `title` as an [accessible name][]. -The [input type="image" Accessible Name Computation algorithm](https://www.w3.org/TR/html-aam/#input-type-image-accessible-name-computation) uses the first non-empty name, but some AU/AT stop at the first existing one, even if empty. +The [input type="image" Accessible Name Computation algorithm](https://www.w3.org/TR/html-aam/#input-type-image-accessible-name-computation) uses the first non-empty name, but some user agents and assistive technologies combinations stop at the first existing one, even if empty. ## Background -Empty `alt` does not provide a "usable string" for `input` element with a `type` [attribute value][] of `image`. -Therefore, contrarily to images, empty `alt` does not make image button decorative. Image buttons have a button role and therefore are exposed as interactive elements. +Contrarily to images, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation default to other means of providing a name. ### Related rules From 167a53d15ab795fc5a695020ca3ea735cdf0981f Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Mon, 8 Aug 2022 12:42:26 +0200 Subject: [PATCH 10/15] Create error-field-is-not-ifentified-using-color-differences-only --- ...ot-ifentified-using-color-differences-only | 108 ++++++++++++++++++ 1 file changed, 108 insertions(+) create mode 100644 _rules/error-field-is-not-ifentified-using-color-differences-only diff --git a/_rules/error-field-is-not-ifentified-using-color-differences-only b/_rules/error-field-is-not-ifentified-using-color-differences-only new file mode 100644 index 00000000000..48e9955ae23 --- /dev/null +++ b/_rules/error-field-is-not-ifentified-using-color-differences-only @@ -0,0 +1,108 @@ +--- +id: +name: Error field is not identified using color differences only +rule_type: atomic +description: | + This rule checks that error fields can be identified not only by color differences but through another visual means. +accessibility_requirements: # Remove whatever is not applicable + wcag21:1.4.1: # Use of Color (A) + forConformance: true + failed: not satisfied + passed: further testing needed + inapplicable: further testing needed +input_aspects: + - DOM Tree + - CSS Styling +acknowledgments: + authors: + - Giacomo Petri +--- + +## Applicability + +This rule applies to any error field that is [visible][]. + +## Expectation (1) + +Each test target, together with its visual context, identify the presence of errors not only through color differences. + +## Assumptions + +https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html +If the presence of errors is conveyed through the use of colors that differ not only in their hue, but that also have a difference in lightness and the difference in relative luminance between the colors leads to a contrast ratio of 3:1 or greater, then this counts as an additional visual mean. + +*Note*: It is possible for an error field to be distinguishable from adjacent fields but still not have a meaningful error message. In that case, it would pass Success Criterion 1.4.1: Use of Color but still fail [Success Criterion 3.3.1: Error Identification](https://www.w3.org/WAI/WCAG21/Understanding/error-identification.html) and, if applicable, [Scuccess Criterion 3.3.3: Error Suggestion](https://www.w3.org/WAI/WCAG21/Understanding/error-suggestion.html). + +## Accessibility Support + +_No accessibility support issues known._ + +## Background + +- [Understanding Success Criterion 1.4.1: Use of Color](https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html) +- [F81 - Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only](https://www.w3.org/WAI/WCAG21/Techniques/failures/F81.html) + +## Test Cases + +### Passed + +#### Passed Example 1 + +The presence of errors is conveyed through text error message. + +```html + + +

This field is empty. Enter your first name.

+``` + +#### Passed Example 2 + +The presence of errors is conveyed also through other CSS properties: +- font-weight: bold AND; +- border-width: 3px. + +```html + + + + + + +``` + +#### Passed Example 3 + +The presence of errors is conveyed through: +- lightness (difference in relative luminance between the colors leads to a contrast ratio greater than 3:1) AND; +- font-weight: bold. + +```html + + + + +``` + +### Failed + +#### Failed Example 1 + +The presence of errors is conveyed through color (hue) differences only. + +```html + + + + +``` + +### Inapplicable + +#### Inapplicable Example 1 + +There are no error fields. + +```html +

This is a paragraph.

+``` From ef1532d76cc37fd88be70e41296feaa51c4eb562 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Mon, 5 Sep 2022 10:11:33 +0200 Subject: [PATCH 11/15] Delete error-field-is-not-ifentified-using-color-differences-only --- ...ot-ifentified-using-color-differences-only | 108 ------------------ 1 file changed, 108 deletions(-) delete mode 100644 _rules/error-field-is-not-ifentified-using-color-differences-only diff --git a/_rules/error-field-is-not-ifentified-using-color-differences-only b/_rules/error-field-is-not-ifentified-using-color-differences-only deleted file mode 100644 index 48e9955ae23..00000000000 --- a/_rules/error-field-is-not-ifentified-using-color-differences-only +++ /dev/null @@ -1,108 +0,0 @@ ---- -id: -name: Error field is not identified using color differences only -rule_type: atomic -description: | - This rule checks that error fields can be identified not only by color differences but through another visual means. -accessibility_requirements: # Remove whatever is not applicable - wcag21:1.4.1: # Use of Color (A) - forConformance: true - failed: not satisfied - passed: further testing needed - inapplicable: further testing needed -input_aspects: - - DOM Tree - - CSS Styling -acknowledgments: - authors: - - Giacomo Petri ---- - -## Applicability - -This rule applies to any error field that is [visible][]. - -## Expectation (1) - -Each test target, together with its visual context, identify the presence of errors not only through color differences. - -## Assumptions - -https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html -If the presence of errors is conveyed through the use of colors that differ not only in their hue, but that also have a difference in lightness and the difference in relative luminance between the colors leads to a contrast ratio of 3:1 or greater, then this counts as an additional visual mean. - -*Note*: It is possible for an error field to be distinguishable from adjacent fields but still not have a meaningful error message. In that case, it would pass Success Criterion 1.4.1: Use of Color but still fail [Success Criterion 3.3.1: Error Identification](https://www.w3.org/WAI/WCAG21/Understanding/error-identification.html) and, if applicable, [Scuccess Criterion 3.3.3: Error Suggestion](https://www.w3.org/WAI/WCAG21/Understanding/error-suggestion.html). - -## Accessibility Support - -_No accessibility support issues known._ - -## Background - -- [Understanding Success Criterion 1.4.1: Use of Color](https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html) -- [F81 - Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only](https://www.w3.org/WAI/WCAG21/Techniques/failures/F81.html) - -## Test Cases - -### Passed - -#### Passed Example 1 - -The presence of errors is conveyed through text error message. - -```html - - -

This field is empty. Enter your first name.

-``` - -#### Passed Example 2 - -The presence of errors is conveyed also through other CSS properties: -- font-weight: bold AND; -- border-width: 3px. - -```html - - - - - - -``` - -#### Passed Example 3 - -The presence of errors is conveyed through: -- lightness (difference in relative luminance between the colors leads to a contrast ratio greater than 3:1) AND; -- font-weight: bold. - -```html - - - - -``` - -### Failed - -#### Failed Example 1 - -The presence of errors is conveyed through color (hue) differences only. - -```html - - - - -``` - -### Inapplicable - -#### Inapplicable Example 1 - -There are no error fields. - -```html -

This is a paragraph.

-``` From 4b6a266f487a797858d1710313ba9c7c51a0dbe1 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Mon, 26 Sep 2022 12:21:51 +0200 Subject: [PATCH 12/15] Update _rules/image-button-non-empty-accessible-name-59796f.md Co-authored-by: Jean-Yves Moyen --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 9d948301b29..4364d606b15 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -60,7 +60,7 @@ The [input type="image" Accessible Name Computation algorithm](https://www.w3.or ## Background -Contrarily to images, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation default to other means of providing a name. +Contrarily to images, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation defaults to other means of providing a name. ### Related rules From 71690d625da78cbff4aa8685fa9b05c538d74f72 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Mon, 3 Oct 2022 10:44:50 +0200 Subject: [PATCH 13/15] Update image-button-non-empty-accessible-name-59796f.md --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 4364d606b15..6c81c3a00b9 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -60,7 +60,7 @@ The [input type="image" Accessible Name Computation algorithm](https://www.w3.or ## Background -Contrarily to images, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation defaults to other means of providing a name. +Contrarily to `img` elements, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation defaults to other means of providing a name. ### Related rules From 92639543b456f25bb421b1f2c5b30993fb2415ba Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Mon, 3 Oct 2022 10:47:16 +0200 Subject: [PATCH 14/15] Update image-button-non-empty-accessible-name-59796f.md --- _rules/image-button-non-empty-accessible-name-59796f.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index 6c81c3a00b9..fd01ae586d0 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -60,7 +60,7 @@ The [input type="image" Accessible Name Computation algorithm](https://www.w3.or ## Background -Contrarily to `img` elements, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation defaults to other means of providing a name. +Contrarily to `img` elements, an empty `alt` attribute does not make image button decorative; image buttons have a button role and are therefore exposed as interactive elements. Consequently, an empty `alt` attribute does not provide a "usable string" for image buttons and the computation defaults to other means of providing a name, as defined in [input type="image" Accessible Name Computation algorithm](https://www.w3.org/TR/html-aam/#input-type-image-accessible-name-computation). ### Related rules From 9a844feb8500cdbd58a90556807c2f319d0f30d9 Mon Sep 17 00:00:00 2001 From: giacomo-petri <106394951+giacomo-petri@users.noreply.github.com> Date: Thu, 13 Oct 2022 17:15:27 +0200 Subject: [PATCH 15/15] Update _rules/image-button-non-empty-accessible-name-59796f.md Co-authored-by: Wilco Fiers --- _rules/image-button-non-empty-accessible-name-59796f.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/_rules/image-button-non-empty-accessible-name-59796f.md b/_rules/image-button-non-empty-accessible-name-59796f.md index fd01ae586d0..dece72e5914 100755 --- a/_rules/image-button-non-empty-accessible-name-59796f.md +++ b/_rules/image-button-non-empty-accessible-name-59796f.md @@ -112,14 +112,6 @@ The image button has an [accessible name][] through the `aria-labelledby` attrib
Search
``` -#### Passed Example 5 - -This image button has an empty `alt` attribute, but a non-empty `title` attribute. This gives the button an non-empty [accessible name][] through the `title` attribute. - -```html - -``` - ### Failed #### Failed Example 1