You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Per the peculiar nature of aria-checked, where it allows for three different states on checkboxes (false, true, mixed), but native HTML only allows for true/false, and then has a separate IDL attribute to handle 'mixed', per ARIA's normative rules about host language attributes having higher importance, authors really must not use the aria-checked attribute on native HTML elements that allow it. Particularlyinput type=checkbox which, if following the requirements of ARIA, as the checked/unchecked MUST always win out, and thus aria-checked MUST always be ignored, even if set to aria-checked=mixed.
These rule update are part of what will resolve the ARIA issue I opened - w3c/aria#1622
Need at least two checkers to accept this change before we can merge.
This change will make it extremely difficult for implementors to implement checkboxes that are styled AND are accessible. Currently most component libraries that implement accessible styled checkboxes use a real checkbox elements for the focus but overlay a visibly styled element of some sort.
I think that this is a change that takes the web platform in the wrong direction.
Currently most component libraries that implement accessible styled checkboxes use a real checkbox elements for the focus but overlay a visibly styled element of some sort.
That is true
This change will make it extremely difficult for implementors to implement checkboxes that are styled AND are accessible
This is not true as the frameworks do not require ARIA. There is the invisible HTML checkbox (without ARIA) and the visible checkbox (which is marked with aria-hidden=true at most, depending on the implementation)
This update is being made to better reflect reality, and to inform authors that what they are doing now is not consistently accessible. Using aria-checked on native checkboxes and radio buttons is not respected in Firefox and Safari, which includes the aria-checked=mixed state. These browsers are correctly following the ARIA spec, as it has been written since version 1.0. Native attributes win out over aria-* equivalents.
Authors using aria-checked=mixed on a native checkbox are presently only exposing this in Chromium browsers, due to their incorrect implementation of ARIA.
Authors should be using the indeterminate IDL attribute to set their checkboxes to the mixed state - which per standard visually hidden checkbox techniques, would work similarly to what authors are doing with their [aria-checked=mixed] + span selectors now.
Further discussion on whether aria-checked needs to be a special case (because it actually is compared to other aria-* attributes, since it combines the checkboxes native checked and indeterminate attributes into one aria-* attribute) can occur in w3c/aria#1622.
directly reference the following PRs in the changelog, and prepend each entry with the appropriate 'label'
related to #419
- #352
- #367 (and follow on [commit](887c772))
- #360
- #353
- #372
- #402
- #404
- #403
- #396
- #391
- #369
- #381
Meets 2 implementations reqIndicates that a spec change has met the necessary 2 implementations needed to merge.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #361
Per the peculiar nature of
aria-checked
, where it allows for three different states on checkboxes (false, true, mixed), but native HTML only allows for true/false, and then has a separate IDL attribute to handle 'mixed', per ARIA's normative rules about host language attributes having higher importance, authors really must not use thearia-checked
attribute on native HTML elements that allow it. Particularlyinput type=checkbox
which, if following the requirements of ARIA, as the checked/unchecked MUST always win out, and thusaria-checked
MUST always be ignored, even if set toaria-checked=mixed
.These rule update are part of what will resolve the ARIA issue I opened - w3c/aria#1622
Need at least two checkers to accept this change before we can merge.
Preview | Diff
Preview | Diff