core-aam
core-aam copied to clipboard
w3c
Core Accessibility API Mappings
Having read the [ARIA spec for `aria-setsize`](https://w3c.github.io/aria/#aria-setsize), as well as the [CORE AAM mappings for `aria-setsize`](https://w3c.github.io/core-aam/#ariaSetsize) and the referenced [Group Position section](https://w3c.github.io/core-aam/#mapping_additional_position), there seems to be something off in how...
Currently, the [Group Position section](https://w3c.github.io/core-aam/#mapping_additional_position) says that to compute `aria-posinset` and `aria-setsize`, user agents should: > ...process the parent (DOM parent or parent defined by [aria-owns](https://www.w3.org/TR/wai-aria-1.1/#aria-owns)), counting items that have...
The switch role is mapped to toggle button in IA2 and ATK. This has apparently led to some problems. See https://github.com/nvaccess/nvda/issues/9187#issuecomment-457001861. Do we want to change the mappings?
According to [UIA's control type documentation](https://docs.microsoft.com/en-us/dotnet/api/system.windows.automation.controltype?view=windowsdesktop-6.0), the "Text" control type "Identifies an edit control, such as a text box or rich text box". Based on this definition, it seems like...
For both ATK and IA2, we should add `Object Attribute: details-roles` with the list of optional values. This is implemented in chromium, as you can see from tests: https://source.chromium.org/search?q=details-roles
In the spec, the MSAA mapping is: * [Role: ROLE_SYSTEM_GROUPING](https://w3c.github.io/core-aam/#role-map-subscript) In the WPT core-aam test, the MSAA mapping is: * [Role: ROLE_SYSTEM_TEXT](https://w3c.github.io/core-aam/#role-map-subscript)
The following table reflects the event mapping currently in the Core AAM for UIA. I noticed some inconsistencies in how things are written and would like a review of the...
The precedence order is: aria-describedby aria-description
Add mark, comment, suggestion. For comment, support comment level, setsize, posinset.
_From @matatk on January 24, 2017 19:7_ This is a spin-off from #513 which resolves that `region` landmarks should only be considered as such if they are named (via `aria-labelledby`...
