Accessible Page and Route Transitions
Add page transitions while preserving keyboard focus, scroll restoration, history, reduced-motion preferences and a no-animation fallback.
Define the navigation contract before choosing motion. A full route change, browser Back, tab switch and inline filter update need different focus and scroll outcomes. For a new page, identify the destination heading or content landmark. For Back, decide whether to restore the prior scroll and interaction target. For an inline change, avoid moving focus from the user's active control unless the task requires it. ## Key Points - [CSS View Transitions module](https://www.w3.org/TR/css-view-transitions-1/) - [Chrome same-document transition and focus guidance](https://developer.chrome.com/docs/modern-web-guidance/guides/ui-behaviors/same-document-transitions) - [WCAG 2.2 focus requirements](https://www.w3.org/TR/WCAG22/?KBOpenTab=undefined)
skilldb get design-systems-skills/page-route-transitionsFull skill: 29 linesAccessible Page and Route Transitions
Define the navigation contract before choosing motion. A full route change, browser Back, tab switch and inline filter update need different focus and scroll outcomes. For a new page, identify the destination heading or content landmark. For Back, decide whether to restore the prior scroll and interaction target. For an inline change, avoid moving focus from the user's active control unless the task requires it.
Keep navigation independent of animation
Perform exactly one route update through the router or browser. Feature-detect any optional view-transition API and keep the same update available without animation. If using document.startViewTransition for a same-document route, coordinate the DOM commit with the router's supported mechanism. The API animates visual snapshots and does not replace focus or routing logic. Avoid wrapping the route in a transition that can prevent navigation when the browser skips the animation or the update fails.
Respect prefers-reduced-motion using a no-motion or appropriately reduced presentation. Keep status and route change information available in either mode. If naming transitioning elements, ensure the intended matching names are unique in each view. Treat motion as decoration around an already usable route. Do not delay link semantics or make an animation promise the only trigger for state changes.
Restore focus, scroll and failure behavior
Set the page title and apply the intended focus when the new content is committed. Give the target a programmatic focus path where necessary and ensure it is not hidden by a sticky header. Coordinate with scroll restoration so focusing does not accidentally override the browser Back position. Handle an interrupted or superseded navigation so an older transition cannot move focus or scroll on the latest route.
Test keyboard link activation, rapid successive navigation, Back and Forward, reduced motion, disabled support and a failed or delayed load. Confirm visible focus, title, scroll and content match the current URL. Verify a focused control being removed has a useful successor. Record supported browser versions and which path was tested without animation.
References and rights
- CSS View Transitions module
- Chrome same-document transition and focus guidance
- WCAG 2.2 focus requirements
Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.
Install this skill directly: skilldb add design-systems-skills
Related Skills
Responsive Patterns
Responsive design patterns, fluid layouts, and adaptive component strategies for design systems
Storybook Docs
Storybook documentation, visual testing, and interactive component cataloging for design systems
Theming
Theme systems, dark mode implementation, and runtime theme switching for design systems
White-Label Multi-Tenant Frontend
Serve tenant-specific branding with safe hostname resolution, validated token overrides and tenant-isolated HTML, assets and cache entries.
Component Architecture
Component API design, composition patterns, and architecture for scalable design system components
Design System Governance
Versioning, contribution processes, and governance models for design system teams