Skip to content.
Adrian Roselli
Computer Vision Adversarial Character Set genAI

All Posts Tagged: standards

Automated WCAG Testing Is Grrreat!

I’m a big fan of using automation in WCAG testing. I use bookmarklets, dev tools, browser features & reporting, and a pile of third-party products from assorted vendors. These save me time and effort, letting me focus on more tricky cases. But… Unfortunately, the marketing machines of some vendors seem…

Posted:

Tags: accessibility, standards, WCAG

Tweaking Text Level Styles, Reprised

In 2017 I wrote Tweaking Text Level Styles (terrible name in retrospect) and I made regular updates over the years. Stop reading it. Remove it from your bookmarks. Unlink it from your posts. Print it onto paper and then burn it. Demo <mark> <del> <ins> <s> Wrap-up The conclusions and…

Posted:

Tags: accessibility, css, html, pattern, standards, usability, UX

Mainlining Mains

Sometimes you run into a main landmark where you don’t expect one. Like Main Street USA in Hong Kong Disney. So you grab a snack in a diner that serves no hot dogs. You can buy little American flags in the heart of Hong Kong and clothes telling Hong Kong…

Posted:

Tags: accessibility, ARIA, html, standards, usability

Be Wary of Accessibility Guarantees from Anyone

TL;DR: anyone promising you that a total solution to digital accessibility is coming, and they are the ones bringing it, may be lying. Background In 2016 I wrote Be Wary of Accessibility Guarantees from Vendors. At the time I was cautioning readers about libraries and frameworks and SaaS and so…

Posted:

Tags: accessibility, rant, standards, UX

1.4.10: Adversarial Conformance

This post is part of RSS Club, rewarding those who still use RSS to read and/or share content. These posts are embargoed from my regular post feed and the socials for an arbitrary period of time. You can see all the RSS-only posts at AdrianRoselli.com/category/RSS. Tell your friends (to get…

Posted:

Tags: accessibility, rant, standards, WCAG

Don’t Wrap Figure in a Link

In my post Brief Note on Figure and Figcaption Support I demonstrate how, when encountering a figure with a screen reader, you won’t hear everything announced at once: No screen reader combo treats the caption as the accessible name nor accessible description, not even for an image that lacks one.…

Posted:

Tags: accessibility, html, standards

Brief Note on Figure and Figcaption Support

I am not going to dive into the details of <figure> and <figcaption>. Go read Scott’s 2019 post How do you figure? for an overview. That said, since Scott’s post there has been movement on the AAPI mapping (partly by Scott). Specifically, the <figcaption> element should not provide the accName…

Posted:

Tags: accessibility, html, standards

Updated Brief Note on Description List Support

TL;DR: Description list support continues to be generally good (with VoiceOver still the outlier), even if you may not like how it is supported. For background, the <dl> has existed since HTML+, or 1993, when it was called definition list. In December 2022 I wrote Brief Note on Description List…

Posted:

Tags: accessibility, html, standards

Development Advent Calendars for 2024

I got myself a coffee advent calendar and I have to admit it was more aspirational than anything. I don’t drink enough coffee. But the packaging is nice. Web developers around the world have for years given a nod to Saturnalia solstice Isaac Newton’s birthday Yule wassailing mummering end of…

Posted:

Tags: accessibility, css, design, html, internet, standards, UX

Brief Note on Disclosures in Fieldsets

TL;DR: Probably don’t use disclosure widgets in fieldsets. If you do it anyway, don’t put the trigger in the <legend>. Context With <details> / <summary>, recent support for the popover attribute, and the never-ending belief that a “clean” page means hiding content, there is a resurgence in stuffing useful content…

Posted:

Tags: html, standards, usability, UX

Semi-Annual Reminder to Learn and Hire for Web Standards

Alex Russell wrote a four-part series a couple weeks ago arguing that modern JavaScript-first framework-focused front-end development is costing the industry and users. Part of his conclusion for organizations: Never, ever hire for JavaScript framework skills. Instead, interview and hire only for fundamentals like web standards, accessibility, modern CSS, semantic…

Posted:

Tags: ARIA, html, rant, standards, W3C, whatwg

Feedback on a Pagination Pattern

Remy Sharp asked on the Mastodon about pagination as he found it in the W3C Design System: <nav aria-label=”pagination” class=”l-cluster pagination”> <ul class=”pagination__list”> <li><a href=”path/to/page”>Previous <span class=”visuallyhidden”>page</span></a></li> <li><a class=”pagination__list__first” href=”path/to/page”><span class=”visuallyhidden”>page</span> 1<span class=”visuallyhidden”> (first page)</span></a></li> <li><a class=”ellipsis”>…</a></li> <li><a href=”path/to/page”><span class=”visuallyhidden”>page</span> 6</a></li> <li><a href=”path/to/page”><span class=”visuallyhidden”>page</span> 7</a></li> <li><a href=”#” aria-label=”page 8″ aria-current=”page”>8</a></li>…

Posted:

Tags: accessibility, ARIA, html, pattern, standards, usability, UX