Accent all areas
Tags: css, accentcolor, styling, forms
Published: 2021-11-07 07:46:56

---
title: Accent all areas
published: true
date: 2021-09-09 14:42:45 UTC
tags: css,accentcolor,styling,forms
canonical_url: https://adactio.com/journal/18442
---

Whenever a new version of Chrome comes out, there’s an accompanying blog post listing what’s new. Chrome 93 just came out and, sure enough, [Pete has written a blog post about it](https://developer.chrome.com/blog/new-in-chrome-93/).

But what I think is the most exciting addition to the browser isn’t listed.

What is this feature that’s got me so excited?

Okay, I’ve probably oversold it now because actually, it looks like a rather small trivial addition. It’s [the `accent-color` property in CSS](https://www.w3.org/TR/css-ui-4/#widget-accent).

Up until now, accent colour was controlled by the operating system. If you’re on a Mac, go to “System Preferences” and then “General”. There you’ll see an option to change your accent colour. Try picking a different colour. You’ll see that change cascade down into the other form fields in that preference pane: checkboxes, radio buttons, and dropdowns.

Your choice will also cascade down into web pages. Any web page that uses native checkboxes, radio buttons and other interface elements will inherit that colour.

This is how interface elements are supposed to work. The browser inherits the look’n’feel of the inputs from the operating system.

That’s the theory anyway. In practice, form elements—such as dropdowns—can look different from browser to browser, something that shouldn’t be happening if the browsers are all inheriting from the operating system.

Anyway, it’s probably this supposed separation of responsibility between browser and operating system which has led to the current situation with form fields and CSS. Authors can style form fields up to a point, but there’s always a line that you don’t get to cross.

The accent colour of a selected radio button or a checkbox has historically been on the other side of that line. You either had to accept that you couldn’t change the colour, or you had to make your own checkbox or radio button interface. You could use CSS to hide the native element and replace it with an image instead.

That feels a bit over-engineered and frankly kind of hacky. It reminds me of the bad old days of image replacement for text before we had web fonts.

Now, with [the `accent-color` property in CSS](https://web.dev/accent-color/), authors can over-ride the choice that the user has set at the operating system level.

On the one hand, this doesn’t feel great to me. Who are we to make that decision? Shouldn’t the user’s choice take primacy over our choices?

But then again, where do we draw the line? We’re allowed over-ride link colours. We’re allowed over-ride font choices.

Ultimately I think it’s a good thing that authors can now specify an accent colour. What makes me think that is the behaviour that authors have shown if they _don’t_ have this ability—they do it anyway, and in a hackier manner. This is why I think the work of [the Open UI group](https://open-ui.org/) is so important. If developers don’t get a standardised way to customise native form controls, they’ll just recreate their own over-engineered versions.

> The purpose of Open UI to the web platform is to allow web developers to style and extend built-in web UI controls, such as `select` dropdowns, checkboxes, radio buttons, and date/color pickers.

Trying to stop developers from styling checkboxes and radio buttons is like trying to stop teenagers from having sex. You might as well accept that it’s going to happen and give them contraception so they can at least do it safely.

So I welcome this new CSS condom.

You can [see `accent-color` in action in this demo](https://codepen.io/web-dot-dev/pen/PomBZdy). Change the value of the `accent-color` property to see the form fields update:

```
:root {
  accent-color: rebeccapurple;
}

```

Applying it at the document level like that will make it universal, but you can also use the property on an element-by-element basis using whatever selector you want.

That demo works in Chrome and Edge 93, the current release. It also works in Firefox 92, which literally just landed (like _as_ I was writing this blog post, support for `accent-color` magically arrived!).

As for Safari, well, [who knows](https://webkit.org/status/#?search=accent-color)? If Apple published a roadmap, then developers would have a clue when to expect a property like this to land. But we mere mortals cannot be trusted with such important hush-hush information.

In the meantime, keep an eye on [Can I Use](https://caniuse.com/mdn-css_properties_accent-color). And lack of support on one browser is no reason not to use `accent-color` anyway. It’s a progressive enhancement. Add it to your CSS today and it will work in more browsers in the future.