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

accname-aam clarify hidden #30

Open
jnurthen opened this issue May 30, 2018 · 3 comments
Open

accname-aam clarify hidden #30

jnurthen opened this issue May 30, 2018 · 3 comments
Milestone

Comments

@jnurthen
Copy link
Member

From @jnurthen on November 6, 2017 23:38

Step 2A states

If the current node is hidden

Where hidden is defined as

Indicates that the element is not visible, perceivable, or interactive to any user. An element is considered hidden if it or any one of its ancestor elements is not rendered or is explicitly hidden.

Please clarify if a node is hidden using aria-hidden whether it should be included in the accessible name calculation.

Copied from original issue: w3c/aria#658

@kasperisager
Copy link
Contributor

On that account, would visibility: hidden or visibility: collapse also count as explicitly hidden?

@accdc
Copy link
Contributor

accdc commented Jun 25, 2018

"On that account, would visibility: hidden or visibility: collapse also count as explicitly hidden?"

Yes, though I don't think we need to document all ways this is done within native host semantics since the browser handles this automatically. The aria-hidden attribute is different because it explicitly hides something in the accessibility tree without involving the native host semantic such as what is visibly rendered.

@Jym77
Copy link

Jym77 commented Nov 10, 2022

It looks like this has been solved by #150 which added a comment to Step 2A to clarify what "hidden" means.

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

5 participants