Keyboard navigation.
A skip link leads directly to the main content. The header remains available while scrolling, and anchored headings have space above them so the header does not cover their text. On smaller screens, the menu button opens the navigation and reports its expanded state. Escape closes an open menu and returns focus to its button.
Links and buttons have visible focus styles. The code sample tabs support arrow keys, Home, and End. Guide headings and breadcrumbs provide additional ways to understand the page structure.
Using the demonstrations.
The robot’s named pose controls, sequence, pause, reset, and gripper controls are buttons. The claw offers equivalent button and keyboard actions. Focus the cabinet itself, then use Left and Right arrows to aim, or Space and Enter to drop. These shortcuts do not apply to unrelated page content.
Status messages describe each demonstration’s state in text. Capsule color is accompanied by its name and position. The illustrations are labeled as local demonstrations rather than physical controls.
Motion and visual presentation.
Reduced-motion preferences shorten transitions and avoid unnecessary animation. Neither demo starts moving automatically. The site does not use flashing prize reveals, background video, or automatically playing audio.
The layout adapts to small screens and enlarged text. Long code samples and reference tables scroll within their own containers. The static guides remain readable when JavaScript is disabled, while the interactive controls explain that JavaScript is needed.
Continuing to improve.
This page describes implemented features, not a certification or a claim that every possible accessibility need has been independently audited. A visual robot illustration may not communicate every spatial detail equally well to all readers; the text state, local API reference, and long-form guides provide complementary information.
Report a barrier.
Email [email protected] with the affected page, task, browser, and assistive technology when relevant. Describe what prevented progress. Avoid including sensitive personal information in a screenshot or log.
For task details, read the playground instructions. For the precise state contract, use the local API reference.