
responsive-accessibility
Design responsive layouts that maintain accessibility across screen sizes, zoom levels, and orientations. Use when designing responsive interfaces, testing zoom behaviour, or reviewing layouts across devices. Triggers on: responsive, zoom, reflow, breakpoint, mobile accessibility, screen size, orientation, viewport, 200% zoom, text scaling, layout shift, horizontal scroll.
- Installs
- 80
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill responsive-accessibility- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads responsive-accessibility automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Responsive Accessibility
Responsive design isn't just about screen size — it's about ensuring accessibility holds at every viewport, zoom level, and orientation. A layout that works at 1440px but breaks at 200% zoom has failed the users who need zoom most.
Core Requirements
Text Reflow at 200% Zoom
- All content must reflow into a single column at 200% zoom with no horizontal scrolling
- This is WCAG 2.1 Level AA (Success Criterion 1.4.10)
- Test by setting browser zoom to 200% at 1280px viewport — the result must be usable without horizontal scroll
- Exceptions: data tables, maps, and diagrams may scroll horizontally if no information is lost
Text Scaling to 200%
- All text must remain readable when scaled to 200%
- Text must not be clipped, truncated, or overlap other elements
- Use relative units (rem, em, %) not fixed pixels for text
- Line height and spacing should scale proportionally
Orientation Freedom
- Content must work in both portrait and landscape orientation
- Never lock orientation unless essential to function (a piano app may need landscape; a form never does)
- Some users mount devices in fixed orientations due to physical setup — locking orientation can block access entirely
Design Patterns
Fluid Layout
- Use flexible grids that adapt rather than fixed breakpoints that snap
- Set max-width on content containers for readability (45–75 characters per line)
- Let whitespace compress before content reflows
- Avoid fixed-width elements that force horizontal scroll
Content Priority
- Define what's essential at each breakpoint
- On small screens: show core content, provide access to rest
- Don't hide critical functionality behind "desktop only" features
- Navigation should adapt (hamburger menu is fine) but all destinations must remain accessible
Touch and Pointer Adaptation
- At small viewports: increase touch targets to 48px minimum
- At large viewports: pointer-friendly sizes are acceptable (24px minimum)
- Detect pointer type with
@media (pointer: coarse)for touch-first sizing - Spacing between targets should increase on touch devices
Zoom-Safe Patterns
- Sticky headers must not consume excessive vertical space at zoom (a header that takes 30% of the viewport at 200% zoom is a barrier)
- Fixed-position elements must be tested at 200% zoom
- Tooltips and popovers must remain visible and reachable at zoom
- Modal dialogs must be scrollable if content exceeds viewport at zoom
Testing Protocol
- Test at 100%, 150%, and 200% browser zoom on a 1280px viewport
- Test at 320px viewport width (mobile equivalent)
- Test in both portrait and landscape orientation
- Test with system font size set to largest option
- At each test point verify: no horizontal scroll, no clipped text, no overlapping elements, all interactions functional
Assessment Checklist
- Content reflows at 200% zoom without horizontal scrolling
- Text remains readable at 200% scaling
- Both orientations are supported
- Touch targets increase at small viewports
- Sticky/fixed elements don't dominate the viewport at zoom
- No functionality is lost at any supported viewport size
- All text uses relative units
FAQ
What does the responsive-accessibility skill do?
Design responsive layouts that maintain accessibility across screen sizes, zoom levels, and orientations. Use when designing responsive interfaces, testing zoom behaviour, or reviewing layouts across devices. Triggers on: responsive, zoom, reflow, breakpoint, mobile accessibility, screen size, orientation, viewport, 200% zoom, text scaling, layout shift, horizontal scroll.
How do I install responsive-accessibility?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill responsive-accessibility in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/responsive-accessibility/ (personal) or .claude/skills/responsive-accessibility/ (project).
Which AI agents can use responsive-accessibility?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is responsive-accessibility safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains responsive-accessibility?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 80 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
keyboard-navigation
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
responsive-review
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
user-preference-respect
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
error-prevention-recovery
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.