# Tailwind's rem-Based Breakpoints and Their Accessibility Tradeoffs

DevFeed: [Tailwind's rem-Based Breakpoints and Their Accessibility Tradeoffs](<https://devfeed.tech/articles/can-we-make-default-tailwind-a-more-accessible-choice-33293.md>)

Original publisher: [Read original article](<https://freek.dev/3179-can-we-make-default-tailwind-a-more-accessible-choice>)

Author: Freek Van der Herten (freek@spatie.be)

Published: 2026-08-14T10:30:33Z

Content type: article

Language: en

Sources: [freek.dev - all blogposts](<https://devfeed.tech/sources/freek-dev-all-blogposts.md>)

Topics: [Tailwind CSS](<https://devfeed.tech/topics/tailwind.md>), [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [responsive](<https://devfeed.tech/tags/responsive.md>), [tailwind](<https://devfeed.tech/tags/tailwind.md>)

## AI overview

This article examines Tailwind's default rem-based breakpoints and their accessibility tradeoffs. Browser font-size preferences can shift layouts, which may help some users, while px breakpoints remain a defensible choice.

## Source excerpt

A sharp look at Tailwind's default rem-based breakpoints, and the accessibility tradeoff they make. It explains how browser font-size preferences can shift layouts, why that can help some users, and why px breakpoints are still a defensible choice. Read more