-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“Pointer Input” not well defined in Glossary #1762
Comments
agree, have not been happy with the bastardisation/redefinition of "pointer input" to then talk directly about the device/hardware. #809 went through various attempts to square that circle without needing to redefine it. I might make another stab at that PR, perhaps a bit wordy...
or something along those lines (as it's not an input mechanism as per your suggestion, but more the actual input event/result itself that was done with the hardware) |
ok, had another stab at improving things in #809 ... maybe at some point this almost 2 year old PR may get a look in ;) |
Thanks @patrickhlauke! |
So, still no resolution here, and it looks like the bad definition is also going to make its way into WCAG 2.2. Is there anything we can do to fix it before 2.2 gets published? |
/me mutters something about "agile"... |
Fixed in I can't believe that it happened. Thanks @patrickhlauke! |
The Pointer Input Glossary item reads:
The link points to the definition of pointer which reads:
The WCAG definition is used in SC 2.5.5 Target Size:
I don't think it makes sense to have pointer defined as the “hardware agnostic representation of input devices” and then define “pointer input” as those “input devices”.
I think what is meant in SC 2.5.5 is the actual element that is targeted.
The glossary should change to something along these lines:
(I’m unsure if I have understood this correctly, but if the device is meant, why don’t we say “The size of the target for pointers [instead of pointer inputs] is at least 44 by 44 CSS pixels except when:” in SC 2.5.5? That is an unnecessary re-definition in that case.)
Related: #749/#809
The text was updated successfully, but these errors were encountered: