E-mail List Archives
Re: qr code and guidelines
From: Joe Humbert (A11y)
Date: Sep 12, 2020 7:28AM
- Next message: Patrick H. Lauke: "Re: qr code and guidelines"
- Previous message: Patrick H. Lauke: "Re: Suggestion required for Facebook iframe feed provided in a web page"
- Next message in Thread: Patrick H. Lauke: "Re: qr code and guidelines"
- Previous message in Thread: Bo Nilsson: "qr code and guidelines"
- View all messages in this Thread
Hi Bo,
In my opinion, its always good to have an alternative way for 2-form factor
authentication (2FA) (e.g., Authenticator app, phone call, text message,
email, etc.). For example, any users camera could be scratched or an update
to the camera app could be screwing things up.
While, I don't think any WCAG SC completely covers this, it could fail
against 2.4.5 Motion Actuation, since a user has to move the camera into a
position to read the QR code, the (2FA) motion could be deemed essential
(probably would be for security reasons). But an alternative would fulfill
this SC.
I have seen scanning functionality implemented fairly accessibly for users
with vision impairments when real-time auditory feedback is provided (e.g.,
no code detected, camera to close, move back to focus, Code successfully
scanned, etc.). If this auditory (and hopefully Braille compatible)
feedback is implemented, it will go a long way to making it accessible.
However, users with mobility impairments, particularly those who mount their
phones in a fixed position (e.g., to a wheelchair) may still find scanning
the QR code difficult.
Hope this helps.
Thankx,
Joe Humbert
Accessibility Champion
Android & iOS Accessibility Novice
- Next message: Patrick H. Lauke: "Re: qr code and guidelines"
- Previous message: Patrick H. Lauke: "Re: Suggestion required for Facebook iframe feed provided in a web page"
- Next message in Thread: Patrick H. Lauke: "Re: qr code and guidelines"
- Previous message in Thread: Bo Nilsson: "qr code and guidelines"
- View all messages in this Thread