Add an "Accessibility Tree" section describing inclusion and exclusion rules #792
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n rules This content was taken from the Core-AAM because it is information which is platform independent and has nothing to do with accessibility API mappings.
This was referenced Jul 25, 2018
|
Feedback from meeting:
|
|
I'm in favor of merging! I agree with Matt. |
|
+1 to merging! |
joanmarie
added a commit
to w3c/core-aam
that referenced
this pull request
Aug 15, 2018
The rules regarding tree inclusion and exclusion are platform independent and have nothing to do with accessibility API mappings. Furthermore, we wouldn't want those rules, which are important, missed because they are not in the ARIA spec. Now that w3c/aria#792 has been merged, remove the redundant content from Core AAM. Fixes github issue #17.
carmacleod
reviewed
Aug 16, 2018
| <p>The following <a>elements</a> are not exposed via the <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> and user agents MUST NOT include them in the <a class="termref">accessibility tree</a>:</p> | ||
| <ul> | ||
| <li>Elements with <rref>none</rref> or <rref>presentation</rref> as the first role in the role attribute. However, their exclusion is conditional and depends on other factors. In addition, the element's descendants and text content are generally included. These exceptions and conditions are documented in the <a href="#conflict_resolution_presentation_none">Presentational Roles Conflict Resolution</a> section.</li> | ||
| <li>Elements, including their descendent elements, that have host language semantics specifying that the element is not displayed, such as CSS <code>display:none</code>, <code>visibility:hidden</code>, or the HTML 5 <code>hidden</code> attribute.</li> |
There was a problem hiding this comment.
Do we want to also explicitly mention tags, like <script>, that are hidden in the browsers' default style sheet? i.e.:
[hidden], area, base, basefont, datalist, head, link, meta, noembed, noframes, param, rp, script, source, style, template, track, title, input[type=hidden], and noscript if there's script.
joanmarie
added a commit
that referenced
this pull request
Oct 24, 2018
…n rules (#792) This content was taken from the Core-AAM because it is information which is platform independent and has nothing to do with accessibility API mappings.
joanmarie
added a commit
to w3c/core-aam
that referenced
this pull request
Nov 8, 2018
The rules regarding tree inclusion and exclusion are platform independent and have nothing to do with accessibility API mappings. Furthermore, we wouldn't want those rules, which are important, missed because they are not in the ARIA spec. Now that w3c/aria#792 has been merged, remove the redundant content from Core AAM. Fixes github issue #17.
pkra
pushed a commit
that referenced
this pull request
May 20, 2024
The rules regarding tree inclusion and exclusion are platform independent and have nothing to do with accessibility API mappings. Furthermore, we wouldn't want those rules, which are important, missed because they are not in the ARIA spec. Now that #792 has been merged, remove the redundant content from Core AAM. Fixes github issue #17.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This content was taken from the Core-AAM because it is information which
is platform independent and has nothing to do with accessibility API
mappings.
Preview | Diff