TL;DR: Regardless of what accessibility conformance level you target, try to ensure that interactive controls are at least 44 by 44 pixels in size. Links in blocks of text are exempt. Overview In real life there is typically both a visual and tactile component to an interface. You have to…
I am going to propose a way to increase the overall accessibility of the WordPress ecosystem. It requires acknowledging some mistakes and using those as the base for building a better platform. I long for a world where a metric for featuring #WordPress themes and plugins in the repo is…
I kind of missed it this year. I was presenting at YGLF and was invested in the other talks, so my annual tweet thread of my accessibility posts since the previous GAAD did not come out on time. Instead I filled up timelines last night. Below are eight tweets with…
I (and the audience) survived my talk today. As our mutual reward, I offer my slides. All the links turned white onupload, so they are nearly impossible to read. I am sharing it now because you can at least hover over them or follow them, otherwise you might have to…
While in town for You Gotta Love Frontend, I was invited to present this talk at the VilniusJS meet-up. There were only a couple designers in the audience, so I did a little on-the-fly reframing — namely to explain the value of a designer on a team. I only went…
I built this for me. An audience of one. A way to keep sharp the skills that I am not always able to use on a project. My requirements were simple: responsive (print, small screens), accessible (beyond screen readers), and kinda fun. Since it relies on a JSON data source…
Many of my clients over the years have relied on fields in tables. Sometimes a checkbox to select a row, sometimes text inputs to update information, sometimes buttons select something. Rarely are they interested in a block of label text above the field, and I cannot disagree with them. The…
Once major browsers started supporting <details> & <summary> developers immediately started to play with them to see what sorts of patterns they could enhance or replace. This is a good thing. Experimentation pushes boundaries, improves understanding. However, we need to be careful of christening this new-to-us interaction as the solution…
Last night I drove up to Toronto, braving concurrent matches from two of their local sporting clubs, parking in oblivion, navigating a maze of progressive rings of fencing, sneaking into the venue via a propped service door, and presented on the role of design in accessibility. It was a code-light…
When a keyboard-only user or screen reader user comes to page that uses CSS to create a layout, there is a chance that what is on the screen does not match the flow of the page. In the posts HTML Source Order vs CSS Display Order and Source Order Matters…
Updated Intro Whether you use a <button> or <input type=”checkbox”> for your toggle depends on a few factors: Use <button> if: you can count on JavaScript being available, flipping the toggle has an immediate effect, the toggle will never have an indeterminate state. Go read Under-Engineered Toggles Too. Use <input…
Direct link in case the embed does not work. I also mentioned some resources at the end of my talk: How to Meet WCAG 2 (Quick Reference) Intopia Launches WCAG 2.1 Map Inclusive Design Principles Inclusive Design posters from Barclays Tweets Some people tweeted about my workshop. I also tweeted…