WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG - Fail or not to - Static text tab-focusable in tables

for

From: Abi James
Date: Jan 1, 2021 11:50AM


This has been an interesting thread to follow over the New Year holiday but I would agree with the earlier contributions that this is a WCAG failure for all the good examples of negative impact on the user.

I would usually apply 2.1.1 keyboard operable as, while WCAG does not define "operable", we all understand that to be that keyboard operation a site must be actually operable for the user and so match the expected keyboard patterns. Wouldn't we fail a site that overrode tab key as the keyboard operation for moving focus?

For a table where static text is tab focusable I would be highlight to the developer that it has broken the mental model for keyboard users and they should
- if the cells are meant to be interactive (as indicated by receiving focus) then they should be operable with enter or spacebar.
- if the table contains interactive cells then it should match the data grid keyboard pattern where focus is moved through the cells using arrow keys.
- if the table cells are not interactive then they should not receive focus.

As adding focusable elements within a table is highly likely to break a screen reader's table navigation function, I would also make sure the tables are thoroughly tested with a screen reader which may add weight to a 2.1.1 non conformance.

I am not saying I would always fail 2.1.1 for a static text/element receiving focus but when a component has clearly been built to not match expected keyboard operation, as documented in the WAI-ARIA patterns, then it should not be considered accessible.

Regards

Abi James


On 1 Jan 2021, at 17:35, Patrick H. Lauke < <EMAIL REMOVED> > wrote:

CAUTION: This e-mail originated outside the University of Southampton.

On 01/01/2021 17:30, Steve Green wrote:

> You might think you're providing added value, but my experience is that stakeholders do not welcome it. In the vast majority of cases, we find that clients only fix what they have to fix i.e. the level A and AA non-conformances. They don't want to know about anything outside of that.
>
> Of course there are exceptions where clients really care about the user experience, so your context is important in determining what you do and don't report. But that decision should be driven by what your stakeholders want, not your personal biases.

And even in those contexts, I'd say it's important to make a clear
distinction between what is an actual hard failure of WCAG, and what
does go above and beyond the minimum normative requirements. If nothing
else, for consistency with any other reports/audits from other companies
the client may be getting. Ditto when doing an Accessibility Conformance
Report based on VPAT. Otherwise, it negates the point of them being all
based on the same baseline understanding of WCAG.

P
--
Patrick H. Lauke

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.splintered.co.uk%2F&amp;data%7C01%7Ca.james%40soton.ac.uk%7C00c5079b8675402ec34e08d8ae7b9cab%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637451193220315464%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=LP%2FJdD8Mfrxkkk2AnNHPP2uODgQKID4x7xfyVt15x7Q%3D&amp;reserved=0 | https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatrickhlauke&amp;data%7C01%7Ca.james%40soton.ac.uk%7C00c5079b8675402ec34e08d8ae7b9cab%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637451193220325460%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=vZlR1jdCuhLdm5DQxGEMmJc1gk%2FYfwL1qZVZmRU7P68%3D&amp;reserved=0
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&amp;data%7C01%7Ca.james%40soton.ac.uk%7C00c5079b8675402ec34e08d8ae7b9cab%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637451193220325460%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdatas8l8O%2FhjTVoH6haNDfLGmnml2T6z5Ixl0ESYuxNI3g%3D&amp;reserved=0 | https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.deviantart.com%2Fredux&amp;data%7C01%7Ca.james%40soton.ac.uk%7C00c5079b8675402ec34e08d8ae7b9cab%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637451193220325460%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=%2FnhoWKYDfW38o2ey4ZZ4oPpC0i0moEC9whHgB2tl4pc%3D&amp;reserved=0
twitter: @patrick_h_lauke | skype: patrick_h_lauke