Skip to content

Updating HTML elements to map to their Aria 1.2 roles #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Nov 7, 2021
Merged

Updating HTML elements to map to their Aria 1.2 roles #348

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
3f31440
blockquote update
scottaohara Jul 20, 2021
847b466
fix mapping for body/html
scottaohara Jul 20, 2021
cc4bf04
update section 3.4 introduction list
scottaohara Jul 20, 2021
5937aa9
update aria 1.1 to 1.2 links
scottaohara Jul 20, 2021
292e629
update json data for specs
scottaohara Sep 29, 2021
02039ce
update hgroup mapping to match reality
scottaohara Sep 29, 2021
34c10e7
point to aria 1.2 roles
scottaohara Sep 29, 2021
cbda1a2
start marking generics
scottaohara Sep 29, 2021
409ef55
typo fixed
stevefaulkner Sep 29, 2021
48311b9
Update index.html
scottaohara Nov 2, 2021
fd74154
Merge branch 'gh-pages' into aria1-2roles
scottaohara Nov 7, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
update section 3.4 introduction list 
* remove bullet about “?” cells.  these have all been removed.
* update list item about `aria-roledescription` and mention that UAs must not expose the attribute if used on an implicit `generic` element.
  • Loading branch information
@scottaohara
scottaohara committed Sep 29, 2021
commit cc4bf04002d168bb357148c9957458e8a9b3d72d
3 changes: 1 addition & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,10 +222,9 @@ <h3>Exposing HTML Features That Do Not Directly Map to Accessibility APIs</h3>
<h3>HTML Element Role Mappings</h3>
<ul>
<li>HTML elements with implicit WAI-ARIA role semantics MUST be mapped to platform <a class="termref">accessibility APIs</a> according to those WAI-ARIA roles' mappings as defined in the [[core-aam-1.2]] specification.</li>
<li>A '?' in a cell indicates the data has yet to be provided.</li>
<li>"Not mapped" (Not Applicable) means the element does not need to be exposed via an <a class="termref">accessibility API</a>. This is usually because the element is not displayed as part of the user interface.</li>
<li>Where applicable, how an element participates in the computation of its own or another element's <a class="termref">accessible name</a> and/or <a class="termref">accessible description</a> is described in the <a href="#accessible-name-and-description-computation">Accessible Name and Description Computation</a> section of this document.</li>
<li>Where an element is indicated as having &quot;No corresponding (WAI-ARIA) role&quot;, user agents MUST NOT expose the <a class="core-mapping" href="#ariaRoleDescription">`aria-roledescription`</a> property value in the <a class="termref">accessibility tree</a> unless the element has an explicit, conforming `role` attribute value.</li>
<li>Where an element is indicated as having &quot;No corresponding (WAI-ARIA) role&quot;, or is mapped to the <a class="core-mapping" href="#role-map-generic">`generic`</a> role, user agents MUST NOT expose the <a class="core-mapping" href="#ariaRoleDescription">`aria-roledescription`</a> property value in the <a class="termref">accessibility tree</a> unless the element has an explicit, conforming `role` attribute value which [[WAI-ARIA-1.2]] does not prohibit the use of `aria-roledescription`.</li>
<li>
<strong>IAccessible2:</strong>
<ul>
Expand Down