ARIA: remove aria-expanded from supported attributes from role listbox
Categories
(Core :: Disability Access APIs, enhancement, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: spectranaut, Assigned: b3nbinoh)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(2 files, 2 obsolete files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0
Expected results:
ARIA is removing aria-expanded from listbox role's supported attribute list: https://github.com/w3c/aria/pull/1862
Rule 5 in CORE-AAM's State and Property Mapping General Rules (https://w3c.github.io/core-aam/#statePropertyMappingGeneralRules) says:
Some WAI-ARIA properties are not global, and are only supported on certain roles. If a non-global WAI-ARIA state or property is used where it is not supported, user agents SHOULD NOT map the given WAI-ARIA property to the platform accessibility API. For example, if
aria-checked="true"is specified on<div role="grid">, it should not be exposed in MSAA implementations as STATE_SYSTEM_CHECKED.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•2 years ago
|
Comment 2•1 year ago
|
||
Valerie mentioned these are likely good first bugs, so I'm marking them as such. Please feel free to correct if that's not accurate.
Updated•8 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Hey sorry I tried to change my WIP Phab page to a non-WIP one but it looks like it just created a new Phab page.
Updated•4 months ago
|
Comment 8•3 months ago
|
||
Updated•3 months ago
|
Comment 10•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Comment 11•1 month ago
|
||
Comment 12•1 month ago
|
||
| bugherder | ||
Description
•