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

An element containing only   in Outlook web, breaks VoiceOver navigation #142

Open
M-J-Robbins opened this issue Nov 21, 2024 · 2 comments

Comments

@M-J-Robbins
Copy link
Contributor

M-J-Robbins commented Nov 21, 2024

Email Client

Outlook webmail

Operating System

MacOS 15
Safari 18

Expected Result

When using role="application" in the browser it is expected that using role="document" inside that will mean the content is treated as web content.

If the web application encompassed by the application role contains parts that should be treated like normal web content, a role of document or article should be used to contain such content.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/application_role

Actual Result

When looking at the below code sample with an element that contains only  , inside a region, inside a document, inside an application. Then it breaks VoiceOver navigation and will exit the region.

Code sample

If testing with Outlook this code will show the issue

    <div aria-label="Testing region in application" role="region" >
      <h1>This text is read out</h1>
      <p>&nbsp;</p>
      <p>This text is ignored</p>
    </div>          

If testing directly in Safari then this code will show the issues. Here I've added role="application" and role="document" that get added by Outlook.

<div role="application">
  <div role="document">
    <div aria-label="Testing region in application" role="region" >
      <h1>This text is read out</h1>
      <p>&nbsp;</p>
      <p>This text is ignored</p>
    </div>          
  </div>
</div>

Additional context

I've reported the bug in Safari here https://bugs.webkit.org/show_bug.cgi?id=283499

@husseinalhammad
Copy link

Do you know if other whitespace characters like &zwj; cause the same issue?

@M-J-Robbins
Copy link
Contributor Author

I tested &zwj; and that was fine. But I haven't tested beyond that yet.

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