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

Listbox role: clarification about Accessible Name Guidance #2856

Open
kantoche opened this issue Nov 7, 2023 · 3 comments
Open

Listbox role: clarification about Accessible Name Guidance #2856

kantoche opened this issue Nov 7, 2023 · 3 comments
Assignees
Labels
editorial Changes to prose that don't alter intended meaning, e.g., phrasing, grammar. May fix inaccuracies. Feedback Issue raised by or for collecting input from people outside APG task force Inaccuracy Incorrect statement in prose (not a code bug) Practice Page Related to a page within the practices section of the APG

Comments

@kantoche
Copy link

kantoche commented Nov 7, 2023

Hi,

In the article Providing Accessible Names and Descriptions, Listbox role has its Necessity of Naming equals to "Required"
See: https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/#accessiblenameguidancebyrole),

But in the design pattern Listbox, we can read : "If the element with role listbox is not part of another widget, such as a combobox, then it has either a visible label referenced by aria-labelledby or a value specified for aria-label." So, in this case the Necessity of Naming should not be "Required".
But there is no status of Necessity of Naming corresponding to a name provided by a previous or a parent content as it should be the case with a combobox.
See: https://www.w3.org/WAI/ARIA/apg/patterns/listbox/

So, could you clarify this issue?

@mcking65
Copy link
Contributor

Related to w3c/aria#1725. This is a valid APG issue.

@mcking65 mcking65 self-assigned this Dec 19, 2023
@a11ydoer
Copy link
Contributor

a11ydoer commented Dec 19, 2023

There is also open APG issue #2290

@mcking65 mcking65 added editorial Changes to prose that don't alter intended meaning, e.g., phrasing, grammar. May fix inaccuracies. Feedback Issue raised by or for collecting input from people outside APG task force Inaccuracy Incorrect statement in prose (not a code bug) Practice Page Related to a page within the practices section of the APG labels Dec 19, 2023
@css-meeting-bot
Copy link
Member

The ARIA Authoring Practices (APG) Task Force just discussed Listbox naming guidance.

The full IRC log of that discussion <jugglinmike> Topic: Listbox naming guidance
<jugglinmike> github: https://github.com//issues/2856
<jugglinmike> Matt_King: Listbox *does* require a name in ARIA, but in a composite like a combobox, we don't require a name on the element itself.
<jugglinmike> Matt_King: I think this is in part an ARIA question, not just an APG question
<jugglinmike> jamesn: I believe there's already an issue for this
<jugglinmike> jamesn: Maybe I'm misremembering, though
<jugglinmike> Jem: Should we transfer this to ARIA, then?
<jugglinmike> Matt_King: We might need a separate issue for ARIA
<jugglinmike> Matt_King: We got some feedback on this issue, but that was back in the 1.1 combobox days when these things were separate
<jugglinmike> jamesn: Is it easiest to recommend a name on the listbox in this case, even though it's redundant?
<jamesn> previous issue was https://github.com/w3c/aria/issues/1725
<jugglinmike> Matt_King: I'll take this issue
<jugglinmike> Matt_King: I'm going to label this as an inaccuracy; I believe this is all editorial
<jugglinmike> Jem: this is related to issue 2290
<jugglinmike> Jem: https://github.com//issues/2290

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial Changes to prose that don't alter intended meaning, e.g., phrasing, grammar. May fix inaccuracies. Feedback Issue raised by or for collecting input from people outside APG task force Inaccuracy Incorrect statement in prose (not a code bug) Practice Page Related to a page within the practices section of the APG
Projects
None yet
Development

No branches or pull requests

4 participants