Skip to content

August 27, 2018 Meeting

Jump to bottom
Matt King edited this page Aug 29, 2018 · 3 revisions

Agenda for August 27, 2018

Issue 605: distinguishing menuitemcheckbox from menuitemradio

Datepicker proposal

Editorial proposal:

  1. Put this datepicker in combobox section.
  2. Consider making some other datepickers in examples for other patterns, e.g., spin button.
  3. Later, for issue 57, make a section that references the various datepickers throughout the guide. That section could provide guidance on how to choose a pattern for a datepicker.

Spin button guidance for aria-invalid

As part of resolution to issue 704, Seeking consensus to add the following guidance to the spin button pattern as proposed in PR 825:

The spinbutton element has aria-invalid set to true if the value is outside the allowed range. Note that most implementations prevent input of invalid values, but in some scenarios, blocking all invalid input may not be practical.

Spinbutton structure

Alert dismissing and hiding

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:

Future meetings and other business

  • September 3: no meeting due to US Labor Day holiday.

Meeting Resources

Clone this wiki locally