WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: series about Accessible Forms

for

From: Roger Hudson
Date: May 18, 2013 10:33PM


Thanks Sailesh,

I hadn't considered this and the result of your testing with NVDA and JAWS
is very interesting. Given that it relies on ARIA I wouldn't expect the
technique to be well supported by WindowEyes, and from Paul's comment it
seems that VoiceOver support is a little patchy.

Regards,
Roger

-----Original Message-----
From: Sailesh Panchang [mailto: <EMAIL REMOVED> ]
Sent: Sunday, 19 May 2013 11:49 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] series about Accessible Forms

Roger,
For grouping fields, certainly fieldset-legend is generally the way to go.
However, using role=group / role=radiogroup works fairly too and can be
relied upon when the page design makes it challenging to use
fieldset/legend.
Both methods can be compared on the sample page linked from
http://www.deque.com/aria-group-viable-alternative-fieldset-legend
Thanks,
Sailesh Panchang

On 5/14/13, Roger Hudson < <EMAIL REMOVED> > wrote:
> Many thanks Jennifer for the writing about the accessible forms
> articles and for providing this information to help people subscribe
> and/or contact me.
>
> And, thanks to Dave for pointing out the difficulties in subscribing.
>
> I will make some changes in the near future, but right now I am
> working on the third article.
>
> Regards,
> Roger
>
> -----Original Message-----
> From: Jennifer Sutton [mailto: <EMAIL REMOVED> ]
> Sent: Wednesday, 15 May 2013 3:05 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] series about Accessible Forms
>
> In case any of the hundreds of people on this list have this same
> question, when somebody sends me something from a site that I want to
> continue to track, here are the steps I'd take to do so.
>
> 1. Look for an RSS feed and subscribe to it. In this case, here it is:
>
> http://usability.com.au/feed/
>
> 2. Contact the site author to explore my options if for some reason
> RSS is not something I can use. I use RSS all the time, but maybe a
> lot of people have forgotten its value.
>
> Here's the Contact page:
>
> http://usability.com.au/contact/
>
> 3. Look up the site author, or company, on social media of choice.
> Mine is Twitter, so here's Roger on it:
>
> https://twitter.com/rogerhudson
>
> If I hadn't already known that the site is run by Roger, and I
> couldn't figure it out by the Contact page, I'd go to the About page
> to look for a name or company I could locate on social media:
>
> http://usability.com.au/about/
>
>
> I took the time to compile this list of approaches in hopes it helps
> many on the list to follow up with the resources posted here. There's
> plenty that goes on in the Web accessibility arena beyond this list.
>
> At 04:15 AM 5/14/2013, you wrote:
>>Looks great, thanks.
>>
>>Is there any way you know of subscribe to notifications of new posts
>>there?
>>I didn't see one, but I probably just missed it?
>>
>>Dave Merrill
>>
>>
>>On Mon, May 13, 2013 at 7:13 PM, Jennifer Sutton
> < <EMAIL REMOVED> >wrote:
>>
>> > Greetings, WebAIM:
>> >
>> > I'd like to extend public thanks and recognition to Roger Hudson,
>> > and the many others he acknowledges, for this current "in progress"
>> > series on Accessible Forms.
>> >
>> > The first two of a projected five parts have been posted. the
>> > links
> are:
>> >
>> > Accessible Forms 1 Labels and identification Web Usability
>> >
>> >
>> http://usability.com.au/2013/04/accessible-forms-1-labels-and-identif
>> i
>> cation/
>> >
>> > Accessible Forms 2: Required Fields and Extra Information | Web
>> > Usability
>> >
>> >
>> http://usability.com.au/2013/05/accessible-forms-2-required-fields-an
>> d
>> -extra-information/
>> >
>> > I encourage those who are interested to continue to follow Roger's
>> > blog for the remainder of the series.
>> >
>> > Best,
>> > Jennifer
>> >
>> > >> > >> > list messages to <EMAIL REMOVED>
>> >
>>
>>
>>
>>--
>>Dave Merrill
>>>>>>list messages to <EMAIL REMOVED>
>
> > > list messages to <EMAIL REMOVED>
>
> > > list messages to <EMAIL REMOVED>
>
messages to <EMAIL REMOVED>