A developer explains how they built a web app using the Canvas API to add a blue beanie to user photos for Blue Beanie Day.
Argues that web browsers should actively warn against and eventually block performance-harming and inaccessible web development practices.
A developer discusses the challenge of deciding when an interactive graph is core content versus a progressive enhancement, and how client requirements can shift that definition.
A critique of the aria-controls attribute, arguing it's poorly supported, confusing, and ineffective for accessibility.
DigitalOcean details the technical rebuild of their website, focusing on improved accessibility, performance, and a new unified design system.
A developer advocates for writing less code to improve performance, reduce maintenance, and create a better user experience, with practical tips.
A technical guide on implementing accessible modal dialogs following WAI-ARIA specifications, covering markup, focus management, and keyboard interactions.
Explains the crucial differences between HTML links and buttons, focusing on accessibility, semantics, and proper use in modern JavaScript web applications.
A developer reflects on lessons from early responsive web design to avoid similar pitfalls when implementing Progressive Web Apps (PWAs).
Argues that web accessibility benefits all users, not just those with disabilities, and improves business outcomes by reaching a wider audience.
A tutorial on setting up a self-hosted web accessibility testing dashboard using the open-source Pa11y tool on a DigitalOcean server.
A developer explains why they switched from icon fonts to SVG for web icons, citing performance, accessibility, and maintainability benefits.
A developer argues against forcing external links to open in new tabs, advocating for user control and confidence in website content.
A web developer reflects on winning an O'Reilly Web Platform Award for her work in accessibility and encouraging women in tech.
Advocates for browsers to display image alt text during loading to improve UX on slow connections and accessibility.
A guide to correctly labeling HTML form elements using name, id, label, fieldset, and legend for accessibility and functionality.
Argues that all websites must begin with server-side rendered HTML for universal accessibility, even if they later use advanced JavaScript features.
A web developer recommends and reviews two industry books: 'Adaptive Web Design, 2nd Edition' on progressive enhancement and 'Using WebPageTest' for performance analysis.
A developer documents the open redesign of their personal website, focusing on performance, accessibility, and modern web features.
Explains how to use ARIA attributes (aria-labelledby, aria-label, aria-describedby) to properly label HTML elements for screen readers and improve web accessibility.
