Add/update implicit ARIA roles and allowed ARIA #168
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #149.
Adds/updates implicit ARIA roles and allowed ARIA.
Notably:
mapelement is now implicitlyrole="map";featureelement is now implicitlyrole="feature"The ARIA of each element is subject to change of course, I suggest opening new issues to discuss the accessibility considerations of each element when/if needed.
Preview (in comparison to WHATWG HTML's accessibility considerations)
HTML spec:
MapML spec:
The HTML spec links (for the
htmlelement in this case) to https://w3c.github.io/html-aria/#el-html:The MapML spec can't (at least not consistently) link to ARIA in HTML because it defines new elements (e.g. the
mapmlelement), we can include the ARIA in a details element instead:The HTML spec links (for the
htmlelement in this case) to thehtmlelement in the HTML Accessibility API Mappings: https://w3c.github.io/html-aam/#el-html (the site's CSS is currently broken so you'll have to collapse the sidebar to view the entire table).The MapML spec doesn't yet have any Accessibility API Mappings, perhaps the most appropriate thing to do is link to the GH issue: