Scott Vinkle explores how React developers can use eslint-plugin-jsx-a11y to identify accessibility issues in JSX. The article demonstrates configuring the linter for browser consoles, code editors, and CI workflows, helping teams catch accessibility problems earlier in development.
Paul J Adam reviews accessibility testing tools for desktop and mobile websites, including WAVE, aXe, a11yTools, tota11y, and HTML_CodeSniffer. He explains how automated tools complement manual keyboard and screen reader testing to identify accessibility issues earlier.
Read Accessibility Testing Tools for Desktop and Mobile Websites …
Eric Bailey explains how to build a cloud-hosted Windows computer with Amazon WorkSpaces for accessibility testing. The guide addresses barriers to Windows access, explains why browser testing services may be insufficient, and provides step-by-step instructions for creating a virtual accessibility testing environment.
Read How to Build a Cloud-Hosted Accessibility Testing Windows Computer using Amazon WorkSpaces …
Marcy Sutton explains how automated accessibility testing can strengthen development workflows, prevent regressions, and free teams for complex testing. She explores unit and integration tests, keyboard interactions, axe-core, and why automation must complement manual and user testing.
Tim Wright explores why text resizing and zooming are essential for people with low vision. He examines WCAG 1.4.4, the impact of disabling user scaling, and how small development changes can significantly improve accessibility and create a better experience for users.
Scott O’Hara uses a Three Little Pigs-inspired story to show how developers can create accessibility barriers through poor HTML, CSS, JavaScript, and ARIA choices. He highlights semantic HTML, keyboard access, accessibility testing, and learning from users with disabilities.