WebAIM - Web Accessibility In Mind

E-mail List Archives

Interpretation of WCAG 1.4.13

for

From: Peter Quale
Date: Jul 18, 2018 8:30AM

Hello all,

I'm hoping to get some opinions on the breadth of WCAG 2.1 guideline
1.4.13, Content on Hover or Focus.

I'm helping with a datepicker widget that opens down from a form field when
the user focuses on the field. The datepicker will sometimes close when
blurred and sometimes not and in the past I would call this out to the
client as a UX issue that affects accessibility. This client is also keen
on addressing 2.1 issues immediately now that the standard is launched.

So my question to the group is does this behavior fit within the spirit of
guideline 1.4.13? The datepicker does obscure the field immediately
following the date field, but it is also possible to close the datepicker
by backtracking to the date field and intentionally using an enter
keypress.

My opinion is that while this is not likely a barrier, it is cumbersome to
go back and intentionally close the datepicker when it does not close. I'm
inclined to require the client to make the datepicker always close on blur.

For reference, here is a link to the guideline.
https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html

Any thoughts or opinions are greatly appreciated.

Thank you all!

-Peter

--
*Peter Quale*
Google Voice: (707) 992-5696