[Athen] Keyboard focus and layout tables
kpham at swccd.edu
Fri Sep 20 10:52:27 PDT 2019
Thank you very much. This helps provides a lot of answers.
From: athen-list <athen-list-bounces at mailman12.u.washington.edu> On Behalf Of Fathauer, Laura
Sent: Wednesday, September 18, 2019 1:36 PM
To: Access Technology Higher Education Network <athen-list at u.washington.edu>
Subject: Re: [Athen] Keyboard focus and layout tables
WCAG 2.1 introduced a contrast ratio requirement for non-text elements of 3.0; the success criteria has this note:
In combination with 2.4.7 Focus Visible<https://www.w3.org/TR/WCAG21/#focus-visible>, the visual focus indicator for a component must have sufficient contrast against the adjacent background when the component is focused, except where the appearance of the component is determined by the user agent and not modified by the author.
Laura Fathauer, WAS
Web Content Accessibility Specialist
316B Shriver Center
Oxford, OH 45056
On Tue, Sep 17, 2019 at 6:23 PM Khoa Pham <kpham at swccd.edu<mailto:kpham at swccd.edu>> wrote:
My apologies if these questions have already been asked.
1. What are the standard or criteria for an acceptable visible keyboard focus indication?
2. Should tables be used to for page content layout such as in Canvas, word documents, and PDFs regardless of the number of table cells used?
I’ve found that some keyboard focus indications are clear and very easy to see when navigating with the keyboard, while other makes me wonder if they are sufficient enough to be considered accessible. Please see the attached images for examples.
For table layouts, I’ve seen a few being used with a minimum of two cells to provide an image of an instructor adjacent to the cell that contains their information. Would this be acceptable?
Thanks in advance,
athen-list mailing list
athen-list at mailman12.u.washington.edu<mailto:athen-list at mailman12.u.washington.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the athen-list