> accessibility is not hard This has not been my experience based on my involvement in accessibility efforts at two medium-to-large companies that decided to m

> accessibility is not hard This has not been my experience based on my involvement in accessibility efforts at two medium-to-large companies that decided to make their existing web-based products accessible to blind and low-vision users. In one of the cases we brought in accessibility consultants, created a usability testing pool of users with various vision and motor impairments, conducted training for dozens of front-end developers, revised our framework, and made changes to many product UIs. After several years and millions of dollars of effort a few products were functionally usable by blind and vision-impaired users. Note that this is distinct from being WCAG compliant, which is a good place to start but doesn't guarantee your product is actually accessible. I think it was the right choice and it made our products better for everyone, but it was Very Hard and it required buy-in up to the executive level. I'd consider it grossly unfair to blame individual developers or call them "hobbyists" solely based on the fact that they worked for years on products that did not have good accessibility. If anything, the assumption that accessibility is something an individual developer who is sufficiently "professional" can just choose to add to their interfaces makes me suspect either the author lacks experience working in a medium/large development organization or they are just targeting WCAG compliance rather than functional accessibility.