WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: for Chrome devs: intro to accessibility course

for

From: Bryan Garaventa
Date: Sep 12, 2013 12:05PM

In reading this, it looks good, but there are some areas that are of concern
to me.

The basic ARIA advice, such as adding role=button to Divs is correct.

It doesn't specify however, that supporting scripting must be added as well
to ensure functionality, otherwise the ARIA attributes added by themselves
will not ensure accessibility for screen reader and keyboard only users.

Within the section "Elements with onclick handlers must be focusable", it
specifies that it is good to add tabindex to a span with a click event.

It does not specify however, that a key event must also be added to ensure
keyboard accessibility, otherwise it will be impossible to press Enter on
the element to activate it. Instead, it says "Elements which have click
handlers but are not focusable can not be used by keyboard-only users.",
which is only partially correct.
Also, a valid ARIA role must be added to provide a textual role of the
element for screen reader users, such as role=button or role=link, otherwise
screen reader users will not be aware that the element is supposed to be an
active element.

These omissions will cause some very large accessibility issues to occur for
users of various Assistive Technologies when used in differing browser
combinations.



----- Original Message -----
From: "Jennifer Sutton" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Thursday, September 12, 2013 9:56 AM
Subject: Re: [WebAIM] for Chrome devs: intro to accessibility course


> For those who may be interested and have not seen, I thought I'd
> share the link that shows the auditing tests that can be done with
> Google's dev tools:
>
> https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules
>
>
>
> > >