Skip to content

accessibility.md

Latest commit

 

History

History
42 lines (31 loc) · 2.75 KB

accessibility.md

File metadata and controls

42 lines (31 loc) · 2.75 KB
Raw

Accessibility

Blueprints is designed so the release-planning workflow does not depend on recognizing unfamiliar icons or understanding its signature implementation.

Current interaction support

  • Main destinations use outcome-based text labels and explicit accessible names.
  • Ctrl+1 through Ctrl+6 switches between Home, Plan releases, Find work, People, Share changes, and Safety check. Use Command instead of Ctrl on macOS.
  • Standard Tab and Shift+Tab navigation reaches form fields and actions.
  • All icon-only canvas controls expose text tooltips and accessible names.
  • Canvas nodes support keyboard selection and movement; the on-screen footer lists the available keys.
  • Version frames and work-item cards expose descriptive accessible names and help text; relationship edges identify their type and label.
  • Ctrl/Command+7, 8, and 9 switch Plan, Dependencies, and Release Notes views.
  • Ctrl/Command+F focuses search, Ctrl/Command+L enters connection mode, and Ctrl/Command+J zooms to selection.
  • Ctrl/Command+Shift+V creates the named version and Ctrl/Command+Shift+I opens a new work item for the selected version.
  • In Plan, Left/Right moves selected editable work between lifecycle columns through the signed workflow. In graph views, arrow keys move selected nodes; Shift changes the step to ten pixels.
  • Destructive and irreversible actions use text labels and explain their consequences.
  • Color is supplemented by labels, counts, status text, and guidance.
  • Default Fluent focus presentation is retained rather than hidden by custom styling.

Language rules

Primary navigation and first-run setup use user outcomes rather than implementation terms. Advanced evidence such as signatures, manifests, key IDs, and audit details belongs in Safety check, Share changes, or People, where it is accompanied by plain-language guidance.

Every new empty, blocked, invalid, or read-only state should answer:

  1. what happened;
  2. whether the user's data changed;
  3. what the user can safely do next.

Stable-release qualification

The current repository has automated command and workflow coverage, but it does not yet claim completed assistive-technology certification. Before v1.0, retain manual results for every supported desktop platform covering:

  • keyboard-only first run, project creation, release planning, export, invitation, sync, conflict, and identity recovery;
  • visible focus at 100%, 150%, and 200% display scaling;
  • screen-reader names, roles, state changes, and reading order;
  • high-contrast or increased-contrast settings;
  • reduced-motion behavior if motion is introduced;
  • text clipping at supported window minimums and increased system text sizes.

Accessibility regressions are release blockers for the primary workflow.