E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 8 (In chronological order)

From: Alastair Campbell
Date: Thu, Jun 27 2013 5:02PM
Subject: Valid elements for aria-required
No previous message | Next message →

Hi everyone,

I was just about to enter a bug for a screen reader about
aria-required not working on some form elements, and realised I don't
have a list of the requirements it should work on.

In the WAI-ARIA spec [1] it says 'form elements that require input or
selection by the user', should that include radio buttons, checkboxs
and select elements?

The HTML5 spec doesn't appear to specify [2], and all the examples
only seem to use text inputs. I could be looking in the wrong place
there though!

Would it be valid to raise a big that required doesn't work on other
form elements?

-Alastair

1] http://www.w3.org/TR/wai-aria/states_and_properties#aria-required
2] http://www.w3.org/html/wg/drafts/html/master/forms.html#concept-input-required

From: James Nurthen
Date: Thu, Jun 27 2013 5:55PM
Subject: Re: Valid elements for aria-required
← Previous message | Next message →

IMO yes for SELECT but not for checkbox and radio button. The aria spec
states that it is valid on the roles

- combobox <http://www.w3.org/TR/wai-aria/roles#combobox>;
- gridcell <http://www.w3.org/TR/wai-aria/roles#gridcell>;
- listbox <http://www.w3.org/TR/wai-aria/roles#listbox>;
- radiogroup <http://www.w3.org/TR/wai-aria/roles#radiogroup>;
- spinbutton <http://www.w3.org/TR/wai-aria/roles#spinbutton>;
- textbox <http://www.w3.org/TR/wai-aria/roles#textbox>;
- tree <http://www.w3.org/TR/wai-aria/roles#tree>;


Listbox is the ARIA equivalent of SELECT but the list above does not
include checkbox and radiobutton. I'm not sure what required means on a
checkbox or radiobutton anyway.

Regards,
James


On Thu, Jun 27, 2013 at 4:02 PM, Alastair Campbell < = EMAIL ADDRESS REMOVED = > wrote:

> Hi everyone,
>
> I was just about to enter a bug for a screen reader about
> aria-required not working on some form elements, and realised I don't
> have a list of the requirements it should work on.
>
> In the WAI-ARIA spec [1] it says 'form elements that require input or
> selection by the user', should that include radio buttons, checkboxs
> and select elements?
>
> The HTML5 spec doesn't appear to specify [2], and all the examples
> only seem to use text inputs. I could be looking in the wrong place
> there though!
>
> Would it be valid to raise a big that required doesn't work on other
> form elements?
>
> -Alastair
>
> 1] http://www.w3.org/TR/wai-aria/states_and_properties#aria-required
> 2]
> http://www.w3.org/html/wg/drafts/html/master/forms.html#concept-input-required
> > > >

From: Joshue O'Connor
Date: Fri, Jun 28 2013 1:12AM
Subject: Re: Valid elements for aria-required
← Previous message | Next message →

Hi Alastair,

> I was just about to enter a bug for a screen reader about
> aria-required not working on some form elements, and realised I don't
> have a list of the requirements it should work on.
[...]
> Would it be valid to raise a big that required doesn't work on other
> form elements?

I'd file it as a bug as it will put this issue on the WGs radar. We could argue if it's a bug or
not ;-) but filing it will help feed into any future requirements gathering that's done that
may result in expanding aria-required use on other HTML elements.

FWIW, I would have thought that it 'should' work on other elements and not just input
boxes (if needed) for accessible UI development.

HTH

Josh

> -Alastair
>
> 1] http://www.w3.org/TR/wai-aria/states_and_properties#aria-required
> 2]
> http://www.w3.org/html/wg/drafts/html/master/forms.html#concept-input-r
> equired
> > > Follow us on Facebook: https://www.facebook.com/ncbiworkingforpeoplewithsightloss
Follow us on Twitter: www.twitter.com/ncbi_sightloss

Check-out NCBI's Micheal O Muircheartaigh appeal on the following link.
http://youtu.be/25P2tiuCi0U

********************************************************************
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. It is the policy of NCBI Group and all of its subsidiary companies to disallow the sending of offensive material.
Should you consider that the material contained in this message is offensive you should contact the sender immediately and also = EMAIL ADDRESS REMOVED = .

********************************************************************

From: Patrick H. Lauke
Date: Fri, Jun 28 2013 2:41AM
Subject: Re: Valid elements for aria-required
← Previous message | Next message →

On 28/06/2013 00:55, James Nurthen wrote:
> I'm not sure what required means on a
> checkbox or radiobutton anyway.

On a group of radio buttons it means that the user has to have made a
selection among the different mutually exclusive choices. It makes sense
if none of the radio buttons are checked at the start, otherwise that
constraint is already satisfied even if the user has made no active choice.

Can't remember if browsers actually enforce required attribute on a
fieldset...may need to do some mild testing.

P
--
Patrick H. Lauke

From: Alastair Campbell
Date: Fri, Jun 28 2013 2:44AM
Subject: Re: Valid elements for aria-required
← Previous message | Next message →

James Nurthen wrote:
> I'm not sure what required means on a
> checkbox or radiobutton anyway.

Good point, there's no grouping element there. A bit of testing
applying 'required' to all of them didn't do anything.

Patrick wrote:
> Can't remember if browsers actually enforce required attribute on a
> fieldset...may need to do some mild testing.

I think it's only <input>s, but it would make sense on a fieldset if
used for radio buttons or checkboxes.

Thanks,

-Alastair

From: Alastair Campbell
Date: Fri, Jun 28 2013 5:49AM
Subject: Re: Valid elements for aria-required
← Previous message | Next message →

James Nurthen wrote:
> IMO yes for SELECT but not for checkbox and radio button. The aria spec
> states that it is valid on the roles
>
...
> - radiogroup <http://www.w3.org/TR/wai-aria/roles#radiogroup>;

At a top level it would make sense to allow for a group of radio
buttons (or checkboxes) to be required. I can see instances where you
don't want to pre-select a radio button, but do want it to be required
(so there is no argument that they just went with the default.)

However, you are right that adding it to the inputs doesn't make much
sense, and there is no defined grouping element we can assume is used.

Patricks idea of fieldsets makes the most sense from an HTML point of
view, perhaps its something that should be added to the HTML5x spec?

-Alastair

From: Steve Faulkner
Date: Fri, Jun 28 2013 6:04AM
Subject: Re: Valid elements for aria-required
← Previous message | Next message →

note adding the html5 required attribute to one radio button makes all
radio buttons in a set required (as in one must be chosen)


regards
stevef

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;


On 28 June 2013 12:49, Alastair Campbell < = EMAIL ADDRESS REMOVED = > wrote:

> James Nurthen wrote:
> > IMO yes for SELECT but not for checkbox and radio button. The aria spec
> > states that it is valid on the roles
> >
> ...
> > - radiogroup <http://www.w3.org/TR/wai-aria/roles#radiogroup>;
>
> At a top level it would make sense to allow for a group of radio
> buttons (or checkboxes) to be required. I can see instances where you
> don't want to pre-select a radio button, but do want it to be required
> (so there is no argument that they just went with the default.)
>
> However, you are right that adding it to the inputs doesn't make much
> sense, and there is no defined grouping element we can assume is used.
>
> Patricks idea of fieldsets makes the most sense from an HTML point of
> view, perhaps its something that should be added to the HTML5x spec?
>
> -Alastair
> > > >

From: Alastair Campbell
Date: Fri, Jun 28 2013 8:08AM
Subject: Re: Valid elements for aria-required
← Previous message | No next message

Thanks, sounds good, presumably a select element should already be
valid for 'required'?

Steve Faulkner wrote:
> note adding the html5 required attribute to one radio button makes all
> radio buttons in a set required (as in one must be chosen)

>
> regards
> stevef
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;
>
>
> On 28 June 2013 12:49, Alastair Campbell < = EMAIL ADDRESS REMOVED = > wrote:
>
>> James Nurthen wrote:
>> > IMO yes for SELECT but not for checkbox and radio button. The aria spec
>> > states that it is valid on the roles
>> >
>> ...
>> > - radiogroup <http://www.w3.org/TR/wai-aria/roles#radiogroup>;
>>
>> At a top level it would make sense to allow for a group of radio
>> buttons (or checkboxes) to be required. I can see instances where you
>> don't want to pre-select a radio button, but do want it to be required
>> (so there is no argument that they just went with the default.)
>>
>> However, you are right that adding it to the inputs doesn't make much
>> sense, and there is no defined grouping element we can assume is used.
>>
>> Patricks idea of fieldsets makes the most sense from an HTML point of
>> view, perhaps its something that should be added to the HTML5x spec?
>>
>> -Alastair
>> >> >> >>
> > >