Posted August 06, 2018
The W3C has had a public notice posted about "Inaccessibility of CAPTCHA" since at least 2005.
About a month ago they started to revise and update a working draft for a new version of "Inaccessibility of CAPTCHA". They're using GitHub for comments and changes, but also have an email address in case that isn't feasible.
Of particular note in that document is section 2 for "Security effectiveness", or rather the ineffectiveness of CAPTCHA.
The W3C also has "Web Accessibility Initiative" (WAI) on their website, with news about progress along those lines.
However, the W3C can only make recommendations. Software developers have to figure out the implementation for each circumstance encountered based on their available resources in the moment. Unfortunately, they're only human.
About a month ago they started to revise and update a working draft for a new version of "Inaccessibility of CAPTCHA". They're using GitHub for comments and changes, but also have an email address in case that isn't feasible.
Of particular note in that document is section 2 for "Security effectiveness", or rather the ineffectiveness of CAPTCHA.
The W3C also has "Web Accessibility Initiative" (WAI) on their website, with news about progress along those lines.
However, the W3C can only make recommendations. Software developers have to figure out the implementation for each circumstance encountered based on their available resources in the moment. Unfortunately, they're only human.
Post edited August 06, 2018 by thomq