Split ARIA props not prohibited from ARIA props permitted#2342
Split ARIA props not prohibited from ARIA props permitted#2342WilcoFiers merged 14 commits intodevelopfrom
Conversation
✅ Deploy Preview for act-rules ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| The `aria-brailleroledescription` property is [prohibited][] for an element with a `none` role. | ||
|
|
||
| ```html | ||
| <h1 role="none" aria-brailleroledescription="Banana text">I like bananas</h1> | ||
| ``` |
There was a problem hiding this comment.
do you think this could be replaced by role="presentation"? it would be clearer because I had to search that role="none" is just a synonym to that
There was a problem hiding this comment.
Discussed on the call. "none" tends to be the preferred name for this these days.
carlosapaduarte
left a comment
There was a problem hiding this comment.
Some editorial changes
| ## Background | ||
|
|
||
| The presence of prohibited ARIA attributes is often the result of a developer using an incorrect role, or a misunderstanding of the attribute. These attributes are ignored by browsers and other assistive technologies. This often means that a state or property which should exist is missing. | ||
| The use of ARIA attributes that are not supported by a role is often the result of a developer either an incorrect role, or misunderstanding the attribute. These attributes are ignored by browsers and other assistive technologies. This often means that information that should exist is missing to assistive technology users. |
There was a problem hiding this comment.
| The use of ARIA attributes that are not supported by a role is often the result of a developer either an incorrect role, or misunderstanding the attribute. These attributes are ignored by browsers and other assistive technologies. This often means that information that should exist is missing to assistive technology users. | |
| The use of ARIA attributes that are not supported by a role is often the result of a developer either using an incorrect role, or misunderstanding the attribute. These attributes are ignored by browsers and other assistive technologies. This often means that information that should exist is missing to assistive technology users. |
|
|
||
| ## Expectation | ||
|
|
||
| No test target is [prohibited][] on the [semantic role][] of the element on which it is specified. |
There was a problem hiding this comment.
| No test target is [prohibited][] on the [semantic role][] of the element on which it is specified. | |
| The test target is not [prohibited][] on the [semantic role][] of the element on which it is specified. |
| - JFK's "We Choose the Moon" speech excerpt is courtesy of NASA. | ||
| --- | ||
|
|
||
| ## Applicability |
There was a problem hiding this comment.
Maybe a nitpick: I would feel better if the word "attribute" was mentioned here (in the applicability). This would match other rules such as https://www.w3.org/WAI/standards-guidelines/act/rules/5f99a7/ , https://www.w3.org/WAI/standards-guidelines/act/rules/6a7281/ , https://www.w3.org/WAI/standards-guidelines/act/rules/674b10/ .
There was a problem hiding this comment.
This comment also applies to the other rule.
Co-authored-by: Carlos Duarte <caduarte@edu.ulisboa.pt>
Co-authored-by: Carlos Duarte <caduarte@edu.ulisboa.pt>
Co-authored-by: Aleksandra <50310535+zlayaAvocado@users.noreply.github.com>
Co-authored-by: Carlos Duarte <caduarte@edu.ulisboa.pt>
Co-authored-by: Carlos Duarte <caduarte@edu.ulisboa.pt>
Accepted
|
@WilcoFiers This seems to solve/supercede both #2036 and #2037. Can you confirm and close them upon merging this? |
Co-authored-by: Jean-Yves Moyen <jym@siteimprove.com>
Work in progress...
Closes issue(s):
Need for Call for Review: 2 weeks
Pull Request Etiquette
When creating PR:
developbranch (left side).After creating PR:
Rule,DefinitionorChore.When merging a PR:
How to Review And Approve