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.

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

Jump to bottom

Consider further calling out aria-hidden expectations for focusable elements #1765

Open
scottaohara opened this issue Jul 12, 2022 · 0 comments · May be fixed by #2181
Open

Consider further calling out aria-hidden expectations for focusable elements #1765

scottaohara opened this issue Jul 12, 2022 · 0 comments · May be fixed by #2181
Assignees
@aleventhal @scottaohara
Labels
clarification clarifying or correcting language that is either confusing, misleading or under-specified
Milestone
2024

Comments

@scottaohara
Copy link
Member

the definition of aria-hidden does not make it clear that content - e.g., focusable elements - can/should/are still exposed to AT when focused.

https://www.w3.org/TR/wai-aria-1.2/#tree_inclusion DOES call out that elements can be exposed even if they are set to aria-hidden=true / focused

That's really it though, in regards to informing authors that aria-hidden=true has been modified over time to purposefully mitigate against author error.

To that point, should there be additional text added to the aria-hidden definition to call out this reality? Should this be explicitly specified in the author error section?

It would sure help make the reality of the situation a lot easier to explain.
@spectranaut spectranaut added the clarification clarifying or correcting language that is either confusing, misleading or under-specified label Jul 14, 2022
@spectranaut spectranaut added this to the ARIA 1.4 milestone Jul 14, 2022
@jnurthen jnurthen assigned scottaohara and aleventhal and unassigned chlane Sep 12, 2023
scottaohara added a commit that referenced this issue May 20, 2024
@scottaohara
Expectations for aria-hidden and focused elements
de87611 
This PR closes #1765 and is related to work that was done in #2037, but scoped only to the original issue I filed.

The intent of this PR is to identify not only how user agents would need to handle focusable elements that are aria-hidden (explicitly or due to being a descendant of an aria-hidden container) - but for the case where a focusable element is within an aria-hidden container, that the entire subtree would need to be re-exposed so that any other relevant information to the user could be made available.  (e.g., so as to not just expose a "learn more" link, with no way to determine what someone would be learning about)

a simple example being like:

```
<div aria-hidden=true>
  <h3>Something or other</h3>
   some details about said something, or other.
  <a href=#>Learn more!</a>
</div>
```
@scottaohara scottaohara linked a pull request May 20, 2024 that will close this issue
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aleventhal aleventhal

@scottaohara scottaohara

Labels
clarification clarifying or correcting language that is either confusing, misleading or under-specified
Projects
None yet
Milestone
2024
Development

Successfully merging a pull request may close this issue.

Expectations for aria-hidden and focused elements w3c/aria
4 participants
@spectranaut @aleventhal @scottaohara @chlane