Documentation maintenance and accessibility

Deliberate Scalar updates

A dependency change needs a contract/security reviewer and release-note reviewer from the ownership policy. Record the old/new exact Scalar and transitive version set, upstream release/security notes, license changes and lockfile integrity. Do not use a floating CDN or automatically accept an upgrade.

Run pinned OpenAPI standards/example validation, link/freshness checks and typecheck; then build the actual Worker and run documentation production browsers. Exercise entered synthetic bearer credentials, intended API request, storage/cookies/IndexedDB/reload, all outbound origins, search/tag/schema/example/download controls, keyboard navigation, reduced motion, narrow/zoomed view and failed-load recovery. Inspect CSP violations and the styling exception in architecture. Retain current receipts before merging. Roll back the package/lockfile together if privacy or rendering regresses.

Manual keyboard and screen-reader smoke

This is a repeatable procedure; publication of it is not evidence that a human completed it.

Use a clean browser profile, no saved session and a synthetic disposable key. Record OS/browser/assistive-technology versions and viewport/zoom. For keyboard-only review, Tab from the address bar: the skip link must be visible, Enter must focus the API reference landmark, every interactive control must have visible focus, and no focus trap may occur outside an open dialog. Search for createTask, follow its tag/operation, expand schema/examples, open and close the request editor, use raw-spec links and return. Escape must close dismissible overlays with focus restored.

With NVDA/Firefox or VoiceOver/Safari, navigate landmarks and headings. Confirm operation names/methods, parameter requiredness, schema expand/collapse state, code-copy labels, error feedback and auth input names are announced. Ensure links make sense outside paragraph context. Enter a synthetic key only into the auth control and never record its value. Check text at200%zoom and reflow at320CSSpixels, reduced motion and high contrast. Verify that failed specification loading announces an alert with raw-spec/support recovery links.

Report each defect with route, action, expected/actual announcement or focus order and a redacted screenshot. Record pass/fail per step, not simply 'accessible'. A new human quickstart test separately verifies account/key setup without undocumented assistance.

Historical documentation

Only v1 draft is currently published; there is no supported historical stable major to fabricate. On the first supported stable release, archive immutable JSON/YAML, generated guides, release commit/digest and changelog under a version-specific artifact location. Keep each supported major's docs available while its API major is supported, with canonical links to that major and an explicit latest-version link.

When support ends, keep historical artifacts read-only, label the end-of-support date prominently and disable interactive execution against unsupported endpoints. Never silently redirect a historical contract URL to a different major. Redact exposed secrets through incident procedure, retaining an audit note rather than rewriting history invisibly. Test supported/archived routes and metadata whenever introducing another major.