Skip to content

Disallow "presentation' or 'none' role on an iframe element #552

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

Open
shunguoy opened this issue Apr 30, 2025 · 3 comments
Open

Disallow "presentation' or 'none' role on an iframe element #552

shunguoy opened this issue Apr 30, 2025 · 3 comments

Comments

@shunguoy
Copy link

With the recent update from Chrome, major browsers support automatic focus on an iframe element. The role "presentation" or "none" on an iframe element causes conflict: accessible through keyboard but not through a screen reader, and the resolution to the conflict might be user agent dependent.

@scottaohara
Copy link
Member

maybe i can reopen #370 where i was trying to work ahead of changes like this

@shunguoy
Copy link
Author

Here are some quick test results: with role='presentation' on an iframe element:
Chrome takes out the iframe content from the accessibility tree
Firefox uses its internal role "internal frame" instead of "presentation", and the iframe content is in the accessibility tree.
Safari: VoiceOver announces the frame's content. The only difference from another frame without a "presentation" role is that the announcement starts with "x items" rather than "in frame x".
The implementations are inconsistent with the ARIA Presentational Roles Conflict Resolution.
@scottaohara

@scottaohara
Copy link
Member

this looks similar to some of the issues i was finding when i tried updating this rule previously. using these roles on iframes can break them.

does your issue indicate that if ARIA in HTML were to update to point out these issues and indicate that authors should not be using these roles on iframes, that IBM would be supportive this time around?

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