Should CSS Override Default Browser Styles?

The Default-Style Debate Has No Clean Boundary

Almost every native interface element a browser renders—checkboxes, radio buttons, select menus, scrollbars, links, buttons—can be restyled with CSS. You can change the cursor, the text-selection highlight, the accent color, and eventually even the look of spelling and grammar errors in editable text.

The technical ability to override all of these is not in question. The recurring argument is about where to stop: the operating system's defaults are familiar, predictable, and often tuned for accessibility. A default checkbox on a user's OS behaves and looks the way that user expects. The same argument applies to select menus, scrollbars, and underlined blue links.

Everyone Draws the Line in a Different Place

In practice, there is no consensus on which defaults are sacred. Nearly every site styles its buttons and links, but even then the degree varies—some teams only alter the link hue while keeping the underline, while others go much further. Styling form controls like checkboxes and selects is common, but plenty of developers refuse to touch them.

The same split appears with cursors. Some developers never change the default cursor, some use a pointer only on interactive elements they have created, and some are comfortable with entirely custom cursor images. Scrollbars produce similar disagreements: a strict camp says they should remain untouched, while others build elaborate custom scrollbar designs.

The Practical Line Is About Choices, Not Bans

CSS exists precisely to change the design of websites, and nearly any ruleset you write overrides some default. The boundary between acceptable and unacceptable styling is fuzzy by nature. There is no single property or element that is inherently wrong to override.

What matters is the choice behind the override. Styling an element becomes a problem only when the result is no longer usable or accessible. A background-color value can make a site impossible to read or navigate, yet nobody calls for banning that property outright. The same logic applies to custom checkboxes, styled scrollbars, and any other default you override: judge the outcome, not the act.