Build an additive Accessible View MVP through conversation.view

[mattheliu]

Outcome

Provide a user-selected, stable reading view for conversation content without scraping or rewriting the host DOM.

Constraints

• Use the DSH conversation.view extension seam and the supported conversation projection.
• Do not observe generated classes, patch host roles, or capture content without an explicit user action.
• Preserve source order, headings, code semantics, status, and focus return.
• Default exports and diagnostics must redact prompts, model output, usernames, paths, and environment identifiers.

Acceptance evidence

• Keyboard and screen-reader task scenarios cover opening, navigating, copying, returning, and recovering from errors.
• Privacy and permission review is linked.
• Unit, integration, axe, and assembled-browser tests pass.
• Listener-verified VoiceOver and NVDA results are recorded before a stable support claim.

[mattheliu]

Automated candidate ready; community AT verification requested

PR #18 now has a green version-scoped automated baseline for commit 27a8007b0b0f65e6a5aa145ff2925598b6fe780d:

• six-platform validation and aggregate gate
• exact DSH + external plugin + Chromium assembled job
• dsh-accessible-view/1.0.0-draft: idle/loaded axe 0, content gate, focus return, and clipboard projection passed

This is not a screen-reader pass. We are requesting independent, listener-verified results for at least:

1. macOS + browser + VoiceOver, with exact versions and language;
2. Windows + browser + NVDA, with exact versions and language;
3. one independent core reading task completed by a disabled developer, with consent and de-identified evidence.

Candidate setup

Use a disposable DSH home and synthetic content only:

git clone https://github.com/omdsh-dev/deepseek-harness.git
git clone https://github.com/omdsh-dev/dsh-accessibility.git

cd deepseek-harness
git checkout dsh-v0.1.1-rc.2-a11y.4
pnpm install
pnpm run build:official

cd ../dsh-accessibility
git checkout feat/accessible-view-mvp
pnpm install --frozen-lockfile
pnpm run build

cd ../deepseek-harness
DSH_TEST_HOME="$(mktemp -d)"
DSH_HOME="$DSH_TEST_HOME" pnpm dsh plugin --profile web add file:../dsh-accessibility
DSH_HOME="$DSH_TEST_HOME" pnpm dsh web

Do not use real prompts, workspaces, paths, credentials, or recordings in public evidence. The disposable home still contains local test state and should be moved to Trash after verification.

What to verify and report

Follow the nine tasks in the English protocol or 中文规程. Report:

• OS, browser, AT, language, verbosity, and punctuation settings;
• exact DSH tag and companion commit;
• each task's actual spoken output, focus target, pass/fail, workaround, and severity;
• a sanitized evidence link or a structured comment—never raw conversation or personal data.

Please report failures as failures; partial or negative evidence is useful. The issue stays open and retains needs-at-verification until the named VoiceOver/NVDA and disabled-developer evidence rows are reviewed.

---

自动候选已就绪，征集社区真实辅助技术验证

PR #18 的跨平台自动测试和精确 DSH + Chromium 组装测试已经通过，但这不等于读屏通过。现征集人工听读的 VoiceOver、NVDA 结果，以及一轮经同意、去标识化的残障开发者独立任务验证。请使用一次性 DSH 目录和合成内容，按上方中文规程逐项记录实际朗读、焦点、结果、变通方式和严重度；公开材料不得包含真实对话、路径、凭据或个人信息。

[mattheliu]

Safer real-AT setup available

The community request above now has a versioned hermetic launcher in PR #20:

• protocol and commands: https://github.com/omdsh-dev/dsh-accessibility/blob/feat/hermetic-at-lab/AT-LAB.md
• 中文规程: https://github.com/omdsh-dev/dsh-accessibility/blob/feat/hermetic-at-lab/AT-LAB.zh.md
• exact automated readiness evidence: feat: publish DSH accessibility validation foundation #20 (comment)

It starts the exact external companion in a disposable DSH Web world, seeds only committed synthetic history, prints exact revisions, opens the requested real/system browser, and cleans owned state on bounded or handled exit. This replaces manual profile installation for AT observation and reduces the chance of exposing a tester's normal DSH data.

The readiness run is not VoiceOver/NVDA or disabled-user evidence. Issue #10 remains open until the ten Accessible View tasks have complete human-observed speech/focus records and at least one consented, de-identified disabled-developer task result.