3 ms·
It mentions on the widget itself that it's accessible. That makes sense at a high level, since it doesn't require interaction. But I'm curious if it might nee
by tyingq 5y ago
It mentions on the widget itself that it's accessible. That makes sense at a high level, since it doesn't require interaction.
But I'm curious if it might need more work in the 'accessible' area. Like, for example, is the progress bar percentage-done exposed in an accessible way? I don't see anything obvious here: https://git.sequentialread.com/forest/pow-captcha/src/branch/master/static/captcha.js#L102 https://git.sequentialread.com/forest/pow-captcha/src/branch... , seems like it just changes width via css styling, but I could be missing it. I'm not sure it presents an easily understandable reason why the submit button is disabled, that you need to wait, etc, either.
- forestjohnson 5y agoYes, unfortunately I don't know anyone who uses a screen reader personally and I've never spent the time to learn how to use one myself. So I don't really have a great way to make it accessible to blind users at the moment, but it's only a couple code changes away, while most other "Captcha" solutions might require a redesign before they could be considered accessible.