Accessibility, Page 2

Part 4 explores the ValidityState API, a powerful, approachable, and well-supported API we can use to define custom validation messages.

Parts 1 and 2 of this series explore the browser's built-in HTML & CSS form validation features and how to progressively enhance the experience by layering in JavaScript. This article continues the exploration, focusing on a use case not handled natively: a checkbox group.

In Part 2 of this series, we take the base HTML and CSS form validation experience and progressively enhance it by adding JavaScript and the Constraint Validation API while also addressing accessibility concerns.

I had the opportunity this week to talk to Nicole Mors, Product Design Manager at Driveway. We dove into the challenges of managing a living design system, what designers can do to improve…

Using the native HTML disclosure widget for a burger menu is so enticing. Unfortunately, the details/summary elements come with accessibility issues, so it's not an inclusive solution.

Progressive enhancement or a great Cumulative Layout Shift metric score? Why not both?

Learning VoiceOver can feel overwhelming, so I’m here to give you a simple, repeatable process you can follow to make testing with VoiceOver as easy as possible.

These days, the arguments for a baseline font size of 16 pixels are widely accepted. But there are plenty of reasons to go even larger!

We’re thrilled to announce that we’ve added accessibility tree snapshots to Pleasantest. These snapshots incorporate important accessibility details into your tests, helping you to understand, track, and maintain the accessibility of your interfaces. We believe Pleasantest is the first testing tool to provide this incredibly useful feature.