Make tabs keyboard navigable
SkillWeb & browsingtabs-accessibility is a skill for AI agents that checks whether Make tabs keyboard navigable works correctly in web pages. It validates the final browser-facing markup rather than the source framework abstraction, so it can be used when reviewing templates, rendered HTML, or shared components.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load skills.
Then ask your AI: use the Make tabs keyboard navigable skill
What your AI can do with it
- Checks that tab navigation on web pages works with the keyboard
- Validates the final browser-facing HTML, not just source framework code
- Reviews templates for keyboard navigability of tabs
- Reviews rendered HTML for keyboard navigability of tabs
- Reviews shared components for keyboard navigability of tabs
Getting started
- Have an AI agent that can load skills.
- Add the tabs-accessibility skill to the agent's available skills.
- Ask the agent to review a template, rendered HTML page, or shared component that contains tabs.
- The agent applies the skill to validate the final browser-facing markup for keyboard tab navigation.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/tabs-accessibility/SKILL.md and read by ahel’s review.
Incorrectly implemented tabs trap keyboard users or leave screen reader users unable to understand the relationship between tabs and their content.
Quick Reference
- Use tablist, tab, and tabpanel roles
- Only one tab in the tab order at a time (roving tabindex)
- Arrow keys navigate between tabs, Tab moves to panel
- Connect tabs to panels with aria-controls/aria-labelledby
Check
Verify tabs use tablist/tab/tabpanel roles, aria-selected state, and arrow key navigation between tabs.
Fix
Implement tabs with role='tablist', role='tab', role='tabpanel', aria-selected, and proper keyboard interaction patterns.
Explain
Explain the ARIA tabs design pattern and how proper implementation ensures keyboard and screen reader accessibility.
Code Review
Review templates, server-rendered HTML, and shared components that output markup related to Make tabs keyboard navigable. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/tabs-accessibility
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should this skill be used?
- Use it when reviewing templates, rendered HTML, or shared components related to making tabs keyboard navigable.
- Does it check source code or the final page?
- It validates the final browser-facing markup, not just the source framework abstraction.
- What does the skill check?
- It checks that tab navigation on web pages works with the keyboard by validating the final HTML.
Advanced
- Item type
- skill
- Key
tabs-accessibility- Source
- github.com/thedaviddias/front-end-checklist