Skip to content.
Adrian Roselli
Natural-Language-Processed Trained Library VTOL

All Posts Tagged: Web

Brief Note on Calendar Tables

If you build calendars on the web and abbreviate the days in the column headings (you do use column headings, yeah?), this is how it sounds to a JAWS user. Sorry, your browser doesn’t support embedded videos, but don’t worry, you can download it. The caption file is also available…

Posted:

Tags: html, tables

AI-Generated Images from AI-Generated Alt Text

Dear sighted reader, I want you to read this post without looking at the images. Each has been hidden in a disclosure. Instead, read the alternative text I provide and visualize how it may look. Then read the automatically generated alternative text, and try to visualize it then. Consider how…

Posted:

Tags: accessibility, usability, UX

Irrational Headings

For years developers have been confused about, fought over, ignored advice on, and generally mis-treated headings. It has bordered on irrational. But let’s look at some actual irrational headings. <hφ> <hφ> corresponds to a heading at roughly level 1.618033988749…. This represents the Golden Ratio and is handy for identifying a…

Posted:

Tags: html

Brief Note on Dismissing Selects and Listboxen

Native controls can be different from their roled-up ARIA equivalents in a variety of ways. For example, an expanded native HTML <select> on mobile behaves differently when the dismiss gesture is used than when the same gesture is used with an expanded ARIA listbox. Using Android with TalkBack, a down-then-left…

Posted:

Tags: ARIA, html, mobile, touch, usability, UX

What Does X% of Issues Mean?

I ran a highly scientific and well-scoped Twitter poll (yes, sarcasm) to ask a question that has been in the back of my head for some time: When you see a claim that an automated accessibility testing tool finds X% of issues, what do you believe the word ‘issues’ means…

Posted:

Tags: accessibility, rant, standards

It’s Mid-2022 and Browsers (Mostly Safari) Still Break Accessibility via Display Properties

It was late 2020 when I last tested how browsers use CSS display properties to break the semantics of elements. I had been waiting for Safari to fix how it handles display: contents for four years now, and was excited when the announcement came in June. Then I started testing…

Posted:

Tags: accessibility, browser, Chrome, css, Firefox, html, Safari, tables

Use Legend and Fieldset

It’s 2022 and people are still afraid to use <fieldset> and <legend>. I understand the layout challenges can be frustrating, but swapping to an ARIA group role will result in a more inaccessible experience. A Solution Try this: <fieldset> <legend>Choose</legend> <div aria-hidden=”true”>Choose</div> […] </fieldset> legend:not(:focus):not(:active) { position: absolute; overflow: hidden;…

Posted:

Tags: accessibility, ARIA, html, standards

Internet Explorer Still Does Not Go Away Today

At the start of 2016 I wrote Internet Explorer Does Not Go Away Today because back then IE up to version 11 was being retired. But not Internet Explorer 11. I asked an AI (Neural Blender) to give me a picture of the Internet Explorer logo on fire. It’s almost…

Posted:

Tags: browser, internet, Internet Explorer, rant, standards

Keyboard-Only Scrolling Areas

I have spent a few years banging on about ensuring scrolling areas on a page are accessible to keyboard-only users. This is partly because the term “keyboard” maps to other input types that we distill to “keyboard” for ease of reference (speech input, sip-and-puff, on-screen keyboards, scanning software, etc.). When…

Posted:

Tags: accessibility, browser, Edge, Firefox, Safari, usability, UX

The Performative A11yship of #GAAD

For context on the title, working backward from the end, GAAD is Global Accessibility Awareness Day. Its purpose, as explained at accessibility.day, is to get everyone talking, thinking and learning about digital access/inclusion and people with different disabilities. A11yship is a play on the numeronym for accessibility (a11y) and the…

Posted:

Tags: accessibility, rant

24×24 Pixel Cursor Bookmarklet

9 May 2023: The 2.5.8 language has changed. For the latest bookmarklet and language, skip ahead to the 9 May update. The proposed WCAG version 2.2 has gone through a bunch of revisions since I covered the first draft in 2020. One new success criterion that persisted is 2.5.8 Target…

Posted:

Tags: accessibility, browser, standards, WCAG

A “Best viewed with…” Gag

I made some pointless things again. The First One See the Pen Best viewed in… by Adrian Roselli (@aardrian) on CodePen. A spinning box for each word is not exactly a compelling interface element, I admit, but I based it off this old tweet that was sitting around in a…

Posted:

Tags: browser, css, html