Technical Accessibility

Developers love to debate frameworks and libraries. As accessibility advocates, it’s important to us that accessibility is considered in these debates. The common question is: “Is React accessible?” But that’s not quite the right way to think about it.

Awareness is important but on this Global Accessibility Awareness Day, we are wishing for bigger changes to reduce friction, reduce costs, and create better markets and incentives for accessibility.

You can Google around and find all sorts of accessibility checklists out there. But do these checklists track the right things?

Logins are critical to the digital world. We need them to keep the bad guys out of our stuff. This includes everything from our email, bank, social media, and e-commerce accounts. And that necessarily creates barriers, which can sometimes present accessibility issues. UX, engineering, and security professionals designing login systems have the difficult task of balancing ease of use with safeguards to keep bad actors out. Following accessibility principles and best practices, including new success criteria for accessible authentication in the brand new WCAG 2.2 release, can ensure that login systems don’t lock out people with disabilities.

If you are new to the topic of web accessibility, there is a lot to absorb about what it means to make your website accessible. Some common accessibility issues are inherent to the way your site was coded while others have more to do with the content that you populate into your site.