IssueTracker

The article Accessibility for web developers has two problematic items:

1. Since "assistive technology" is often used as a stand-in for screen readers, this statement is less than ideal (it should disambiguate the specific AT the author means):

Keyboard-only and assistive technology users need to be able to place keyboard focus on elements to interact with them

2. The following paragraph gives no warning of the risk:

A tabindex value greater than 0 places the element in a manual tab order. All elements in the page with a positive tabindex value are visited in numerical order, before elements in the natural tab order.

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 positive tabindex 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