dsh-accessibility

The default DeepSeek Harness (DSH) client is not screen-reader friendly: there is no built-in semantic diagnostics feedback, no operation guide for VoiceOver, NVDA, or JAWS, and the conversation interface is hard to consume through assistive technology. dsh-accessibility is an optional DSH companion that addresses exactly this gap — it does not patch DSH components; instead it plugs into official DSH slots and structured projections to give disabled developers an accessibility path free of brittle DOM-class hacks.

Three capabilities stand out. First, page-level semantic diagnostics: seventeen structural checks cover landmarks, the application heading, control names, image alternatives, nested interactive controls, ARIA references, menus, listboxes, trees, radio groups, tab lists, dialogs, and adjustable separators. Every failed check ships with contextual inspection and repair guidance, and a single-defect practice mode keeps results stable at 1/17 for repeatable human evaluation. Second, an experimental Accessible View registered through DSH's official conversation.view slot: it renders finalized and in-progress records in source order, preserves semantic Markdown and code, offers explicit disclosures for context, reasoning, tool arguments and output, command input, and errors, and supports per-message copy plus older-history loading. Third, assistive-technology quick guides and a CLI accessibility presentation: built-in VoiceOver / NVDA / JAWS cheat-sheets, a low-noise headless display, and a versioned final JSON result on the development line. A transient focus tracker additionally reports the latest external focus target's approximate name, role, Tab position, and exposed state without ever displaying or retaining classes, IDs, selectors, URLs, or HTML.

On security and privacy, diagnostics inspect only the current document's in-memory semantic attributes and never read conversation text. The Accessible View reads the structured conversation solely after an explicit user action; sensitive technical sections require separate disclosure, and copying is a per-message system-clipboard action. Neither feature makes network requests, emits telemetry, or persists its own results or conversation copies. The plugin is well suited for developers who want screen-reader support, semantic diagnostics feedback, or an accessible reading experience inside DSH — especially disabled developers — and for teams that need to verify their DSH UI meets basic accessibility contracts.