WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 508 chapter 3 and non-WCAG keyboard issues


From: Sean Murphy
Date: May 27, 2019 4:38AM


You are talking about usability not accessibility. If the user can access the actual link and as Patrick is already stated in my take the hundred SolTabs to get there. That's a usability not accessibility. It would be different if they could not get to the element.

Please excuse any errors due to Siri.

My experience is the part

> On 27 May 2019, at 6:28 pm, Michael Hanton < <EMAIL REMOVED> > wrote:
> Hi all,
> I'm wondering, for keyboard issues that do not fail WCAG 2.0 but are nevertheless accessibility barriers, should these be called out in a VPAT under Chapter 3? Specifically, under 302.7 With Limited Manipulation?
> For example, Where you have an index, Table of Contents, or carousel that contains hundreds of links that you would need to TAB through to get to the following content. This doesn't fail any WCAG 2.0 SC (as far as I can see) but it is a major barrier for keyboard users. Does it therefore contravene Section 508 302.7 With Limited Manipulation which says: "Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or operation of more than one control at the same time."? That seems to be a catch-all clause requiring accessibility for non-mouse users.
> All opinions welcome.
> Michael Hanton
> Skillsoft | phone: +353 1 2181049
> Accessibility Specialist
> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > | www.skillsoft.com<;http://www.skillsoft.com>;
> [cid:image001.jpg@01D5146E.8ED8D230]<http://www.skillsoft.com/>;
> > > >