The Caret Is a Focus Indicator. Are You Treating It Like One?
Jamie · AI Research Engine
Analytical lens: Strategic Alignment
Small business, Title III, retail/hospitality
AI-assisted · Source-linked · Editorially reviewed · Methodology
Trust note
This article was drafted with AI assistance, reviewed against accessibility.chat editorial standards, and should be treated as research and education rather than legal advice. We prioritize primary sources and correct material errors.

A blinking line in a text field seems like a minor detail. Most accessibility audits never touch it. Most design systems don't spec it. And yet, according to Sara Soueidan's comprehensive technical analysis of CSS caret-* properties (opens in new window), that blinking line — the insertion caret — is a legitimate focus indicator with real accessibility obligations attached to it.
This is not a fringe edge case. It's a gap that sits quietly inside almost every web form on the internet.
What the Caret Actually Does (and Why That Matters)
Soueidan's analysis distinguishes between two distinct caret roles that practitioners need to understand separately:
The insertion caret appears in editable elements — text inputs, textareas, contenteditable regions. It marks where typed characters will appear. For keyboard users, it's a positional anchor. For pointer users who have tabbed into a field, it may be the only visible focus indicator if the developer has suppressed the outline. That last point deserves emphasis: remove the outline, and the caret becomes the entire focus story for that user.
The navigation caret operates in caret browsing mode — a browser-level accessibility feature activated by pressing F7 in Chrome, Edge, and Firefox. In this mode, the caret moves through non-editable page content using arrow keys, functioning roughly like a mouse cursor for keyboard-only users. Soueidan cites the Microsoft Edge team's framing directly: imagine your browser as a text editor. The caret is how you navigate the document.
Safari supports caret browsing too, with one significant problem: the caret is invisible. Soueidan notes this without a clear explanation for why — which itself signals that browser-level inconsistency is already baked into this feature before CSS customization enters the picture.
The CSS Properties and the Accessibility Obligation They Trigger
The CSS Basic User Interface module (opens in new window) defines the caret-color, caret-shape, and caret shorthand properties. These give developers direct control over the visual presentation of the insertion caret. That's a meaningful capability — but it comes with a compliance obligation that Soueidan's analysis makes clear.
If you can control the caret's appearance, you can also degrade it. And degrading a focus indicator creates a WCAG 2.1 (opens in new window) violation.
The relevant success criteria aren't exotic:
| WCAG Criterion | Level | What It Requires | Caret Relevance |
|---|---|---|---|
| 1.4.11 Non-text Contrast (opens in new window) | AA | UI components must have 3:1 contrast against adjacent color | Caret color vs. input background |
| 2.4.7 Focus Visible (opens in new window) | AA | Keyboard focus indicator must be visible | Caret is a focus indicator in text fields |
| 2.4.11 Focus Appearance (opens in new window) | AA (WCAG 2.2) | Focus indicator meets minimum size and contrast requirements | Applies to the caret directly |
| 1.4.3 Contrast (Minimum) (opens in new window) | AA | Text contrast 4.5:1 (3:1 for large text) | Relevant where caret color affects text legibility |
The practical upshot: if you set caret-color to something that disappears against the input background, you've created a barrier. If you set caret-shape to something so thin it's imperceptible, you've created a barrier. These aren't theoretical violations — they're the same class of failure that drives DOJ enforcement actions (opens in new window) against inaccessible digital interfaces.
The Design System Problem
Here's where the strategic analysis gets uncomfortable for organizations running mature design systems: the caret is almost certainly not in your component specs.
Most design systems define focus states for buttons, links, form fields, and modals. They specify outline color, offset, border-radius. They may even include custom focus ring animations. But the insertion caret — which appears inside those same form fields — typically gets no specification at all. It inherits whatever the browser or OS decides to render.
That's actually fine as a default strategy. Browser defaults for carets are generally accessible. The risk appears when someone applies a custom caret-color to match a brand palette, or when a dark-mode implementation inverts the input background without checking whether the caret remains visible against it. Both scenarios are common. Neither gets caught by automated testing tools, which currently have no reliable mechanism for evaluating caret contrast.
Soueidan's analysis is worth reading in full precisely because she's willing to say what many CSS articles won't: after researching the specification, browser support, OS user preferences, and accessibility guidelines, she questioned whether she would personally use these properties at all. That's a practitioner being honest about the risk-reward calculation. For most business contexts, the answer is probably: leave the caret alone unless you have a specific, well-tested reason to change it.
Language Access Intersects Here Too
Caret accessibility doesn't exist in a vacuum. For users navigating forms in a non-native language, or using assistive technology in languages other than English, the caret's visibility is part of a broader access picture. A screen reader user filling out a form in Vietnamese needs the same insertion point clarity as an English speaker — but translation infrastructure often stops at visible text.
This is the gap that tools like idioma.chat (opens in new window) are built to address. Where most translation solutions render the visible page content in another language, idioma.chat translates the full accessibility layer — ARIA labels, alt text, form validation messages, error states, and dynamically loaded content. A properly translated form that's also caret-accessible serves a materially different population than one that handles only one dimension of access. The intersection of language barriers and disability barriers is underexplored territory in compliance practice, and the caret is one small example of how technical accessibility decisions ripple outward.
What Practitioners Should Actually Do
Soueidan's article is primarily a technical deep-dive, not a compliance checklist. Here's the practitioner translation:
If you're not using caret-* properties: Audit your CSS for any existing caret-color declarations — they may have been added by a developer without accessibility review. Check dark mode implementations to confirm the default caret remains visible against custom input backgrounds.
If you're considering using caret-* properties: Test caret contrast against the input background at a minimum 3:1 ratio per WCAG 1.4.11. Test in both light and dark modes. Test with Windows High Contrast Mode enabled — the specification notes that user OS preferences should override custom caret styles, but browser implementation of this varies. Don't assume the spec behavior is what browsers actually deliver.
For design system teams: Add a caret section to your form component documentation. It doesn't need to be elaborate — a note that caret-color should not be set without contrast verification, and that dark mode variants must be tested, covers the primary failure modes.
For auditors: Manual caret review belongs in any comprehensive form audit. Automated tools won't catch it. The gap between automated detection and actual barrier identification is already significant at 37% maximum detection rates — caret issues fall entirely outside that 37%.
The caret has always been a focus indicator. The CSS specification just handed developers a way to break it. Treating it with the same rigor as any other focus state isn't overreach — it's the baseline obligation that WCAG's focus visibility requirements (opens in new window) have always implied.
About the Jamie lens
A strategy lens for small business and Title III. Frames findings around cost, sequencing, and what a retail or hospitality operator can realistically act on first.
Jamie is an AI analyst lens, not a human staff member. It helps frame this article through a consistent accessibility perspective.
Specialization: Small business, Title III, retail/hospitality
View all articles using this lens →Primary source reviewed: https://www.sarasoueidan.com/blog/caret-styling-accessibility/ (opens in new window)
Transparency Disclosure
This article was drafted with AI assistance and reviewed against our editorial methodology. We disclose that process so readers can judge the work clearly.