Skip to content
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.

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

Accessibility Tree details #13

Open
dginev opened this issue Oct 11, 2021 · 3 comments
Open

Accessibility Tree details #13

dginev opened this issue Oct 11, 2021 · 3 comments

Comments

@dginev
Copy link
Contributor

dginev commented Oct 11, 2021

I am unsure about a sentence in the document, so making an issue to inquire further:

In general, the accessibility tree is a simplified version of the DOM in that only information needed by AT is exposed. For example, a span with no semantic information will not be part of the accessibility tree.

I made a document containing two unmarked spans, and am seeing both Firefox and Chrome include them in the AT tree. See screenshot at the bottom.

I also enabled chrome's Screen Reader (which is the only app i have succeeded with using on linux) and it spoke both spans by default.

So what exactly does "not be part of" mean in the sentence?


image

@NSoiffer
Copy link
Contributor

The contents of the span are part of the tree, but not the span itself... or at least that is what the spec says should happen. From https://www.w3.org/TR/core-aam-1.1/#intro_treetypes, "Generally if something can be trimmed out it will be, for reasons of performance and simplicity. For example, a with just a style change and no semantics may not get its own accessible object, but the style change will be exposed by other means."

From your examples, that appears to be what is happening. For MathML, it means that would typically be stripped out, but not the presentation inside it.

@dginev
Copy link
Contributor Author

dginev commented Oct 11, 2021

Hmm, I see. So maybe a rephrasing of:

"For example, a span with no semantic information will not be preserved in the accessibility tree, only its textual content."

@NSoiffer
Copy link
Contributor

NSoiffer commented Oct 11, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants