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

Resolve "iframe element has accessible name" feedback #473

Open
8 tasks
maryjom opened this issue Jul 24, 2020 · 1 comment
Open
8 tasks

Resolve "iframe element has accessible name" feedback #473

maryjom opened this issue Jul 24, 2020 · 1 comment
Assignees

Comments

@maryjom
Copy link
Collaborator

maryjom commented Jul 24, 2020

Survey results

Wilco

Trevor

  • Editorial: The note under failed example 4 has two colons. Are we allowing notes inside of the examples, or should we find a different place for that as well. Need to determine how to handle the notes before publishing for consistency I think.
  • Could the note in the applicability section moved under accessibility support as possibly unsupported by browsers?

Kathy

  • https://act-rules.github.io/rules/cae760#inapplicable-example-3
    Inapplicable Example 3 - This iframe element has a negative tabindex and therefore is not included in the sequential focus navigation. <iframe tabindex="-1" src="/test-assets/SC4-1-2-frame-doc.html"> </iframe> Is this included in the accessibility tree? If so, it should not be inapplicable. Clarify inapplicable example 3
  • There's recent emails about iframes need a title from the AG WG that discusses the need for this rule.
  • Issues 1367 and 1170.
@WilcoFiers
Copy link
Collaborator

RESOLUTION: iframes without an accessible name should have a rule for SC 4.1.2, that rule must include passing examples using aria-label and aria-labelledby

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

No branches or pull requests

2 participants