aida-docs 0.2.0

Phone output, an accessibility pass over every output, and every dependency up to date with a clean npm audit.

Phone screenshots and video

When your app's readers use it on a phone, AIDA now captures each of their walkthroughs at a phone size too (touch, a phone browser, taps instead of clicks) and shows both:

• Help pages get phone screenshots beside the computer ones, with a Computer / Phone switch that starts on the reader's own kind of screen and is remembered across the site.
• Each walkthrough gets a portrait phone video (<id>.phone.mp4) with its own captions, chapters and transcript, shown in a phone frame with tap marks.
• The app brief decides by default (readers[].devices, from the builder interview); devices: [desktop, phone] in the config or a walkthrough overrides it. The first device is the primary one, and phone-first walkthroughs print phone screenshots in their PDFs.
• Where the phone layout differs, mark the step that only works on one device with devices: [desktop] and add a phone version with devices: [phone] (setup steps too). aida inspect --device phone shows the phone layout.
• A phone capture that fails never costs the desktop page: it's reported as a warning.
• The agent connector's get_procedure adds phoneScreenshot to each step.

Accessibility

Every output now aims at WCAG 2.2 AA where the format allows. On the example app's guide pages, axe reports no violations at computer or phone size, in light or dark mode.

• Alt text for every screenshot written from the step (the screen, what to do, what's highlighted), in pages, PDFs and cards.
• A transcript beside every video and path clip (<id>.transcript.md), shown on the page. The caption track is offered but not on by default, because captions are already in the picture. There's a chapters track. MP4s tag their audio language and carry captions as a subtitle stream.
• Guide and card PDFs are tagged, with an outline, title and language.
• Brand colours are adjusted until text reaches 4.5:1 and focus rings 3:1 (site, video and PDF, light and dark); aida theme says what it changed. Dark mode no longer inherits a text colour set only for light.
• Help site: a skip link, visible focus, reduced motion, and an accessible help chat and widget (focus kept in the dialog and returned on close, answers announced, Escape closes it).
• New QA checks: a11y:alt-text, a11y:transcript, a11y:pdf.
• New config lang (default en): the site's language, PDF language, caption tracks and transcripts.

Dependencies and security

• npm audit is clean. Kokoro, the default voice, is now vendored onto @huggingface/transformers 4 (kokoro-js pins transformers 3 and a vulnerable sharp). The audio is unchanged, and the voice file (about 0.5 MB) downloads on first use instead of shipping 28 MB of voices.
• Updated: Playwright 1.65 (run npx playwright install chromium), Next.js 16.4.5, Fumadocs 16.18, MCP SDK 1.32.2, Anthropic SDK 1.6, commander 15, vitest 5.
• Node 22.12 or later is now required (commander 15).
• Extra arguments are now an error instead of being silently ignored. aida validate and aida import playwright take several files or globs.

Upgrading

• npm i -D aida-docs@0.2.0 (or npx aida-docs@0.2.0).
• Run aida upgrade in your help app to bring in the new site components (Computer/Phone switch, transcript, skip link). Compare any .aida-new files it leaves beside ones you've changed.
• The next aida build re-renders pages and remuxes videos once (new alt text, transcripts and language tags).

npm: https://www.npmjs.com/package/aida-docs