Dennis Deacon examines how inaccessible gift card emails and redemption pages can exclude people with disabilities. He identifies common HTML and keyboard accessibility issues, including missing alt text, unassociated form labels, and inaccessible help content, then shows how simple fixes restore access.
Read Congrats! You Just Received an Inaccessible Gift Card …
Scott O’Hara explores the accessibility challenges of HTML’s title attribute, including inconsistent browser and screen reader support. He explains common misuses and identifies situations where title can still provide accessibility value.
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.
Dennis Lembrée examines the accessibility of SVG icons, icon fonts, sprites, and images, comparing their strengths and limitations. Using Easy Chirp as a case study, he explores screen reader support, keyboard access, performance, styling, and the practical tradeoffs of each approach.
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.
Melanie Sumner and Sean Massa explain how developers can build more accessible web applications through semantic HTML, appropriate ARIA, keyboard support, accessible names, automated testing, and screen reader testing, while integrating accessibility into their teams and development communities.
Sam Joehl explores techniques for providing equivalent content to screen reader users when visual information lacks a direct programmatic alternative. The article covers visible alternatives, ARIA, visually hidden text, and choosing appropriate techniques to create more accessible web experiences.
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.