28085 2015-02-23 19:34:54 +0000 pattern-listbox changes based on 2/23/2015 meeting 2018-05-14 17:28:18 +0000 1 1 1 Unclassified ARIA Practices 1.1 PC Windows NT RESOLVED FIXED P2 normal --- 1 w3cbugzilla a11ythinker oldest_to_newest 118099 0 w3cbugzilla 2015-02-23 19:34:54 +0000 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) 120631 1 a11ythinker 2015-06-01 17:40:34 +0000 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. 120632 2 a11ythinker 2015-06-01 17:44:22 +0000 Adda link to a section explaining the difference between roving tabindex and aria-activedescendant 120633 3 a11ythinker 2015-06-01 17:45:32 +0000 The aria-activedescendant vs roving tabindex statement should be in the roles, states, and properties row of the table. 120634 4 a11ythinker 2015-06-01 18:06:23 +0000 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. 120635 5 a11ythinker 2015-06-01 18:08:55 +0000 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. 120636 6 a11ythinker 2015-06-01 18:34:36 +0000 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+/. Change: ◾ Shift+Up Arrow and Shift+Down Arrow move and extend the selection. to: ◾ 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. 121010 7 a11ythinker 2015-06-15 17:36:38 +0000 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. 121012 8 a11ythinker 2015-06-15 17:39:35 +0000 In last paragraph, change the numerals to words; 5 should be five. 121013 9 a11ythinker 2015-06-15 17:45:21 +0000 up and down arrow in 5th bullet of kb interaction should say up and down arrow. 121014 10 a11ythinker 2015-06-15 17:46:29 +0000 home and end are missing for moving to beginning and end 121015 11 a11ythinker 2015-06-15 18:00:10 +0000 Add up/down arrow as first item in selection model 2 and look at order of items in the 2 lists.