aria
aria copied to clipboard
w3c
Accessible Rich Internet Applications (WAI-ARIA)
# Describe the change As per [comments](https://github.com/w3c/aria-practices/issues/3211#issuecomment-2585618581) in https://github.com/w3c/aria-practices/issues/3211, currently only roles where an accessible name is required have an Accessible Name Required row, with a value pair set to...
Should the ARIA WG standardize heuristic-based ignoring of ARIA and related features? And if so, how? One pre-existing example is how [engines now ignore `aria-hidden` in certain scenarios](https://w3c.github.io/aria/#aria-hidden) where it's...
Updates the existing note and adds new ua and author requirements for instances of aria-labelledby and aria-labeledby Closes #2093 i did not put this content into the accounting for author...
Closes #1960 Adds `aria-checked` as a supported state to `gridcell`, with the same wording around combining `aria-checked` & `aria-selected` as on `option` and `treeitem`. The `aria-checked` support also inherits into...
closes #2382 and is related to #2344 / #2369 This PR adds aria-valuetext as a supported property for the combobox role. the `aria-valuetext` definition is slightly updated to indicate that...
Closes #2012 This PR adds additional user agent guidance for how orphan roles SHOULD be treated outside of the context of a required accessibility parent role. *** Preview | Diff
Semi-related to #1862 We have logic in `aria.js` to apply ARIA 1.2-specific deprecation warnings, but no other built-in deprecation language or system, particularly for deprecating support for an attribute on...
As discussed in the WG meeting today, dpub-aria has `aria-valuenow (required)` which is a problematic partial inheritance from its aria superlass `separator` which has `aria-valuenow (if focusable)`. I'm guessing something...
There was a previous effort to allow certain roles to receive their accessible name from encapsulation. That work was put to the side, and a more targeted version was spun...
The WG did not want to go in the direction of #2407. Instead the editors will look for other approaches to present deprecation, possibly following the HTML spec's example.