This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28085 - pattern-listbox changes based on 2/23/2015 meeting
Summary: pattern-listbox changes based on 2/23/2015 meeting
Alias: None
Product: ARIA
Classification: Unclassified
Component: Practices (show other bugs)
Version: 1.1
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Matt King
QA Contact:
Depends on:
Reported: 2015-02-23 19:34 UTC by James Nurthen
Modified: 2018-05-14 17:28 UTC (History)
0 users

See Also:


Description James Nurthen 2015-02-23 19:34:54 UTC
Change Tab text to something like 

Tab: When the listitem receives focus for the first time, move focus to the first option with aria-selected="true". If nothing has aria-selected="true" then then move focus to the first option and, optionally, select the item depending on functionality desired.

to communicate what should happen on focus... see minutes for more details

Edit something about the first letter navigation to state that is should be supported if more than 7 options

Shift+up/down needs to go into selection section

Do something with the checkboxes section....
(need to continue)
Comment 1 Matt King 2015-06-01 17:40:34 UTC
If focus is set to the container with role listbox then aria-activedescendant must be used to refer to the option that has the visual focus indicator.
Comment 2 Matt King 2015-06-01 17:44:22 UTC
Adda link to a section explaining the difference between roving tabindex and aria-activedescendant
Comment 3 Matt King 2015-06-01 17:45:32 UTC
The aria-activedescendant vs roving tabindex statement should be in the roles, states, and properties row of the table.
Comment 4 Matt King 2015-06-01 18:06:23 UTC
Need an example that uses the checked state on options and emphasizes that this is not coded using the checkbox role. Consider an example where partially checked can be used.
Comment 5 Matt King 2015-06-01 18:08:55 UTC
Remove first comma from:
◦ If an option is selected, before the listbox receives focus, focus is set on the selected item when the listbox receives focus.
Comment 6 Matt King 2015-06-01 18:34:36 UTC
Chage order of sentence:
• Multiple Selection: In multi-select listboxes, the author may choose between 2 types of selection models. One model requires a modifier key, e.g., shift or control, to change the selection state, and the other does not. 
to match presentation.

Rewrite description of selection models so that the difference in modifier key usages are clear.
It is not clear that model 1 does not require modifiers because it lists keys with modifiers.

Remove ctrl+\ and ctrl+/.

◾ Shift+Up Arrow and Shift+Down Arrow move and extend the selection. 
◾ Shift+Up Arrow and Shift+Down Arrow move focus and extend the selection. 

Add the word optionally to the beginning of key assignments that are not essential.

Add ctrl+a to selection model 1.

Add a bullet that applies to both selection models about a button, link or checkbox for selecting all and deselecting all.
Comment 7 Matt King 2015-06-15 17:36:38 UTC
Move content advice about options in the description  into a note. Leone is taking an action to get them into WCAG techniques so we can eventually reference WCAG.
Comment 8 Matt King 2015-06-15 17:39:35 UTC
In last paragraph, change the numerals to words; 5 should be five.
Comment 9 Matt King 2015-06-15 17:45:21 UTC
up and down arrow in 5th bullet of kb interaction should say up and down arrow.
Comment 10 Matt King 2015-06-15 17:46:29 UTC
home and end are missing for moving to beginning and end
Comment 11 Matt King 2015-06-15 18:00:10 UTC
Add up/down arrow as first item in selection model 2 and look at order of items in the 2 lists.