core-aam
core-aam copied to clipboard
w3c
Core Accessibility API Mappings
The [current mapping](https://www.w3.org/TR/core-aam-1.2/#ariaLabelledBy) states that browsers should expose `aria-labelledby` through `AXTitle` if the value is rendered visually. However, if I'm reading [WebKit's AXDescription code](https://github.com/WebKit/WebKit/blob/main/Source/WebCore/accessibility/AccessibilityNodeObject.cpp#L2105) right, it will always expose `aria-labelledby`...
In the current [core-aam 1.2 mappings for aria-labelledby](https://www.w3.org/TR/core-aam-1.2/#ariaLabelledBy), AX API maps it as such: > - Property: AXDescription: if the value is not exposed visually > - Property: AXTitle: if...
related to https://github.com/w3c/aria/pull/1931 PRs/tests can be hancled in the original HTML AAM issue (or here... whatever, this can be edited) *** Preview | Diff
Based on screen reader feedback, the `alert` role no longer fires a system alert event, but a live region changed event (still on insertion). Related Chromium PR with the change:...
Part of the work on https://github.com/w3c/aria/issues/1440 This adds mappings for `aria-actions` that piggyback off `aria-details`. This should (in theory) allow actions to build off the work already done for `aria-details`...
`directory` role is deprecated in [ARIA](https://w3c.github.io/aria/#directory), but it is not currently listed as deprecated in [core-aam.](https://www.w3.org/TR/core-aam-1.2/#role-map-directory) Related issue in ARIA: https://github.com/w3c/aria/issues/2161
(cross-posted from https://github.com/w3c/aria/issues/2153 as I believe the issue will need considerations in both specs) # Describe your concern Currently, in the description for `role="alert"` https://www.w3.org/TR/wai-aria-1.3/#alert the ARIA spec states >...
The CSS custom highlight feature, introduced through the ::highlight() pseudo-element, provides a mechanism for styling text ranges on a webpage without impacting the DOM, and it's growing in usage in...
I was asked whether it was spec'd anywhere what should happen for if an accessible name changes. I pointed to this spec since the name change (and description change) events...