Files
pipdock/.github/PULL_REQUEST_TEMPLATE.md
T
poli0981andClaude Fable 5.2 3e2c5e1a07 docs: accessibility statement, contributing guide, code of conduct and templates
GitHub's community profile listed five things missing, and the ops repository
supplies no defaults despite its description, so they are added here.

ACCESSIBILITY.md is at the root, where GitHub looks and where the README can
link it. It follows the Accessibility Toolkit's structure, rewritten for a
Windows desktop application and a CLI: the target (WCAG 2.2 AA, as a target and
not a conformance claim), what is supported, a table of what was tested and by
whom, what was not tested, the known limitations, and how to report a barrier
without a GitHub account. It commits to an answer within seven days and to no
fix date, because one person cannot honestly promise one.

CONTRIBUTING.md states the rules a contributor actually meets: the checks CI
runs, generated bindings, goldens, both locales, and the invariants that are
not negotiable. CODE_OF_CONDUCT.md is Contributor Covenant 2.1, unmodified
apart from the contact address. The pull request template carries an
accessibility checklist, and accessibility.yml is an issue form that asks for
impact rather than for a diagnosis. bug_report.yml keeps its name: the in-app
Report bug link is built from it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 20:01:03 +07:00

1.8 KiB

What this changes

How it was checked

  • A test fails without this change and passes with it
  • npm run lint, npm run typecheck, npm test
  • cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace --locked

If it touches…

  • A Rust type that crosses to the UI — bindings regenerated (cargo run -p xtask -- bindings)
  • CLI output — goldens re-blessed deliberately, and the diff is the change you meant
  • User-visible text — added to both ui/src/locales/en and ui/src/locales/vi; nothing phrased in Rust
  • A new error code — every place CLAUDE.md lists, both errors.json included
  • Behaviour a user reads about — docs/ updated, and legal/ checked separately
  • Something a user would notice — an entry in changelog/

Accessibility (for any change to the interface)

  • Everything new can be reached and operated with the keyboard alone
  • Focus is visible, and goes somewhere sensible when the screen changes or a dialog closes
  • Controls that show only a symbol have an accessible name; inputs have labels
  • Nothing is said by colour alone, and a destructive button carries data-destructive
  • Checked once with a screen reader, or said here that it was not