Skip to content.
Adrian Roselli
Deep Learning Un/Inert Library CRT

All Posts Tagged: browser

Source Order Viewer in Edge 86

Update, 15 September 2020: Microsoft put together a more formal announcement at Introducing Source Order Viewer in the Microsoft Edge DevTools. It has some video examples and instructions to enable it. Edge 86 has introduced a feature that shows the source order of a page. You can read more about…

Posted:

Tags: accessibility, browser, css, Edge

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

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

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