Fixed
Status Update
Comments
ke...@gmail.com <ke...@gmail.com> #2
Reported
ke...@gmail.com <ke...@gmail.com> #3
Reportrd
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com> #4
This one also has a note added to warn against positive tabindexes.
me...@adrianroselli.com <me...@adrianroselli.com> #5
I appreciate the note and correction.
The post, however, does not explain what was changed, when it was changed, nor why it was changed.
The changes also don't address the first item of the two issues I noted.
Description
The article Accessibility for web developers has two problematic items:
This reads as an endorsement of using positive
tabindex
values. This post fails to mention the significant risk of failing 2.4.3 Focus Order. In years of performing WCAG reviews I still have yet to see a positivetabindex
value that did not result in a WCAG violation. For a post explicitly about accessibility, this is significant problem.I came upon this article because a junior dev asked me to explain why this article, why Google was recommending something counter to my own guidance to them.
Related issue on another article against which I filed a bug report:https://issuetracker.google.com/u/1/issues/350944652