WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: building accessible javascript accordions?

for

From: Bryan Garaventa
Date: Aug 3, 2013 12:37PM

No problem. I found that, if the interactive coding for particular design
patterns isn't provided, it is extremely difficult to accurately gage the
accessibility and usability of the component.

So, this is what the AccDC TSG is designed to do, to establish a functional
baseline that is proven to be accessible through comprehensive accessibility
testing.

When I refer to testing, I mean accessibility testing for screen reader and
keyboard only users, for voice navigation users via common keyboard
interaction commands, and for standard sighted users, all of which are
accounted for.

The live pages are all linked within the component sections, so they can
easily be tested by others as well.

----- Original Message -----
From: "Alastair Campbell" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Friday, August 02, 2013 3:42 PM
Subject: Re: [WebAIM] building accessible javascript accordions?


> Wow, thanks Bryan.
>
> Did I manage to stumble into the worst case straight off, or are there
> plenty more?? ;-)
>
> I've been in user-research land for a couple of years but I'm getting
> stuck into the docs again now, I'll be sure to keep AccDC TSG to hand
> as I do.
>
> When you say testing, do you mean UAT style "does it work as
> expected", and/or regular users trying tasks?
>
> Both are useful, I'm just trying to gauge where the core interaction
> issues might be, separately from the confusion for developers.
>
> Kind regards,
>
> -Alastair
> > >