WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: A simple beginner's question

for

From: Robert Fentress
Date: May 23, 2016 12:47PM

Also, perhaps I'm misunderstanding the question, but aren't there a lot of
other instances where ARIA would be useful in a site that doesn't use AJAX,
beyond just remediation? I'm thinking widgets like trees, menus, dialogs,
etc., where the roles, states, and properties are not a part of the HTML
standard yet. Not using AJAX doesn't mean that you're not using dynamic
HTML.

On Mon, May 23, 2016 at 12:50 PM, Robert Fentress < <EMAIL REMOVED> > wrote:

> Another argument for where ARIA might be useful on pages that don't use
> AJAX is when you want to signal to a user that a field is required but do
> not want focus to be automatically moved to the required field should the
> user attempt to submit the form without entering anything in that field.
> For instance, you can signal that a field is required using
> the HTML5 "required" attribute, but I believe that automatically moves
> focus in most (all?) browsers, which could be viewed as disorienting. In
> that instance, "aria-required" *might* be better, since it doesn't result
> in this behavior, but still informs the screen reader user that the field
> is required. Though I suppose you could accomplish much the same thing
> using hidden text in the label, I like the idea of having this information
> conveyed semantically somehow.
>
> On Mon, May 23, 2016 at 8:35 AM, Léonie Watson < <EMAIL REMOVED> > wrote:
>
>> > From: Birkir R. Gunnarsson [mailto: <EMAIL REMOVED> ]
>> > Sent: 23 May 2016 12:42
>> > aria-describedby is the best technique in my experience to relate error
>> > messages to form fields If your error checking happens when user submits
>> > the form you:
>> > 1. use aria-describedby to associate error message with form fields and
>> 2.
>> > Move focus to the first form field with an associated error message.
>>
>> You can do this, but if you're using aria-describedby to associate useful
>> information with the field already, it can get messy. With something like
>> an error, sticking to old-school HTML seems like the best option, if for no
>> other reason than backwards compatibility.
>>
>> Plenty of ways to "skin the cat" of course :)
>>
>>
>>
>> Léonie.
>>
>> --
>> @LeonieWatson tink.uk Carpe diem
>>
>>
>>
>> >> >> >> >>
>
>
>
> --
> Robert Fentress
> Senior Accessibility Solutions Designer
> 540.231.1255
>
> Technology-enhanced Learning & Online Strategies
> Assistive Technologies
> 1180 Torgersen Hall
> 620 Drillfield Drive (0434)
> Blacksburg, Virginia 24061
>



--
Robert Fentress
Senior Accessibility Solutions Designer
540.231.1255

Technology-enhanced Learning & Online Strategies
Assistive Technologies
1180 Torgersen Hall
620 Drillfield Drive (0434)
Blacksburg, Virginia 24061