Variantes focus y focus-visible
Aplique estilos focus:* para la navegación con teclado y focus-visible:* para mostrar anillos de foco únicamente a usuarios de teclado, no al hacer clic con el ratón.
Variantes focus y focus-visible es una lección gratuita de Tailwind CSS Academy en CoddyKit. Esta es la lección 2 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Tailwind CSS Academy, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Tailwind CSS Academy incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
The Importance of Focus Styles
Keyboard navigation is used by people with motor disabilities, power users, and anyone filling out a long form. When an element is focused via keyboard, the browser highlights it with a focus indicator. CSS's :focus pseudo-class triggers on any focus event, while :focus-visible triggers only when the browser determines a visible focus indicator is helpful — typically keyboard navigation. Tailwind provides both as focus: and focus-visible: variant prefixes.
<!-- focus-visible is the accessible modern choice -->
<div class="flex gap-4">
<button class="bg-blue-500 text-white px-4 py-2 rounded focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:ring-offset-2">
Tab to me
</button>
</div>focus: Variant Basics
The focus: variant applies a style whenever the element receives focus, regardless of how — mouse click, touch, or keyboard. The most common use is removing the browser's default focus outline and replacing it with a custom ring: focus:outline-none focus:ring-2 focus:ring-blue-500. While convenient, this pattern has a downside: mouse users see the ring on click too, which some designers consider visually intrusive.
<!-- focus: fires on both mouse click and keyboard tab -->
<div class="space-y-3 max-w-sm">
<input
type="text"
placeholder="Click or tab to focus"
class="w-full border border-gray-300 rounded-lg px-4 py-2 focus:outline-none focus:ring-2 focus:ring-blue-500 focus:border-blue-500"
/>
<button class="w-full bg-gray-200 py-2 rounded-lg focus:outline-none focus:ring-2 focus:ring-gray-500">
Focus-on-click-too button
</button>
</div>focus-visible: The Modern Approach
focus-visible: maps to the CSS :focus-visible pseudo-class. Browsers apply this only when they determine that showing a focus indicator is appropriate — which means keyboard navigation but typically not mouse clicks on buttons. This gives you the best of both worlds: mouse users do not see the ring, but keyboard users always get clear feedback. This is the recommended approach in all modern Tailwind projects.
<!-- focus-visible: only shows ring for keyboard, not mouse -->
<div class="space-y-3 max-w-sm">
<!-- Try: click with mouse (no ring) vs Tab key (ring appears) -->
<button class="w-full bg-blue-500 text-white py-2 rounded-lg focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:ring-offset-2">
Smart focus (use Tab key)
</button>
<input
type="text"
placeholder="Input: ring on keyboard focus"
class="w-full border border-gray-300 rounded-lg px-4 py-2 focus:outline-none focus-visible:ring-2 focus-visible:ring-indigo-500"
/>
</div>Custom Focus Color Conventions
Choose focus ring colors that contrast with both the element and the page background. Brand color rings work well: focus-visible:ring-indigo-500 for an indigo-branded product. Error state focus can use focus:ring-red-500 on invalid inputs. Dark mode requires considering whether your ring color has enough contrast against dark backgrounds — light rings (ring-white or ring-blue-300) work better on dark surfaces.
<!-- Focus colors for different contexts -->
<div class="space-y-4 max-w-sm">
<!-- Normal: brand color ring -->
<input class="w-full border rounded px-3 py-2 focus:outline-none focus:ring-2 focus:ring-indigo-500" placeholder="Brand focus" />
<!-- Success: green ring -->
<input class="w-full border border-green-300 rounded px-3 py-2 focus:outline-none focus:ring-2 focus:ring-green-500 bg-green-50" placeholder="Valid input" />
<!-- Error: red ring -->
<input class="w-full border border-red-300 rounded px-3 py-2 focus:outline-none focus:ring-2 focus:ring-red-500 bg-red-50" placeholder="Invalid input" />
</div>Focus Styles for Links
Links are among the most important keyboard-navigable elements. By default, browsers apply a focus outline to links, but you may want to customize it to match your design. The pattern focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:rounded creates a clean ring that fits snugly around inline text links, making them clearly identifiable during keyboard navigation.
<!-- Accessible link focus styles -->
<p class="text-gray-700 leading-relaxed max-w-prose">
Visit our
<a href="#" class="text-blue-600 underline focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:rounded">
documentation
</a>
to learn more about
<a href="#" class="text-blue-600 underline focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:rounded">
getting started
</a>
with our product.
</p>Focus Within — Parent Reacting to Child Focus
focus-within: applies to a parent when any of its descendants are focused. This is useful for highlighting an entire form field container (label + input + helper text) when the input inside receives focus, not just the input itself. The visual group expands to indicate which form field group is active, making complex forms easier to navigate.
<!-- Entire form group highlights when input is focused -->
<div class="space-y-3 max-w-sm">
<!-- Container gets ring when child input is focused -->
<div class="border border-gray-200 rounded-xl p-3 focus-within:border-blue-500 focus-within:ring-2 focus-within:ring-blue-500/20 transition-all">
<label class="block text-xs font-medium text-gray-500 mb-1">Email Address</label>
<input
type="email"
class="w-full focus:outline-none text-gray-800"
placeholder="you@example.com"
/>
</div>
<div class="border border-gray-200 rounded-xl p-3 focus-within:border-blue-500 focus-within:ring-2 focus-within:ring-blue-500/20 transition-all">
<label class="block text-xs font-medium text-gray-500 mb-1">Password</label>
<input
type="password"
class="w-full focus:outline-none text-gray-800"
placeholder="••••••••"
/>
</div>
</div>Focus and Transition for Smooth Rings
Ring and border changes on focus can be animated with Tailwind's transition utilities. transition-shadow animates shadow (which rings use internally), and transition-colors animates border color changes. Setting duration-150 for a quick 150ms transition gives focus styles that feel instant and responsive without being jarring — the right balance for interactive form elements.
<!-- Smoothly animated focus rings -->
<div class="space-y-4 max-w-sm p-4">
<input
type="text"
placeholder="Focus with smooth transition"
class="w-full border border-gray-300 rounded-lg px-4 py-2 focus:outline-none focus:ring-2 focus:ring-blue-500 focus:border-blue-500 transition-all duration-150"
/>
<textarea
placeholder="Textarea with focus transition"
rows="3"
class="w-full border border-gray-300 rounded-lg px-4 py-2 focus:outline-none focus:ring-2 focus:ring-purple-500 focus:border-purple-500 transition-all duration-150 resize-none"
></textarea>
</div>Disabling Focus Styles Responsibly
You may encounter design requests to remove focus outlines entirely — resist this unless you provide an alternative. focus:outline-none alone violates WCAG 2.1 Success Criterion 2.4.7 (Focus Visible). Always pair it with a custom ring, border change, background change, or some other visible indicator. The pattern focus:outline-none focus-visible:ring-2 is the responsible way to remove the default outline while maintaining accessibility.
<!-- ❌ Bad: removes focus with no replacement -->
<button class="bg-blue-500 text-white px-4 py-2 rounded focus:outline-none">
Inaccessible (no focus indicator)
</button>
<!-- ✅ Good: replaces with custom ring -->
<button class="bg-blue-500 text-white px-4 py-2 rounded focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:ring-offset-2">
Accessible (custom ring)
</button>Focus in Select and Checkbox Elements
Native form controls like select, checkbox, and radio also respond to focus variants. For selects, the pattern is the same as inputs: focus:outline-none focus:ring-2 focus:ring-blue-500. For checkboxes, the ring wraps the checkbox square, and for radios it wraps the circle. The @tailwindcss/forms plugin provides better defaults for these elements across browsers.
<!-- Focus styles on different form controls -->
<div class="space-y-4 max-w-sm">
<!-- Select -->
<select class="w-full border border-gray-300 rounded-lg px-4 py-2 focus:outline-none focus:ring-2 focus:ring-blue-500">
<option>Option 1</option>
<option>Option 2</option>
<option>Option 3</option>
</select>
<!-- Checkboxes -->
<label class="flex items-center gap-3 cursor-pointer">
<input type="checkbox" class="w-4 h-4 rounded border-gray-300 text-blue-600 focus:ring-2 focus:ring-blue-500" />
<span>Agree to terms</span>
</label>
<!-- Radio -->
<label class="flex items-center gap-3 cursor-pointer">
<input type="radio" name="plan" class="w-4 h-4 border-gray-300 text-blue-600 focus:ring-2 focus:ring-blue-500" />
<span>Monthly plan</span>
</label>
</div>Skip Navigation Links
Skip navigation links are the first focusable element on a page, allowing keyboard users to jump directly to the main content and bypass the navigation. They are visually hidden by default but become visible on focus. The pattern uses sr-only combined with focus:not-sr-only focus:absolute to bring the link into view only when a keyboard user tabs to it. This is a WCAG 2.4.1 compliance requirement.
<!-- Skip navigation link: visible only on keyboard focus -->
<a
href="#main-content"
class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 bg-blue-500 text-white px-4 py-2 rounded font-medium z-50"
>
Skip to main content
</a>
<nav class="bg-gray-800 text-white px-6 py-4">
<!-- Navigation items -->
</nav>
<main id="main-content" class="p-6">
Main content here
</main>Focus Styles in Dark Mode
Focus rings designed for light mode may disappear or lose contrast in dark mode. Use Tailwind's dark: variant to switch ring colors: focus-visible:ring-blue-500 dark:focus-visible:ring-blue-400 uses a slightly lighter blue in dark mode for better contrast against dark backgrounds. Alternatively, use white rings on dark surfaces: dark:focus-visible:ring-white.
<!-- Focus rings for both light and dark mode -->
<div class="p-6 bg-white dark:bg-gray-900 space-y-3">
<input
type="text"
placeholder="Adaptive focus ring"
class="w-full bg-white dark:bg-gray-800 border border-gray-300 dark:border-gray-600 text-gray-900 dark:text-white rounded-lg px-4 py-2 focus:outline-none focus-visible:ring-2 focus-visible:ring-blue-500 dark:focus-visible:ring-blue-400 focus-visible:border-blue-500 max-w-sm"
/>
</div>Quick Check
Test your understanding of Tailwind CSS Mastery concepts from this lesson.
Lesson Recap
In this lesson you learned: focus: fires on any focus event while focus-visible: fires only for keyboard navigation, focus-within: highlights a parent when any child is focused — great for form field groups, and always pair focus:outline-none with a custom ring to maintain WCAG accessibility. Next up we explore disabled and placeholder variants for form element styling.
Preguntas frecuentes
¿La lección «Variantes focus y focus-visible» es gratis?
Sí — el texto completo de «Variantes focus y focus-visible» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Tailwind CSS Academy, actualiza a CoddyKit PRO. El curso de Tailwind CSS Academy incluye 4 lecciones en total.
¿Qué aprenderé en «Variantes focus y focus-visible»?
Aplique estilos focus:* para la navegación con teclado y focus-visible:* para mostrar anillos de foco únicamente a usuarios de teclado, no al hacer clic con el ratón. Practicas Tailwind CSS Academy con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Tailwind CSS Academy?
No se requiere experiencia previa. Tailwind CSS Academy en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 2 de 4.
¿Cuánto tiempo toma la lección «Variantes focus y focus-visible»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Tailwind CSS Academy?
Sí. Cada lección de Tailwind CSS Academy incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Variantes hover y active
- Variantes focus y focus-visible
- Variantes disabled y placeholder
- Variantes group y peer