PRIMARY-AT-CAMPAIGN.md

Primary VoiceOver, NVDA, and disabled-developer campaign

简体中文 | English

Campaign status: open; real VoiceOver, NVDA, and disabled-developer results may now be submitted. Campaign protocol: dsh-a11y-primary-at-campaign/0.1.0-draft. Scenario protocol: dsh-core-at-lab/1.0.0-draft. Machine-readable state: PRIMARY-AT-CAMPAIGN.json.

This first campaign targets exact DSH 0.1.2-alpha.2 revision 5803bfcfdd502adac26ae9b8eec12d6aed263ec6 with exact lab revision 6aed71615edd1db1ec5b12897e1ad40b79294c78. An isolated-Chrome startup and cleanup smoke run passed for this pair on macOS. A separately regenerated three-engine browser report passes fourteen deterministic checks on the same exact DSH revision and is bound in the machine manifest. These prove only lab and automated-browser readiness; the ledger still contains zero human records.

Public availability and evidence boundary

The exact core and lab revisions, this default-branch guide, the bilingual intake forms, Discussion 16, NVDA Issue 1, and VoiceOver Issue 2 were anonymously verified before the campaign opened. All five availabilityGates rows in the manifest are ready.

Opening the campaign is coordination state, not accessibility evidence. The ledger starts with zero human records; failed and partial submissions are welcome, and no intake Issue becomes a support claim without separate consented, de-identified, validated, and publicly reviewed evidence.

Recheck the five public gates anonymously at any time:

pnpm run campaign:public:verify
pnpm run campaign:public:require

The first command always prints a versioned, privacy-minimized observation report. The strict command exits nonzero unless the exact revisions, default-branch intake, Discussion 16, and Issues 1/2 are all publicly readable and current without credentials. Neither command edits the campaign or creates human evidence.

Maintainer publication order and tested replacement bodies for the default-branch PR, Discussion 16, and Issues 1/2 are in the primary AT outreach handoff.

Exact setup for this open campaign

git clone https://github.com/omdsh-dev/deepseek-harness.git
git -C deepseek-harness checkout 5803bfcfdd502adac26ae9b8eec12d6aed263ec6
pnpm --dir deepseek-harness install --frozen-lockfile
pnpm --dir deepseek-harness run build

git clone https://github.com/omdsh-dev/dsh-accessibility.git
git -C dsh-accessibility checkout 6aed71615edd1db1ec5b12897e1ad40b79294c78
pnpm --dir dsh-accessibility install --frozen-lockfile

For VoiceOver with Safari on a dedicated clean profile:

pnpm --dir dsh-accessibility run lab:at:core ../deepseek-harness safari

For NVDA with Chrome on physical Windows, use the cross-platform isolated profile:

pnpm --dir dsh-accessibility run lab:at:core ../deepseek-harness chrome

The launcher must report the two exact revisions above. Stop if either checkout is dirty, a different revision appears, personal browser UI appears, or the disposable fixture is not the only content. Follow AT-CORE-LAB.md, then submit one environment/language combination through the AT form. A disabled developer uses the same exact lab and the dedicated disabled-developer form; dedicated AT is recorded only when actually used.

First-wave acceptance

• VoiceOver/Safari: all nine claim-eligible core tasks have direct human observations for every declared modality and at least one focus transition per Web task.
• NVDA/Chrome: the same exact task set on physical Windows, including browse/focus-mode behavior.
• Disabled-developer core: one participant completes all seven representative-core tasks independently, effectively, and safely in one exact-environment record.
• Failed and partial outcomes remain public barriers with claim: none; no result is normalized into a pass.
• Every candidate claim passes pnpm run evidence:validate and public review. Coverage remains scoped and is never called “fully accessible” or certification.

See COMMUNITY-VALIDATION.md for consent, privacy, compensation, withdrawal, observation, and review rules.