Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARIA in HTML update for role allowances for button/input button elements #1304

Closed
scottaohara opened this issue Feb 15, 2023 · 2 comments
Closed
Labels
engine Issues in the accessibility-checker-engine component priority-3 (low) Ready for QA Standards user-reported Issues identified outside of the core team

Comments

@scottaohara
Copy link

ARIA in HTML (w3c/html-aria#446) is updating the role allowances for the button element, as well as input type=button, image, reset, submit. ARIA in HTML spec update preview.

This update serves two purposes:

  1. to add new role allowances to these elements - specifically treeitem, gridcell and slider. Each of these roles - if implemented correctly - can work just fine with the button element. Other potential accessibility gaps due to author implementation may be found via other existing automated or manual checks.
  2. The various input buttons were in misalignment with each other, as well as the button element. These input types now all have the same allowances as the button element. input type=reset, submit and image have been revised to allow all the same roles, but note that authors are NOT RECOMMENDED to use them. The reason for this is that the LOE of making a proper implementation of these roles, compared to using a button element or other element (like a div), is likely far greater than using these input types due to the limitations of their styling and content models, in comparison.

The full list of allowed roles for these elements now would be:
checkbox, combobox, gridcell, link, menuitem, menuitemcheckbox, menuitemradio, option, radio, slider, switch, tab, or treeitem. (button is also allowed, but NOT RECOMMENDED.)

The expectation here would be that all the allowed roles would no longer be exposed as errors or warnings.
For the input types (image, reset, submit) where roles are allowed but NOT RECOMMENDED, a warning message indicating that a more malleable HTML element, such as a <button> or <div> may be more appropriate to ease the development of the custom feature.

Test cases - button and input type=button tests and
input type=reset, image, submit tests

@aliunwala
Copy link
Contributor

Triage:
We will backlog this for implementation and discussion.

@ErickRenteria
Copy link
Contributor

Validated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine Issues in the accessibility-checker-engine component priority-3 (low) Ready for QA Standards user-reported Issues identified outside of the core team
Projects
None yet
Development

No branches or pull requests

5 participants