- From: James Elliott via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Mar 2025 05:52:24 +0000
- To: public-webauthn@w3.org
No technology is going to cover all users. At some point you have to say "we can't support that". Why are we excluding the users who use text-only (i.e. non-HTML) based screen readers? Most recent statistics on this indicate less than 0.2% o 1.6% of all requests are made by screen readers that don't support or have disabled javascript. So the question is where is the line in the sand? As far as supporting it with the least effort possible (which is probably going to be a requirement if it's implemented).. my guess is the best way to support it is with an invisible form input element, and contains a `challenge` or similar attribute with base64 web encoded JSON as the attribute value which contains the input parameters to the existing JS API, and a attribute to indicate if the form should be auto submitted, with the response being written to the input value base64 web encoded. This way the input/output is very simple to manage and the API for it is uniform. -- GitHub Notification of comment by james-d-elliott Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1255#issuecomment-2723681241 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 March 2025 05:52:25 UTC