September 10, 2018 Meeting
Matt King edited this page Sep 11, 2018
·
2 revisions
(Continuation of August 27 discussion)
The ARIA specification for alert includes the following two sentences:
Since alerts are not required to receive focus, content authors SHOULD NOT require users to close an alert.
And:
If an alert requires focus to close the alert, then content authors SHOULD use alertdialog instead.
The APG Alert pattern says:
It is also important to avoid designing alerts that disappear automatically. An alert that disappears too quickly can lead to failure to meet [WCAG 2.0 success criterion 2.2.3.]https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-no-exceptions.html()
- "too quickly" is ambiguous.
- If alerts do not disappear automatically and cannot not have a close icon, when do they go away?
- Isn't it possible to give an alert a focusable close icon even if it does not appear in a dialog that steels focus?
Related issues:
- Current toolbar does not pass regression tests; open bugs in Issue 847: Toolbar Example: Bugs with keyboard support, aria-disabled, and aria-label.
- Jon has student working on new toolbar example; demos an editor toolbar.
- Bocoup contract work on regression tests will wrap up next week.
- Try to get new toolbar done in time for tests to be developed by Bocoup? Or, fix bugs in existing toolbar?
- October 22 and 29: No meetings due to 2018 W3C TPAC
- Home
- About the APG TF Work
- Contributing
- Meetings
- Management and Operations Documentation
- Publication Change Logs