October 2, 2017 Meeting

Agenda for October 2, 2017

Release 1 Publication Planning

• Publication planning project
• Current milestone:

1. What must be in that is not done?
2. Important things that should be in that are not done:
   • Combobox examples
   • Disclosure pattern (examples are done)
   • Feed examples
   • Listbox examples (mostly editorial cleanup)
   • Grid examples done but not fully reviewed
   • Switch?
   • Should we pull window splitter to focus on other things, or try to finish it?
   • Should we pull incomplete parts of keyboard section 4?
     • 4.2 Discernible and Predictable Keyboard Focus
     • 4.8.1.3 Choose Where to Add Shortcuts
     • 4.8.2.1 Operating System Key Conflicts
     • 4.8.3 Exposing and Documenting Keyboard Shortcuts
   • There are internal links to section 5, Grid and Table Properties

Issue 413: KeyBoard navigation for xOS

Issue 413 - KeyBoard navigation for xOS is about the following text in the introduction of the design pattern section:

Although users of Mac OS X are familiar with using the Command key instead of the Control key, the Command key is typically reserved for desktop applications and OS-level integration. Until device and platform independence can be addressed in WAI-ARIA 2.0, the primary Control modifier key for WAI-ARIA widget interaction is specified as Control on all platforms, including Mac OS X.

Discuss options:

1. Revise this paragraph to make it more accurate. Even in native, CMD does not correspond to Control on Windows except for in a few cases like clipboard copy and paste.
2. Remove this paragraph.
3. Remove the paragraph and add: A. A section to the keyboard interface section about Mac OS keys B. A note to the new section in each pattern where it could apply.
4. Other?

Examples of ARIA 1.1 Combobox with Listbox Popup

• Implementation of ARIA 1.1 Combobox with listbox popup in combo-examples-1.1 branch
• Issue 100: Develop examples of ARIA 1.1 Combobox design pattern

Notes and questions:

1. We've worked only on the example code; the supporting documentation is not yet started.
2. Should the different types of autocomplete all be on one page or broken out to multiple pages?
3. Open issue to discuss with browser and screen reader devs: How should labeling be done? Should we allow the textbox and popup to have distinct labels? For example, "Fruits and Vegetables" on textbox and "Suggested Fruits and Vegetables" on the popup?

Meeting Resources

• This Meeting's Minutes
• Prior Meeting (September 18) Minutes
• All Meetings
• All Git Issues
• Editor's draft on github pages
• RawGit of master branch
• Current Public Working Draft on w3.org/tr
• Defects open in bugzilla