Bug 181856
| Summary: | AX: Update SVG mappings to reflect changes in SVG AAM | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joanmarie Diggs <jdiggs> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Joanmarie Diggs
The SVG AAM used to contain direct platform mappings. Now, for many roles, SVG AAM says things like:
$GRAPHICS_ARIA_ROLE role mapping if the element meets the
criteria for Including Elements in the Accessibility Tree
The specific platform mappings of those Graphics ARIA roles is contained in the Graphics AAM. Support for Graphics ARIA roles and mappings is being done in bug 181796. I was thinking it would also be worth updating our SVG Accessibility support to follow what is now being done in the SVG AAM (e.g. for SVG shapes, return the WebCore AccessibilityRole corresponding to 'graphics-symbol' rather than directly returning AccessibilityRole::Image). And I was planning to include that in the patch I provide for bug 181796. But the SVG AAM has some inconsistencies in their mappings. So I filed an issue against the spec: https://github.com/w3c/svg-aam/issues/1. Once we know what their plans are we can update our implementation.
Also, it seems they changed the mapping of the `use` element. It used to be treated as an image; now it is mapped to the graphics-object role, and graphics-object is mapped as a group; not an image.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/36658876>