August 6, 2018 Meeting
- 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.
- Issue 704: Spinbutton: What should aria-valuenow be when a user gives invalid input, when should it update?
- Spec for aria-valuenow
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?
Issue 1: APG tooltip pattern says:
If the tooltip is invoked when the trigger element receives focus, then it is dismissed when it no longer has focus (onBlur). If the tooltip is invoked with mouseIn, then it is dismissed with on mouseOut.
WCAG 2.1 1.4.13 Content on Hover or Focus says:
If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing. The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
In the ARIA spec it is the triggering element (link/button) only that controls the show/hide of the tooltip content (additional content). This conflicts with the WCAG spec where focus needs to encompass the trigger and additional content.
Issue 2: Understanding Success Criterion 1.4.13: Content on Hover or Focus
role=tooltip does not allow active embedded elements, however, the WCAG 2.1 spec states:
Provide a mechanism to easily dismiss the additional content, such as by pressing Escape or selecting a close button.
- 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?
- September 3: no meeting due to US Labor Day holiday.
- Home
- About the APG TF Work
- Contributing
- Meetings
- Management and Operations Documentation
- Publication Change Logs