Skip to content.
Adrian Roselli
Decentralized Non-Fungible System BYOB

All Posts Tagged:

WCAG 2.1 Is the Current Standard, Not WCAG 2.0 — and WCAG 2.2 Is Coming

The title kind of says it all. WCAG 2.1 has been the standard for over two years — it was published in June 2018. If you rewind to when the Accessibility Guidelines Working Group (AGWG) was asking for feedback on its near-final 2.1 draft, many of the Success Criteria in…

Posted:

Tags: accessibility, rant, WCAG

Speech Viewer Logs of Lies

The headline is intentional hyperbole, chosen mostly for the sloppy alliteration. When sighted users test with a screen reader it is common to rely on the visual output — checking to see where focus goes, confirming that controls behave, watching the spoken output in a text log. The problem is…

Posted:

Tags: accessibility, usability, UX

Be Wary of doc-subtitle

In early March, Steve Faulkner shared this nugget for making sub-headings: 👉If you want to semantically identify a heading subtitle, look no further than role="doc-subtitle" w3.org/TR/dpub-aria-1.0/#doc-subtitle #HTML #ARIA #WebDev pic.twitter.com/uaHcVRp6oz Steve Faulkner (@stevefaulkner) March 7, 2020 On its surface it looks pretty handy. Handy enough that Chris Ferdinandi wrote about…

Posted:

Tags: accessibility, ARIA, browser, html, pattern, rant, standards

What’s New in WCAG 2.2

The latest (and probably last) WCAG version 2 point release is in draft and the W3C is asking for comments and feedback by 18 September 2020 either via GitHub or via email. The new success criteria address cognitive and learning disabilities, mobile devices, and ebooks. Read more details in the…

Posted:

Tags: accessibility, standards, W3C, WAI, WCAG

Source Order Viewer in Canary

Don’t tell anyone. This may be a secret. But I am really excited, as no person should ever be over something this mundane. Check this out (and then read on for what is happening here): The alt text gives it away, but look in the lower right corner. In the…

Posted:

Tags: accessibility, browser, Chrome, Edge, whatwg

30 Years of the Americans with Disabilities Act

Today is the 30th anniversary of the Americans with Disabilities Act of 1990 (ADA). Thirty years is not very long when you consider Americans elected (largely unknowingly) a disabled president in 1932. On the other hand, it seems an eternity ago given Americans elected a president who mocks disabled people…

Posted:

Tags: accessibility, law

My Gratuitously Signaling Watch

In early 2016 I bought myself the Eone Bradley (nobody is sponsoring this post and the link is not an affiliate link). I first saw this watch at the CSUN Assistive Technology Conference, some on the wrists of people with little or no vision, and had admired it since then.…

Posted:

Tags: accessibility, design, usability

ARIA Grid As an Anti-Pattern

First I will cover what an ARIA grid is per the ARIA specification, and then I will discuss two patterns proposed by the ARIA Authoring Practices. ARIA 1.1 Data Grids Layout Grids As Defined The Provided Examples 1. Simple List of Links 2. Pill List For a List of Message…

Posted:

Tags: accessibility, ARIA, ARIAbuse, rant, standards, UX

#accessiBe Will Get You Sued

Disclaimer: This post and the headline is my opinion. I provide facts throughout to inform that opinion. I say this because accessiBe managed to get $40 million in two rounds of funding from K1 Capital and I am guessing some of that money will be allocated to attorney fees. I…

Posted:

Tags: accessibility, overlay, rant, standards, UX

How Not to Deploy a Twitter Feature

Twitter announces a new feature is rolling out for iOS, the ability to record audio tweets. It demonstrates this with an uncaptioned video of its Twitter avatar making bird noises: Tweets with audio are rolling out on iOS and we only have one thing to say about it pic.twitter.com/CZvQC1fo1W Twitter…

Posted:

Tags: accessibility, rant, Twitter, UX

Disclosure Widgets

A disclosure widget is a simple control whose sole purpose is to hide or show stuff. Native HTML has one built in via the <details> and <summary> elements. Until recently, if you wanted to use it in modern browsers you needed to use a polyfill. In most cases it was…

Posted:

Tags: accessibility, ARIA, html, pattern, standards

Avoid aria-roledescription

HTML has all sorts of built-in features that, when used correctly, are accessible, will localize, and which just work. For example, if I want a button, I use <button>, and a screen reader will announce it as button. For users in other languages, they will hear whatever is their word…

Posted:

Tags: accessibility, ARIA, ARIAbuse, browser, rant, standards, UX