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

All Posts Tagged: Firefox

Splitting within Selects

The native HTML <select> is renowned for its styling limitations. Even with control over the closed state and trigger appearance, the options themselves are still defined primarily by the browser and the OS. While I think this is generally fine (preferred, even), the <selectlist> (nee <selectmenu>) hopes to change that.…

Posted:

Tags: accessibility, browser, Chrome, Firefox, html, Safari, standards, usability, whatwg

Browser Video Players Review

Browsers each provide built-in video players for the <video> element. Nearly four years ago Scott Vinkle wrote How accessible is the HTML video player?, where he compared these to one video player product. I decided it was time to test for myself. I structured my test and reporting a bit…

Posted:

Tags: accessibility, browser, Chrome, Firefox, html, mobile, Safari, standards, W3C, whatwg

Brief Note on Super- and Subscript Text

Thanks to a conversation on the A11y Slack, I ran desktop browsers and screen readers through a test to see how they announce content marked up as superscript and subscript. I spun up an old demo from mid-2018 for a quick test: See the Pen HTML Buddies: sub & sup…

Posted:

Tags: accessibility, Firefox, html, JAWS, VoiceOver

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

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

Reference: SRs and Extended Characters

This post serves no purpose other than to demonstrate the fidelity of screen readers when announcing non-emoji Unicode characters when using default settings. There is no judgment on which is correct. This is simply for reference. I grabbed the following tweet and recorded it across common screen readers (WordPress ate…

Posted:

Tags: accessibility, browser, Chrome, Edge, Firefox, Safari

XPath for In-Browser Testing

Both Chrome and Firefox support XPath searches when in the DOM view of their dev tools. Because the browser cleans whatever HTML it encounters (closing tags, correcting nesting), XPath can operate on the code as XML. Simple checks like finding a unique ID value can result in multiple hits in…

Posted:

Tags: browser, Chrome, Firefox, html

WHCM and System Colors

Outline: Feature Queries Proprietary, or Internet Explorer Only Standards Track, or Edge Only Frankenquery’s Monster System Colors CSS2 System Color Keywords WHCM Proprietary Feature Query Color Mappings CSS4 System Color Keywords Browser Support Internet Explorer Legacy Edge (Ledgacy) Chromium Edge (Chromiedge) Firefox Chrome Examples Backgrounds Inline SVGs SVGs via <img>s…

Posted:

Tags: accessibility, browser, Chrome, css, Edge, Firefox, html, Internet Explorer, WHCM

evolt.org Browser Archive 20 Years Old

The Browser Archive home page as captured on 13 October 1999. On August 18, 1999, we at evolt.org launched the Browser Archive. At launch browsers.evolt.org contained 80 different browsers. It started with my personal testing suite built up from 1996, and just kind of went from there. Those links point…

Posted:

Tags: browser, Firefox, Internet Explorer, Netscape, Opera

Group Labels Do Not Guarantee… Uniquity?

Heading this off early: uniquity uniq·​ui·​ty; \ yüˈnikwətē, -wətē, -i \Uniqueness; quality of being unique. There is a place where accessibility practitioners hang out and try to out-do each other with niche knowledge of nuance. While loitering in one, a question came up about text fields that have the same…

Posted:

Tags: accessibility, browser, Chrome, Edge, Firefox, Internet Explorer, Safari, usability, UX

Stepping Back from the Edge

Due to lack of overwhelming request, you can download this logo (SVG). By now it is old news, in Internet time, that Microsoft Edge will replace its rendering engine with Chromium. Nearly six years ago I wrote about Opera dumping Presto to move to Chromium. The landscape is slightly different…

Posted:

Tags: browser, Chrome, Edge, Firefox, Microsoft, standards, W3C, whatwg

Display: Contents Is Not a CSS Reset

CSS resets are a collection of CSS styles that undo the default browser styling of many or most HTML elements. Recently I have seen cases of developers using display: contents on lists and headings to remove the margins and padding, and generally to visually do what a CSS reset might…

Posted:

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