aria
aria copied to clipboard
w3c
Accessible Rich Internet Applications (WAI-ARIA)
This PR does a few things: 1. Adds text indicating that UAs should calculate the x of y position of options similar to radio buttons (this is what happens now,...
I recreated the [original HTML AAM repo PR](https://github.com/w3c/html-aam/pull/566) The `` element is part of the [customizable select feature](https://github.com/whatwg/html/issues/9799) and is being added to HTML [here](https://github.com/whatwg/html/pull/10633). ## Implementation * WPT tests:...
This issue follows on from [a previous discussion in #1277](https://github.com/w3c/aria/issues/1277#issuecomment-689478291). The [current working draft of ARIA 1.2](https://www.w3.org/TR/wai-aria-1.2/#aria-expanded) extends support for `aria-expanded` to the checkbox role, but not the radio role....
I was checking one of the Failed examples in the ACT Rules about "ARIA required context role" ([Failed example 3](https://w3.org/WAI/content-assets/wcag-act-rules/testcases/ff89c9/52508dc0ac389108301d7cbd7f931be45a45741f.html)). I'm unsure about the expected violation of the acc parent/descendant...
Initial draft of select / button as child of a select mappings. # Test, Documentation and Implementation tracking Once this PR has been reviewed and has consensus from the working...
This came up during the AGWG call when discussing the [svg element with explicit role has non-empty accessible name](https://act-rules.github.io/rules/7d6734) ACT rule. Why should an `img` only be named from author?...
Follow up to https://github.com/w3c/aria/pull/2410. Reviewing the spec css identified various other issues. Let's collect them here - [ ] [spec HTML] nested `.rfc2119` -- look like simple authoring errors -...
### Description: In the ARIA specifications, the [Presentational Roles Conflict Resolution](https://www.w3.org/TR/wai-aria-1.3/#conflict_resolution_presentation_none) section applies to elements with either an explicit or inherited presentational role: > User agents MUST NOT expose [elements](https://dom.spec.whatwg.org/#concept-element)...
Should we explicitly clarify that required accessible parent/children relationships do not apply to elements with `aria-busy="true"`? It seems understandable, but I don’t see a place where this is clearly stated....
In regards to the updated content model for the select element and its allowed children, an `optgroup` can have a `legend` element as its first child, and this `legend` needs...