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

[Role Parity] need role for iframe #879

Open
jnurthen opened this issue Jan 9, 2019 · 7 comments
Open

[Role Parity] need role for iframe #879

jnurthen opened this issue Jan 9, 2019 · 7 comments

Comments

@jnurthen
Copy link
Member

jnurthen commented Jan 9, 2019

per plans for role parity need a role for equivalent to <iframe> in HTML

@jnurthen jnurthen added this to the ARIA 1.2 milestone Jan 9, 2019
@pkra pkra self-assigned this Apr 11, 2019
@pkra pkra removed their assignment Aug 29, 2019
@jnurthen jnurthen modified the milestones: ARIA 1.2, ARIA 1.3 Sep 28, 2019
@jnurthen
Copy link
Member Author

This is too late for 1.2 - moving to 1.3

@pkra
Copy link
Member

pkra commented Sep 30, 2019

Sorry for dropping the ball on this! I accidentally unassigned myself when doing some batch unassigning.

@joanmarie joanmarie changed the title need role for iframe [Role Parity] need role for iframe Nov 21, 2019
@pkra pkra self-assigned this Nov 21, 2019
@pkra
Copy link
Member

pkra commented Feb 13, 2020

@scottaohara recently commented on embed

In drafting up a potential definition for this role, and re-reviewing what object and embed are meant to represent, I'm wondering if this might be similar to generic in that this role is more meant for implementors rather than authors.

Being that these elements largely embed content that could be considered graphics or other media (videos/audio), nested browsing contexts (application or document roles) or plugins like flash, i'm unsure why we'd want authors to use this role when it'd be more straight forward to use other roles that better represent the embedded content.

This resonated with my thoughts on iframe. It also does not feel like a role for authors.

@pkra
Copy link
Member

pkra commented Nov 8, 2021

w3c/html-aria#368 seems relevant; James Teh's comments show how particular iframe implementations are. It seems questionable to me that ARIA could reach parity here.

@scottaohara
Copy link
Member

@pkra, suggest we punt this to 1.4 since the embed/object one is slated for 1.4 as well

@pkra
Copy link
Member

pkra commented Jan 21, 2022

@pkra, suggest we punt this to 1.4 since the embed/object one is slated for 1.4 as well

This is already in the 1.4 milestone. (All remaining role parity issues now are, so I renamed that project board.)

@pkra pkra removed their assignment Jun 30, 2022
@brennanyoung
Copy link
Contributor

I definitely think iframes should have a generic role. If authors need something else they can add a non-generic role like "section" or "complimentary", in which case a name would be required. Generic iframes should not require names or lang attributes.

iframes that do require names (i.e. those marked-up with a non-generic semantic role) might usefully inherit their accessible name (and language) from the title (and lang attribute) of the HTML content inside (if one exists) in a similar way to how the first heading inside a semantic element is taken to be the accessible name of that element.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants