W3C home > Mailing lists > Public > public-aria@w3.org > September 2017

RE: Logic behind aria-required not being valid on role=checkbox?

From: Matt King <a11ythinker@gmail.com>
Date: Sun, 17 Sep 2017 23:47:20 -0700
To: "'Michiel Bijl'" <michiel.list@moiety.me>
Cc: "'Bryan Garaventa'" <bryan.garaventa@levelaccess.com>, "'ARIA Working Group'" <public-aria@w3.org>
Message-ID: <012901d33049$faa57690$eff063b0$@gmail.com>
In the case described, the user interface is requiring a specific value. The question is whether ARIA should be able to help assistive technologies in a case like that. If the AT can identify required fields to the user, then, shouldn't the AT be enabled to identify the checkbox that requires user action in order for the user to proceed?

The definition of aria-required is:

> Indicates that user input is required on the element before a form may be submitted.

The checkbox Bryan describes meets that definition.


-----Original Message-----
From: Michiel Bijl [mailto:michiel.list@moiety.me] 
Sent: Sunday, September 17, 2017 11:20 PM
To: Matt King <a11ythinker@gmail.com>
Cc: Bryan Garaventa <bryan.garaventa@levelaccess.com>; ARIA Working Group <public-aria@w3.org>
Subject: Re: Logic behind aria-required not being valid on role=checkbox?

Thing is that the checkbox can’t be required as such because it always has a value, it’s always 0 or 1. It’s never invalid. HTML required doesn’t dictate the final value. Neither should aria-required.

— Michiel

> On 18 Sep 2017, at 03:59, Matt King <a11ythinker@gmail.com> wrote:
> That seems valid to me. Worth raising an issue.
> Matt
> -----Original Message-----
> From: Bryan Garaventa [mailto:bryan.garaventa@levelaccess.com]
> Sent: Friday, September 15, 2017 7:26 PM
> To: ARIA Working Group <public-aria@w3.org>
> Subject: Logic behind aria-required not being valid on role=checkbox?
> Hi,
> Somebody brought a use case to my attention today regarding the use of 
> aria-required and role=checkbox, and it seems like a valid one, 
> however aria-required doesn't appear to be supported on role=checkbox.
> The use case being that of a License Agreement checkbox where, if the 
> checkbox is not checked then the form will not submit, so technically 
> interacting with the checkbox is required to proceed.
> Would there be any interest in adding aria-required as a supported 
> attribute of role=checkbox in this case?
> Bryan Garaventa
> Accessibility Fellow
> Level Access, Inc.
> Bryan.Garaventa@LevelAccess.com
> 415.624.2709 (o)
> www.LevelAccess.com
Received on Monday, 18 September 2017 06:47:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 18 September 2017 06:47:46 UTC