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

Specify what should happen when unhiding an ancestor of a live region #175

Open
mitchellevan opened this issue May 15, 2023 · 2 comments
Open

Comments

@mitchellevan
Copy link

With each of the structures below, what should happen?

  1. Load a page with one of the structures below
  2. Unhide the parent container

Structure 1: unhiding visually

<div style="display:none;"> <-- e.g., inside a disclosure widget -->
  <div aria-live="polite">chat message: hello</div>
</div>

Structure 2: unhiding from assistive technology

<div aria-hidden="true"> <-- e.g., behind a dialog -->
  <div aria-live="polite">chat message: hello</div>
</div>

Browsers are currently inconsistent. aria-live example with test results

The consequence of the inconsistency is that aria-live is difficult to use on visible content, like a chat log, when combined with other common widgets in the same page such as a disclosure widget or a dialog.

If Core AAM is not the right place for this issue, please let me know.

@JAWS-test
Copy link

Related w3c/aria-practices#78, w3c/aria#1854

I have come to share the assumptions you made on your test page as a basis for evaluating screen reader output, even though I wrote otherwise years ago in the linked issues

@jnurthen
Copy link
Member

closing in favour of the aria issue w3c/aria#1937

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

4 participants