Articles Tagged

Firefox 146 has shipped the CSS Color 5 version of contrast-color() that only resolves to black or white. Hopefully Chrome support and CSS Color 6 implementation is to follow.…

Why should you use a semantic <button> instead of a generic <div>? Accessibility, right? By how exactly does it help accessibility?

A set of notes taken from Eric Bailey's article about the use of inclusive personas and user research.

The Web Accessibility Initiative (WAI) group has published a working draft of the hugely anticipated WCAG 3.0, and is seeking feedback on it.

…

Short story: Slapping hidden=until-found on an element in HTML enables any hidden content within the element to be findable in the browser with in-page search.

My brain can’t help but try to make connections between seemingly disparate ideas. And that’s what happened yesterday when I read:

• Hidde’s “Can components conform to WCAG?”
• Joas’s “Automating Design Systems”
• Zell’s “We Might Need Something Between Root and Relative

…

Focus trapping is about managing focus within an element, such that focus always stays within it. The whole process sounds simple in theory, but it can quite difficult to build in practice, mostly because of the numerous parts to you got to manage.

The contrast-color() function doesn’t check color contrast, but rather it outright resolves to either black or white (whichever one contrasts the most with your chosen color). Safari Technology Preview recently implemented it and we explore its possible uses in this article.

The reading-flow and reading-order proposed CSS properties are designed to specify the source order of HTML elements in the DOM tree, or in simpler terms, how accessibility tools deduce the order of elements. You’d use them to make the focus order of focusable elements match the visual order, as outlined in the Web Content Accessibility Guidelines (WCAG 2.2).