Skip to content

Validate the complete Windows NVDA screen-reader matrix #1

Description

@mattheliu

Exact campaign target

Validate the DSH core Web tasks with a person directly operating and listening to NVDA on physical Windows.

Do not begin until the campaign manifest says open. The launcher must report:

  • DSH 0.1.2-alpha.2: 5803bfcfdd502adac26ae9b8eec12d6aed263ec6
  • accessibility lab 0.1.0-beta.6: 6aed71615edd1db1ec5b12897e1ad40b79294c78
  • protocol: dsh-core-at-lab/1.0.0-draft

The previous candidate text in this Issue is superseded. Historical comments remain valid only for the versions they name.

Primary environment

  • physical Windows with exact OS build;
  • exact NVDA and Chrome versions;
  • one UI/speech language, voice, verbosity, punctuation, browse/focus-mode, input, and output configuration per result;
  • the lab's cross-platform chrome mode, which creates and removes a temporary profile and blocks non-loopback name resolution.
pnpm --dir dsh-accessibility run lab:at:core ../deepseek-harness chrome

Use AT-CORE-LAB.md. Record these nine claim-eligible task IDs without renaming them:

  • discover-structure
  • navigate-sessions
  • search-sessions
  • adjust-layout
  • switch-session-view
  • read-conversation
  • inspect-trajectory
  • configure-settings
  • edit-composer-draft

Required observation

For every task, retain pass, partial, or fail; independent/effective/safe completion; actual NVDA speech and keyboard observations; browse/focus-mode changes; focus before and after important transitions; assistance; workaround; and the smallest reproducible barrier. A modality may be claimed only when directly observed on every claimed task. Do not infer output from captions, DOM, accessibility trees, automation, screenshots, or AI operation.

Use only the disposable synthetic Sessions. Stop if personal browser UI or content appears. Never publish the one-use sign-in URL, raw speech history, recordings, logs, prompts, credentials, personal paths, or participant data.

Acceptance boundary

  • Partial and failed results remain claim: none and are not rerun or rewritten to hide a barrier.
  • A candidate a11y-at-tested record must pass the public human-evidence validator and public review for this exact cohort.
  • This Issue does not establish Windows, NVDA, or whole-product support by itself.
  • Disabled-developer task completion is collected separately and is never inferred from an AT-specialist result.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityAccessibility barriers, support, and inclusive designhelp wantedExtra attention is neededneeds-at-verificationRequires manual or independent assistive-technology verificationpriority:P0Blocks independent completion of a core task or release gate

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions