Skip to content.
Adrian Roselli
SaaS Funded Library CLI

All Posts Tagged: browser

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

CSS Logical Properties

I have often remarked that my blog is little more than a place for me to offload my memory. I need not remember the syntax, logic, test results, etc. of every control, widget, style, browser, and so on. I can just write a post and refer to it later. This…

Posted:

Tags: browser, css, design, i18n, L10n, standards

Stop Giving Control Hints to Screen Readers

TL;DR: for standard HTML controls and standard ARIA patterns (widgets), you do not need to add instructions for screen readers on how to use them nor what they are. When a screen reader encounters an element on the page that invites interaction beyond reading, it typically provides users with instructions…

Posted:

Tags: accessibility, ARIA, ARIAbuse, browser, html, standards, WCAG

Smashing / Web We Want Video Pitch

At Smashing Conference in New York on Tuesday, October 15, Microsoft is hosting a lunch session as part of its The Web We Want initiative. Developers are pitching their wants. I was invited to pitch my request, but since I will not be at the conference I was asked for…

Posted:

Tags: accessibility, browser, slides, standards, WAI, WCAG

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

Maybe Ignore type=search

Another case of the headline saying it all. If you have a valid, accessible search field (with a useful, sensible label) then you can probably ignore type=”search” and use type=”text” instead. I made a code sample you can use for testing in your preferred set-up; it is what I used…

Posted:

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

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

Web Turns 30, Seems Popular

The world wide web has officially lasted 30 consecutive years, which means it’s catching up to its parent, the Internet, which itself is bearing down on 50. That’s an important distinction. The Internet is not the web; it is the foundation on which the web was born. In honor of…

Posted:

Tags: browser, html, internet, W3C

Avoid Default Field Validation

HTML5 gives us form field validation for free. The problem is that the default messages browsers provide are not always useful and typically do not work with assistive technology. I made an example on CodePen that uses an email field (type=”email”), is required (required), and uses a pattern to restrict…

Posted:

Tags: accessibility, browser, html, pattern, usability, UX

Baseline Rules for Scrollbar Usability

Web Content Accessibility Guidelines Inclusive Design Principles Manage Expectations Wrap-up CSS Scrollbar Module (added 10 December 2021) Now that one of the most popular CSS resource sites on the innertubes has implemented styled scrollbars in the browser I think the time is right (or too late?) for me to try…

Posted:

Tags: accessibility, browser, css, usability

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

Variable Fonts and Dyslexia

Dyslexia is not a black or white, on or off condition. Some with dyslexia report different challenges than others, ranging from typefaces to page layout to other factors. A few years ago I wrote Typefaces for Dyslexia, where I gathered some research suggesting that dedicated typefaces, on the whole, do…

Posted:

Tags: accessibility, browser, fonts, standards, usability, UX