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

New rule: ARIA required owned elements #468

Open
ajanec01 opened this issue Jul 17, 2020 · 3 comments
Open

New rule: ARIA required owned elements #468

ajanec01 opened this issue Jul 17, 2020 · 3 comments

Comments

@ajanec01
Copy link

The ACT-Rules community group has completed work on ARIA required owned elements. We would like to see this rule be added to the WCAG ruleset. You can find the rule here:

Rule title: ARIA required owned elements
Rule id: bc4a75
Link to the rule: ARIA required owned elements
License: W3C Software And Document Notice And License
Implementors:

  • QualWeb
  • SortSite
@maryjom
Copy link
Collaborator

maryjom commented Jul 24, 2020

Created survey due 6 August.

@tbostic32
Copy link
Collaborator

Feedback

Rule: https://act-rules.github.io/rules/bc4a75
Survey results: https://www.w3.org/2002/09/wbs/93339/ACTRuleARIArequiredOwns/results

Trevor

  • Passed example 4 invalid html. <li> element not under under any of<li>, <ul>, <menu>. Elements with role="menuitemradio" and role="menuitemcheckbox" don't have required attribute aria-checked.

  • Notes 1 and 3 could be moved into the background section.

Kathy

  • Element has implicit semantic role that is identical to its explicit semantic role. Why is this exempt in the applicability?

@tbostic32
Copy link
Collaborator

My first comment on the HTML is being addressed in this pull request: act-rules/act-rules.github.io#1414

From our discussion the invalid HTML is intended and should be covered by the accessibility support section.

Kathy's comment is currently under discussion in issue act-rules/act-rules.github.io#1413

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

4 participants