Skip to content.
Adrian Roselli
Quick-Charge Funded Model MVP

All Posts Tagged: html

Disclosure Widgets

A disclosure widget is a simple control whose sole purpose is to hide or show stuff. Native HTML has one built in via the <details> and <summary> elements. Until recently, if you wanted to use it in modern browsers you needed to use a polyfill. In most cases it was…

Posted:

Tags: accessibility, ARIA, html, pattern, standards

Chrome 80/81 Bug: Accessible Name Calculation

The good:Chrome 80 rolled out on 19 February 2020, and with it came a pile of fixes for how elements with CSS display properties have their semantics exposed in the accessibility tree. These huge accessibility bug fixes featured prominently in my CSUN talk this year (starting at slide 36). The…

Posted:

Tags: accessibility, Chrome, html

CSUN 2020: CSS Display Properties versus HTML Semantics

While originally I was scheduled to attend CSUN to present two talks one talk, I ended up not attending (my father won A Major Award so I joined him instead). I gave my talk remotely in my scheduled slot (during my father’s award dinner). While I would have loved to…

Posted:

Tags: accessibility, ARIA, css, html, slides, standards

Stop Using ‘Drop-down’

TL;DR: Stop using the word drop-down. Instead choose a term that accurately describes the control you want. I have worked both with native platform developers and web developers. While control names might differ, if a control was functionally the same then it was not an issue. A TextBox, for example,…

Posted:

Tags: html, lingo, pattern, standards

Block Links, Cards, Clickable Regions, Rows, Etc.

Whether you call them cards, block links, or some other thing, the construct of making an area of content clickable (tappable, Enter-key-able, voice-activatable, etc.) is not new. While hit area size is mostly a usability issue, marketers often want a larger click area around their calls to action (CTAs) to…

Posted:

Tags: accessibility, css, design, html, pattern, tables, usability, UX

Link Targets and 3.2.5

TL;DR: Regardless of what accessibility conformance level you target, do not arbitrarily open links in a new window or tab. If you are required to do so anyway, inform users in visible text. Overview Throughout this post I am going to use the terms browser window and tab interchangeably. While…

Posted:

Tags: accessibility, html, usability, UX, WCAG

Fixed Table Headers

Related Under-Engineered Responsive Tables A Responsive Accessible Table Hey, It’s Still OK to Use Tables Keyboard and Overflow

Posted:

Tags: accessibility, css, html, mobile, pattern, tables

Showing File Types in Links

Links to files can be a surprise for users, especially those who cannot use, do not notice, or do not have the status bar to show a link destination. Some users may appreciate knowing a link points to a file, sometimes even a particular file. For links with the download…

Posted:

Tags: css, html, usability, UX

Web Development Advent Calendars for 2019

Web developers around the world have celebrated Saturnalia solstice Isaac Newton’s birthday Christmas with advent calendars covering web-related topics. As a result, you may recognize some of the ones listed below. Every year I miss a few on day one, so add a comment or tweet me if you have…

Posted:

Tags: accessibility, css, design, html, internet, standards, UX

Accessible Drop Caps

Since the early days of the web, when images could be floated and text would wrap around them, designers have wanted to bring drop caps onto the web. Then we learned how terrible a pattern like <img alt=”M” align=”left”>atthew is for users, and CSS introduced :first-letter, letting us believe all…

Posted:

Tags: accessibility, ARIA, css, design, html, pattern, usability, UX, WCAG

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

An HTML Element Potentially Worth $18M to Indiegogo Campaigns

The title of this post is a play on Jason Grigsby’s recent post An HTML attribute potentially worth $4.4M to Chipotle. In it he asks: How many other people have failed to finish an order because the form doesn’t support autofill and the error messages aren’t helpful? An HTML attribute…

Posted:

Tags: accessibility, html, standards, usability, UX, WCAG