How is the studio designed for access?

What is implemented

Stations, the field folio list and every form control are reachable in document order with the keyboard, focus outlines stay visible, and dialogs are native elements that return focus to the control that opened them. Text reflows without horizontal scrolling down to a narrow phone width, motion respects the reduced-motion setting, and forced-colour mode is supported. Each control carries a real label rather than relying on hint text alone.

What automated checks do not cover

Automated axe checks run against the landing page, the published notes and the studio on every browser test run, and they catch only a narrow band of problems. Sessions with people using screen readers, magnification, switch access or voice control on their own hardware have not been run, and no conformance level is claimed. The exported reader page is plain semantic HTML with no script, so it zooms, reflows and prints on its own.

How to report a barrier

Write down the browser and version, the station you were on, the control by its visible label, and what you expected to happen. Send that to the support address in the page footer. A description of the blocked step is more useful than a screenshot alone, because the fix is usually in the markup for that one control.

Worked example from the sample project

Work the sample with the keyboard alone. The station navigation, the field folio list and every form control in the folios are reachable in order, focus stays visible, and dialogs return focus to the control that opened them. The exported reader page is plain semantic HTML with no script, which means it reflows, zooms and prints without any of the studio's chrome getting in the way.

That last point is not incidental. The handoff packet's reader page is often the artifact somebody actually reads, sometimes on paper, sometimes through a screen reader, usually months later. A documentation product whose output is inaccessible has failed at its only job.

What this does not do

• No conformance certification is claimed for this release.
• Automated scans do not replace testing with people using assistive technology, which remains an owner gate.
• Screen-reader behaviour varies by browser and version and is not guaranteed by the product.

Do this in the studio

Check the artifact people will actually read, which is the exported reader page.

1. Open the Handoff packet station and export the packet.
2. Open the reader page and navigate it with the keyboard and at 200 percent zoom.
3. Print one page and confirm the field folios stay legible.

Open the studio at the Handoff packet station

Related reading

• What the packet contains
• Support
• Product limitations