WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Honeypots & SC 1.3.1

for

From: glen walker
Date: Apr 17, 2023 10:56AM

I'm not sure I see the programmatic relationship with the fake hidden field
to make it a 1.3.1. It might be a focus order or focus visible issue, but I
generally reserve those for input fields that are intended to be focused.
In this case, the input field is for preventing spambots so it has a
purpose but isn't really intended for users to navigate to it. You could
potentially have sr-only text to explain what the field is for and even
visible explanatory text that displays if you navigate to the field with
the keyboard (kind of like how some skip links appear when you tab). But I
suppose there's a potential that that might prevent the spambot from
accessing it.

In general, though, I agree with Patricks that *if* it's a failure of some
sort, then it's very mild, if that. And that might be explained away by an
"exception" rule that many guidelines have such as 3.3.3 that says "unless
it would jeopardize the security or purpose of the content".