E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 4 (In chronological order)

From: Michael Hanton
Date: Mon, May 27 2019 2:28AM
Subject: 508 chapter 3 and non-WCAG keyboard issues
No previous message | Next message →

--_004_BL0PR08MB53322552F3F3F5CEFB510AD7911D0BL0PR08MB5332namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I'm wondering, for keyboard issues that do not fail WCAG 2.0 but are nevert=
heless accessibility barriers, should these be called out in a VPAT under C=
hapter 3? Specifically, under 302.7 With Limited Manipulation?

For example, Where you have an index, Table of Contents, or carousel that c=
ontains 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 mod=
e of operation is provided, ICT shall provide at least one mode of operatio=
n that does not require fine motor control or operation of more than one co=
ntrol at the same time."? That seems to be a catch-all clause requiring acc=
essibility for non-mouse users.

All opinions welcome.

Michael Hanton
Skillsoft | phone: +353 1 2181049
Accessibility Specialist
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > | www.ski=
llsoft.com<http://www.skillsoft.com>;
[cid:image001.jpg@01D5146E.8ED8D230]<http://www.skillsoft.com/>;


--_004_BL0PR08MB53322552F3F3F5CEFB510AD7911D0BL0PR08MB5332namp_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=2532;
creation-date="Mon, 27 May 2019 08:28:37 GMT";
modification-date="Mon, 27 May 2019 08:28:37 GMT"
Content-ID: <image001.jpg@01D5146E.8ED8D230>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAeAB4AAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMg
IyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/2wBDAQsLCw8NDx0QEB09KSMpPT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT3/wAARCAArAKADASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2aiii
gAoriPif40v/AAXpdlcadDbyPPMY289SQAFzxgium8P6hJq3h3Tr+dVWW6to5nVOgLKCce3NAGjR
RXm9v458QyfFl/D76ao00OyZ8ttwQLkSbumD+XOOtAHpFFebx/ETU3+LZ8Lm3tPsPmmPftbzOI92
c5x19qXW/iHqem/FKz8Nw29o1nNJCjOyt5nz4zg5x39KAPR6KKKACiiigAooqjrOrW2haRdalesV
t7ZC7Y6n0A9ycD8aAL1FeLJ8WfGWrtLe6H4dSTTomwcQSSn6FgRzj0FekXHjHT9E0vTp/E08WmXV
5EH8k7m2tgbhwO2RQBo69qL6Tod5fRIrvBEXVW6E+9YPh34h6brJSC7xZXZ42ufkc/7Lf0NanilH
vvCOoLaq0zS258tUGS2emBXn2h/DmadY7nX5hY27EBYiwEjk9Bk8Ln86iTlzaHp4Wlhp4eUqzs76
d/u6nWeJvHB8Na/b2k1qJrWSESOyN86ncRwOh6Vv6Rrlhrlt5+n3KSqPvKOGT2I6iuB8aeFL7UNf
0+00m0doIrNYxIxOxAGPVj7Y966Hwn4Dt/DsovJp2uL7aV3LlUUHqAO/1P6UJy5vIK1LCLDRkpe/
b7/Xt/W5V+IPxGTwdJbWNnafbdTuRuSIk7VGcAnHJJOQAPSuWl+I/j/SF+1av4VT7J1YrDIu0e7Z
OPxFX/ip4F1fV9Ws/EHh795eWqKrRBgGG1iysueCQT0+lZNh8Zta0W5Sz8X6I6no0iIYpMeu1uD+
GKs8wk+NN6+peCvD95JbvbPcSeYYXOWTKZwa7zQdWs9D+G2k3+ozrDbQ6fCWY/7g4A7k+lcJ8bNR
ttX8H6FfWMgltriYvG47gp/OvONa1/WvEOh2AnhkGkaYkdqgjU+XvC4yx/vED8O1AHsvgnx5r3jX
Xp3ttMtrfQYWIaaTd5h4+VQc4LdCeMAfhlIPiLqMvxYbws1ra/YxIyeaA3mcRls5zjqPSum8D3ek
3vhCwl0KJYLLy9ohHWNh95W9TnOT36968ss/+TkX/wCviT/0QaAEg/5ORP8A18t/6INO8V/8nB6b
/wBd7X+lNg/5ORP/AF8t/wCiDTvFf/Jwem/9d7X+lAHc/EH4jL4OltrGzs/tup3K7kiJO1QTgE45
JJyAB6Vy83xH8f6Qv2rV/CqfZOrFYZF2j3bJx+Iq/wDFPwLq+ravZ+IfD37y8tUVWiDAOCrFlZc8
Egnp7Csmw+M2s6LdJZ+L9EdSOGkRDFJj12twfwxQB6bL4mtbHwpHrurI9jC0KytE/LqWHC+55xXm
p+L/AIn125lHhbw350EZ+80bzN+O0gD6Uz43a0mp+HPD8thN5lheNJOGHRsBQM+43NxXpvg/TbXS
vCWmW1kirF9nRyVH32ZQSx9yTmgDhPD3xmdtWXTPFmm/2bOzBPNAZVQnpvVuVHvmj42+ILy30dtG
j0yV7S6jjke+BOxCHzt6Yz8o796Z8e9NtW0HT9RKqt2lx5AbHLIVYkfgVH5n1o8T3U15+z1bTXBJ
laC3DE9Th1AP6CgDD+HXjzVtG0Cz0u08MXN9b+ewN1Hvx8zc9FI4z61mfGPxBeavrkVndaXLZxaf
LNHDK+cXAyBuGQBj5R0z1r0z4Nf8k3sv+usv/oZrkv2gv9ZoP0n/APZKAN3wl8Rda1PUNN02fwnd
W9vIFjN0d+1QF+9ymMcetanxW58MQf8AX0v/AKC1dbpn/IKtP+uKf+giq2vaDaeIrJLW+MgiSQSf
u2wSRnj6c0pK6sdGEqxpVozlsmeb+CfFevreR2EMMmpW+QCrH5oh67+w9jXrVVtP02z0u1W3sbeO
CJf4UGM+59T9atUoppasvGV4V6nNCHL+p534y8V+L/DPiNp7TRRfaF5agbFLHd/ESV5U545BGBXG
eLfG+ofEXS49G07wtcicyq/mHMhQj0+UY9yT0r3eiqOQ8N+IHhm90P4Y+GtLaN5riCZzL5QLBWYF
iOPTOPwr0Xw/4bsL/wCGNhpFzaCKC5sU81Au0h2UEt/vbufrXW0UAeHeALnVfh946uPDuowTyWFz
KI/MSNioc/ckHsRgH9elS2lncj9op5jbzeV57nzNh248k969sooA8Shs7kftFGY283lfaGO/YduP
IPOaXxTaXL/H3Tplt5miE9sd4QlcDGea9sooA868ZeLPF/hjxI09poovtC8tQuxSx3fxEleVOeOQ
RgVxvi7xrqHxG0yLRtO8LXImMofzDmQoR6fKMe5J6V7vRQB5tffDGa/+Fen6FJKi6pZAzRuT8okJ
JZM+nzYz7A1y+ifEDxR4Csk0bXPD89zHbfJC7bkIXsNwBDAdsV7jRQB4Pd23iv4v6za/abF9N0iA
8MykIgPUgnG9vpx9Oa7v4n6Ytr8KbjT9PhcxwCCONEG4hVdR29hXe0UAcP8AB+GWD4dWSTRvG/mS
na6kH75rF+OHhu/1jS9Pv9PgkuPsTOJY413MFbb82O4G3n616lRQB5T4I+Jeua1qem6U+gMLdVEV
zcoHO3C4DdMLyBnOa9WoooAKKKKAP//Z

--_004_BL0PR08MB53322552F3F3F5CEFB510AD7911D0BL0PR08MB5332namp_--

From: Patrick H. Lauke
Date: Mon, May 27 2019 2:33AM
Subject: Re: 508 chapter 3 and non-WCAG keyboard issues
← Previous message | Next message →

On 27/05/2019 09:28, Michael Hanton wrote:

> 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.

While annoying, tabbing through hundreds of links does not "require fine
motor control" (doesn't *require*, say, use of a mouse...yes, it's a
right pain for pure keyboard users, but they do get to activate the
right link when they reach it in the end), nor the use of "more than one
control at the same time".

So strictly no, I wouldn't say you can just interpret this as a
catch-all for what is, in the end, a usability problem for keyboard
users. However, you can feel free to "Pass", but still add a note, in
the Accessibility Conformance Report.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Sean Murphy
Date: Mon, May 27 2019 4:38AM
Subject: Re: 508 chapter 3 and non-WCAG keyboard issues
← Previous message | Next message →

Michael,

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 ADDRESS 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 ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > | www.skillsoft.com<;http://www.skillsoft.com>;
> [cid:image001.jpg@01D5146E.8ED8D230]<http://www.skillsoft.com/>;
>
> > > >

From: glen walker
Date: Mon, May 27 2019 8:35AM
Subject: Re: 508 chapter 3 and non-WCAG keyboard issues
← Previous message | No next message

The only way you could force this into a non-compliance issue was if your
"index, Table of Contents, or carousel" were "repeated on multiple Web
pages", then it would be a 2.4.1 Bypass Blocks issue.

If the hundreds of tabs were only on one page, then it's not considered a
Bypass Blocks issue, but you could still recommend a UX change to have a
skip link just before the carousel (or whatever element has all the tabs
stops) to jump over it, as Patrick and Sean suggested.

Glen