Skip to content.
Adrian Roselli
Crypto Algorithm Intelligent Agent RTFM

All Posts Tagged:

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

Tag, You’re It

Eric tagged me into this chain letter of a post. From what I can glean, you are supposed to steal the headings and treat them as questions. Why did you start blogging in the first place? Three key reasons: So I wouldn’t have to keep repeating myself; to act as…

Posted:

Tags: internet

CSUNATC 2025 Recap

This post only covers my impressions and experiences from CSUNATC. Others probably had dramatically different experiences. Talk Types The talks seemed to fall into three broad categories this year: product pitches, vendor room sessions (which were product and service pitches), and ‘AI’ talks. Vendor Rooms For the most part, if…

Posted:

Tags: accessibility

Don’t Use Fake Bold or Italic in Social Media

I posted something on Mastodon that uses Unicode math symbols to produce fake bold and fake italic text. I used YayText.com to generate it, but I am not linking it because you I don’t want you to use it. I embedded the post, but you can go to it directly…

Posted:

Tags: accessibility, browser, social media, usability, UX

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

Generic LLM Chatbot Attestation

LLM-powered chatbots are here to stay. As a result, I am playing around with a disclaimer to recommend for clients. After all, if the LLM says that it’s fine to mix chlorine and ammonia to clean the sink, then that chatbot user needs to be told to probably confirm it…

Posted:

Tags: rant, usability

Which VoiceOver?

You may have seen this as a thread on Mastodon (my primary social short-form platform) or on BlueSky. Imagine these as the opening to a series of conversations between a vendor or client or boss or PO or whomever and me. Variations on Real Life Conversations “We like the way…

Posted:

Tags: accessibility, Apple, Safari

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

aria-description Does Not Translate

It does, actually. In Firefox. Sometimes. A major risk of using ARIA to define text content is it typically gets overlooked in translation. Automated translation services often do not capture it. Those who pay for localization services frequently miss content in ARIA attributes when sending text strings to localization vendors.…

Posted:

Tags: accessibility, ARIA, ARIAbuse, Chrome, Edge, Firefox, i18n, L10n, Safari

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

FTC Catches up to #accessiBe

From the FTC on Friday: The Federal Trade Commission will require software provider accessiBe to pay $1 million to settle allegations that it misrepresented the ability of its AI-powered web accessibility tool to make any website compliant with the Web Content Accessibility Guidelines (WCAG) for people with disabilities. FTC Order…

Posted:

Tags: accessibility, law, overlay, WCAG