Accessibility mapping of <a> element - #2844
Conversation
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
spectranaut
left a comment
There was a problem hiding this comment.
I'm a little worried that this is so similar t
| </tr> | ||
| <tr> | ||
| <th>[[wai-aria-1.1]]</th> | ||
| <td>No corresponding role</td> |
There was a problem hiding this comment.
I'm a little worried that this is so similar to the core-aam definition of an a element -- other than the AXSubrole.
For example: The "tag" object attribute is actually always exposed, for all elements, that should be made more clear in the Core-AAM, and the linux mappings in the Core-AAM mention HyperlinkImpl, which is not mentioned here.
I think it might be better to say that there is a corresponding role, and that you should follow it, but that there is an AXSubrole override. So basically, for ATK write "Use the WAI-ARIA mappings" like here https://w3c.github.io/html-aam/#el-a, but for AX AXPI write "Use the WAI-ARIA mappings, but override subrole with..."
spectranaut
left a comment
There was a problem hiding this comment.
This is looking good, one small change request.
Co-authored-by: Valerie Young <spectranaut@igalia.com>
spectranaut
left a comment
There was a problem hiding this comment.
Looks good to me, thanks @tannal !
|
I've marked this as "waiting for implementations" because we require two implementations to merge. |
Closes w3c/mathml-aam#39
This change map mathml a element to link role in atspi and axapi.
Leave TBD for MSAA and UIA api.
See the mathml-aam issue in detail.
Test, Documentation and Implementation tracking
Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.
I got 503 when accessing webkit bug tracker, so for now I can't file the issue. :-)