As of my 28 January 2024 update at the end of this post, aria-label auto-translation support is seemingly as spotty as when I first wrote this post. It does, actually. Sometimes. One of the big risks of using ARIA to define text content is that it often gets overlooked in…
Since the early days of the web, when images could be floated and text would wrap around them, designers have wanted to bring drop caps onto the web. Then we learned how terrible a pattern like <img alt=”M” align=”left”>atthew is for users, and CSS introduced :first-letter, letting us believe all…
TL;DR: for standard HTML controls and standard ARIA patterns (widgets), you do not need to add instructions for screen readers on how to use them nor what they are. When a screen reader encounters an element on the page that invites interaction beyond reading, it typically provides users with instructions…
Another case of the headline saying it all. If you have a valid, accessible search field (with a useful, sensible label) then you can probably ignore type=”search” and use type=”text” instead. I made a code sample you can use for testing in your preferred set-up; it is what I used…
Early in 2017 I filed an issue against WAI-ARIA Authoring Practices (APG) requesting a change to the menu navigation pattern. Despite a great deal of feedback in agreement, it languished. In late 2017 I wrote Don’t Use ARIA Menu Roles for Site Nav and started actively campaigning against the APG…
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…
WordCamp Europe has wrapped up in Belgrade. I presented a (not quite) three hour workshop on accessibility, specifically designed to be computer-free. I may have re-used a few slides from my presentation at last year’s WordCamp, but overall this is new material with some WCAG 2.1 references thrown in for…
If the embed below does not work, view the slides directly at SlideShare. I also collected tweets all about me… Kicking off day two of the Guelph Accessibility Conference. #AccessConf2018 pic.twitter.com/qXpTfjmOKt Adrian Roselli (@aardrian) May 30, 2018 Everything I know about accessibility I learned from stack overflow. With such a…
Related Other posts in this accidental series: Layout as a Clue to Semantics Display: Contents Is Not a CSS Reset Tables, JSON, CSS, ARIA, RWD, TLAs… Tables, CSS Display Properties, and ARIA A Responsive Accessible Table Hey, It’s Still OK to Use Tables When I presented my talk CSS Display…
Related Other posts in this accidental series: Display: Contents Is Not a CSS Reset Tables, JSON, CSS, ARIA, RWD, TLAs… Tables, CSS Display Properties, and ARIA A Responsive Accessible Table Hey, It’s Still OK to Use Tables I did not mean to write a series on tables. It’s not a…
About an hour ago I wrapped up my talk to Portland Accessibility and User Experience Meetup. I have posted the slides to SlideShare and embedded them below. I understand there may be a transcript available later. When I know, I will link it.