RE: Does the HTML5 required attribute have the same accessibility affect as aria-required for an ARIA defined widget?

James,

Just so I understand, you recommend developers support both required and aria-required attributes on standard from controls for legacy browser/AT support?

Jon


-----Original Message-----
From: James Craig [mailto:jcraig@apple.com] 
Sent: Thursday, May 08, 2014 12:30 PM
To: Gunderson, Jon R
Cc: Steve Faulkner; w3c-wai-pf@w3.org WAI-PFWG; wai-xtech@w3.org
Subject: Re: Does the HTML5 required attribute have the same accessibility affect as aria-required for an ARIA defined widget?


On May 8, 2014, at 10:21 AM, Gunderson, Jon R <jongund@illinois.edu> wrote:

> James,
> 
> What I am getting at is what is a clear message to developers on what to do:
> 
> If a form control is required:
> 
> 1. Use the required attribute on standard HTML form controls, and 
> don't use aria-required

This statement is accurate for modern browsers. There are some legacy versions that exposed @aria-required to the AX trees but not @required. For these, it would be fine for web authors use both attributes, as long as the values were not in conflict. Redundancy for the sake of legacy support is fine.

Required:
  <input required aria-required="true">
  <!-- include both true values -->

Not required:
  <input>
  <!-- omit both false values (false is the default value for both, so there is no need to include aria-required="false") -->

> 2. For ARIA defined widgets use aria-required attribute and don't use 
> the required attribute

AFAIK, this statement is accurate for all browsers.

> While there may be combinations of markup that would be technically correct, describing these combination to developers might be confusing and more than they want (or need)  to know to make something accessible.
> 
> Thanks,
> Jon
> 
> 
> -----Original Message-----
> From: James Craig [mailto:jcraig@apple.com]
> Sent: Thursday, May 08, 2014 12:16 PM
> To: Gunderson, Jon R
> Cc: Steve Faulkner; w3c-wai-pf@w3.org WAI-PFWG; wai-xtech@w3.org
> Subject: Re: Does the HTML5 required attribute have the same accessibility affect as aria-required for an ARIA defined widget?
> 
> On May 8, 2014, at 10:05 AM, Gunderson, Jon R <jongund@illinois.edu> wrote:
> 
>> So the following would be also be considered  invalid, since the aria-required attribute is in conflict with the required attribute:
>> 
>> <input type="checkbox" required aria-required="true">
> 
> I would call your example redundant, but not in conflict. Both @required and @aria-required have true values. Likewise the following example is redundant but not in conflict.
> 
>  <input type="checkbox" aria-required="false"> <!-- @required is false 
> (implicit) and @aria-required is also false (explicit) -->
> 
> However, the following examples are in conflict:
> 
>  <input type="checkbox" aria-required="true"> <!-- @required is false 
> (implicit) and @aria-required is true (explicit) -->  <input 
> type="checkbox" required aria-required="false"> <!-- @required is true 
> (explicit) and @aria-required is false (explicit) -->
> 
> James
> 
>

Received on Thursday, 8 May 2014 17:34:27 UTC