core-aam
core-aam copied to clipboard
w3c
Core Accessibility API Mappings
WebKit mappings are not correct for style-based roles: strong, emphasis, maybe more… There are number of AXSubroles listed that don't match the implementation: AXStrongStyleGroup, AXEmphasisStyleGroup, etc. Looks like @joanmarie made...
This short review is for the following spec: [Core Accessibility API Mappings 1.2](https://w3c.github.io/core-aam/). 1. [x] _If the spec (or its implementation) contains any natural language text that will be read...
I really care a TON about this spec in general, and about the ATK/AT-SPI2 mappings in particular (because I am the Orca screen reader maintainer :smile:). While I do have...
In the references section of core-aam, the links to the Linux foundation documentation for IAccessible2 and AT-SPI are broken. These links are 404 [AT-SPI] [Assistive Technology Service Provider Interface](https://developer.gnome.org/libatspi/stable/). The...
If many HTML elements map to generic in the future, which are not grouping elements, then the mapping of generic should be adjusted. See: https://github.com/w3c/html-aria/issues/406
From https://github.com/w3c/aria/issues/1009 > What is more concerning is there is no mapping for aria-details for AX API, which means using this property will be useless to users of macOS. That's...
According to https://bugs.webkit.org/show_bug.cgi?id=206253#c18 AXCustomContent should be used if MacOS version >= 11 Otherwise, use AXHelp (as it says now).
When working on https://github.com/w3c/core-aam/pull/97, I noticed that the MSAA + IAccessible2 mapping for role="form" with an accessible name is IA2_ROLE_FORM. I would have thought it should be mapped to IA2_ROLE_LANDMARK...
IA2 provides specific roles for banner and contentinfo role, i.e. IA2_ROLE_HEADER and IA2_ROLE_FOOTER correspondingly, which should be used instead more generic IA2_ROLE_LANDMARK. See issue https://github.com/w3c/html-aam/issues/133 for details.
