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

Use of group within list is unclear #1011

Closed
JAWS-test opened this issue Jul 16, 2019 · 4 comments · Fixed by #1053
Closed

Use of group within list is unclear #1011

JAWS-test opened this issue Jul 16, 2019 · 4 comments · Fixed by #1053
Assignees
Labels
has PR PR exists that will close this issue
Milestone

Comments

@JAWS-test
Copy link
Contributor

JAWS-test commented Jul 16, 2019

Neither the definition of the roles list, listitem and group nor the definition of aria-level in the specification contains any indication of how nested ARIA lists are created. Is the use of group sufficient or is aria-level required? If there is an element with role=group in role=list, this could be used to group or nest the list entries...? Unfortunately, the specification makes no statement about this.
Therefore I would like to know how

<ul><li>...<ul><li>...</ul></ul>

is marked in ARIA. I would also suggest changing the specification so that it becomes clear.

@JAWS-test
Copy link
Contributor Author

Just to let you know what the output of JAWS 2019 (e.g. with IE 11 and in Chrome) of ARIA lists is like:

The following roles are not output as nested lists (specified in the order of their nesting in the source code)

  • list - group - listitem
  • list - listitem - group - listitem
  • list - listitem with aria-level
  • list - listitem - listitem

The following elements are output as a nested list

  • list - list - listitem
  • list - listitem - list - listitem
  • list - listitem - group - list - listitem (with additional output of the group)

So this seems to be quite a mess, while for HTML it is clearly specified how nested lists must be marked.

@a11ydoer a11ydoer self-assigned this Jul 18, 2019
@joanmarie joanmarie added this to the ARIA 1.2 milestone Jul 18, 2019
@joanmarie
Copy link
Contributor

Making 1.2 for now and asking APG TF to look into.

@sh0ji
Copy link

sh0ji commented Aug 20, 2019

I haven't been able to find any instance where it made any meaningful difference to use group instead of list in my research and support the notion to remove it here.

@jnurthen
Copy link
Member

See dequelabs/axe-core#1200 for more discussion on this

@jnurthen jnurthen added F2F Topics For F2F (or virtual F2F) and removed F2FCandidate Candidate topics for F2F (or Virtual F2F) meeting labels Sep 3, 2019
@scottaohara scottaohara self-assigned this Sep 11, 2019
@jnurthen jnurthen added has PR PR exists that will close this issue and removed F2F Topics For F2F (or virtual F2F) labels Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has PR PR exists that will close this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants