August 6, 2018 Meeting

Agenda for August 6, 2018

Publication target: December 2018
Plan summary on Wiki
Confirm Jon working on both patterns and examples (not just examples). Both are required to be included in the release.

Questions asked in the issue:

What should the value of aria-valuenow be when a user provides invalid input? Should aria-valuenow not change? Should it be set back to some default when the spinbutton loses focus? Should the input be undone by reverting to the previous value?
What should aria-valuenow be when the user deletes the text in the spinbutton?
Would the WG consider adding instructions to set aria-invalid on spinbuttons when the value is invalid, either because it's nonsense or because it's outside of the specified range?

Bryan raised Issue 459: Manual activation tabs is confusing when aria-selected alone is seperate from focus
Should this drive some browser requirements to aria-controls or raise JAWS bug? See ARIA issue 531
Appropriateness of aria-expanded on tab elements?

Issue 614: Question about how role="separator" is supposed to work in Menu widgets
Issue describes level of support in various AT/browser combinations.
Raises the question of purpose; only to support reading mode/touch?
Should separators be labeled? Or, should there only be labeling if using a group, which should be announced in forms/focus mode?