While web developers tend to focus on JavaScript and CSS, none of what we do would be possible without HTML acting as the foundation. It has long seemed like HTML wasn't evolving, but things may be changing. New elements like <selectlist> are on the horizon, cool new features like popovers, and a swath of related browser APIs (Web Components, PWAs, etc.).

Starfield has a lot of computers to interact with: Ship controls, desktop terminals, and information kiosks. And they all have accessibility problems.

In late August, Meta released the full web experience for the Threads app. The previous web version was read-only. In this article, I will take another look and see if there are interesting things that I found along the way.

Custom properties - aka “CSS variables” - seem fairly straightforward. However, there are some behaviors to be aware of regarding how the browser computes the final values. A misunderstanding of this process may lead to an unexpected or missing value and difficulty troubleshooting and resolving the issue.

TL;DR Browsers kind of expand the tap target of elements and try to find the element the user intended to click. It works slightly differently in each browser, but the end result is roughly the same: Browsers assist users who are unable to click perfectly given the combination of their circumstances and abilities.