docs: sync the specs with the accessibility pass

UI-SPEC §7 no longer describes a forced-colors list that is "not complete": the
mark is data-destructive. §8 gains the five rules the pass left behind — focus
on every screen replacement, names that contain the visible text, composite
widgets as one tab stop, chip meanings as text, status regions that exist
before their first message.

TESTING says which of the three new tests holds what, and that none of them
knows what a screen reader says; the manual charter gains a ten-minute
accessibility pass. CLI-SPEC writes down that the CLI has no colour and nothing
that animates, which was true of the code and stated nowhere.

RELEASE-CI: the conversation-resolution rule the protection table never listed,
the labels box that had been true for weeks, and .nvmrc, which still said 24 a
month after every workflow moved to 26.

README links the new files and gains Accessibility and Contributing sections.
AI-DISCLOSURE and About name the model that produced 1.5.0.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Fable 5.2 committed 2026-11-10 20:01:03 +07:00
1 parent 3e2c5e1a07
commit 4732f05197
9 files changed
+72 -13

No files matched your search

+1 -1
View File
@@ -1 +1 @@
24
26
+16 -1
View File
@@ -137,11 +137,24 @@ just stating them. Everything below is for reading the code.
| [docs/RELEASE-CI.md](docs/RELEASE-CI.md) | CI callers into `poli0981/.github`, release pipeline |
| [docs/I18N.md](docs/I18N.md) | EN/VI localization rules |
| [docs/ROADMAP.md](docs/ROADMAP.md) | Spike week, milestones, exit criteria |
| [ACCESSIBILITY.md](ACCESSIBILITY.md) | What is supported, what has been tested, what is known not to work, and how to report a barrier |
| [CONTRIBUTING.md](CONTRIBUTING.md) | Setting up, the checks CI runs, and what a pull request needs |
| [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) | Contributor Covenant 2.1 |
| [legal/](legal/) | EULA, Disclaimer, Privacy Policy, Third-Party Notices (linked by the in-app legal gate) |
## Accessibility
PipDock is built to work with a keyboard alone, with a screen reader and under a Windows contrast theme, and `pipdock` on the command line is plain text with no colour and nothing that animates. The target is WCAG 2.2 AA; it is a target and not a conformance claim, and [ACCESSIBILITY.md](ACCESSIBILITY.md) says exactly what has been tested, by whom, and what is known to fall short.
If something gets in your way, [open an accessibility issue](https://github.com/poli0981/pipdock/issues/new?template=accessibility.yml) or write to [accessibility@poli0981.dev](mailto:accessibility@poli0981.dev) — in English or Vietnamese, with no GitHub account needed and no diagnosis expected.
## Contributing
Bug reports, accessibility reports and pull requests are welcome. [CONTRIBUTING.md](CONTRIBUTING.md) covers setup, the checks, and the handful of rules that are not negotiable; everyone taking part is expected to follow the [Code of Conduct](CODE_OF_CONDUCT.md). Security problems go through the [security policy](.github/SECURITY.md), not a public issue.
## How this was built
PipDock was written with substantial help from an AI coding assistant — **Claude Opus 5** through 1.3.0 and **Claude Opus 5.5** from 1.4.0, made by [Anthropic](https://www.anthropic.com), through [Claude Code](https://claude.com/claude-code) — under human review. It wrote source code, tests, debugging work and the Vietnamese translation. Every change reached `main` through a pull request, and `main` is protected and cannot be bypassed. Through 1.3.0 the maintainer read and merged each one, and drove the built application by hand on three machines before 1.0.0 shipped; 1.4.0 was released by the assistant on the maintainer's written instruction, once its checks had passed.
PipDock was written with substantial help from an AI coding assistant — **Claude Opus 5** through 1.3.0, **Claude Opus 5.5** for 1.4.0 and **Claude Fable 5.2** for 1.5.0, made by [Anthropic](https://www.anthropic.com), through [Claude Code](https://claude.com/claude-code) — under human review. It wrote source code, tests, debugging work and the Vietnamese translation. Every change reached `main` through a pull request, and `main` is protected and cannot be bypassed. Through 1.3.0 the maintainer read and merged each one, and drove the built application by hand on three machines before 1.0.0 shipped; 1.4.0 and 1.5.0 were released by the assistant on the maintainer's written instruction — a plan the maintainer approved — once the checks had passed.
That review mattered: **thirty-five defects** reached or nearly reached `main`, and not one was caught by the test suite that was green at the time. They were found by running the thing.
@@ -158,3 +171,5 @@ PipDock is an independent project. It is not affiliated with or endorsed by the
## Tiếng Việt (tóm tắt)
PipDock là ứng dụng Windows (GUI + CLI) giúp kiểm tra, cài đặt, cập nhật và gỡ **hàng loạt** gói thư viện Python một cách an toàn: luôn chạy dry-run xem trước thay đổi, xử lý xung đột phiên bản với 3 lựa chọn rõ ràng, tự chụp snapshot trước mỗi lần chạy để rollback một chạm, cảnh báo khi gỡ gói mà gói khác đang phụ thuộc, và tổng kết "13 thành công, 2 thất bại" kèm lý do từng gói. Hỗ trợ engine pip hoặc uv (chọn trong Settings), tìm gói tức thì nhờ cache chỉ mục PyPI, kèm module Code Health (deptry/vulture/ruff) để dọn dependency thừa và dead code. Không thu thập dữ liệu. Giấy phép GPL-3.0.
**Khả năng tiếp cận:** PipDock dùng được chỉ với bàn phím, với trình đọc màn hình (đã thử với Narrator) và ở chế độ tương phản cao của Windows. Chi tiết, kể cả những gì chưa được kiểm thử, nằm trong [ACCESSIBILITY.md](ACCESSIBILITY.md). Nếu gặp rào cản, hãy [mở issue](https://github.com/poli0981/pipdock/issues/new?template=accessibility.yml) hoặc viết tới [accessibility@poli0981.dev](mailto:accessibility@poli0981.dev) — tiếng Việt cũng được.
+11 -4
View File
@@ -13,10 +13,10 @@ commit trailers. Nothing here changes the licence or the warranty position — s
| | |
|---|---|
| Model | **Claude Opus 5** — first commit through 1.3.0 · **Claude Opus 5.5** — from 1.4.0 |
| Model | **Claude Opus 5** — first commit through 1.3.0 · **Claude Opus 5.5** — 1.4.0 and the maintenance after it, through 2026-11-04 · **Claude Fable 5.2** — from 2026-11-10, which is 1.5.0 |
| Vendor | **Anthropic** ([anthropic.com](https://www.anthropic.com)) |
| Interface | [Claude Code](https://claude.com/claude-code), Anthropic's CLI/desktop coding agent |
| Period | 2026-07-27 → 2026-08-21 (first commit to 1.3.0) · 2026-10-16 → 2026-10-17 (1.4.0) |
| Period | 2026-07-27 → 2026-08-21 (first commit to 1.3.0) · 2026-10-16 → 2026-10-17 (1.4.0) · 2026-10-20 → 2026-11-04 (CI and dependency maintenance) · 2026-11-10 (1.5.0) |
The trailer on each commit records which model produced it, and `git log` is the authoritative
history — the table above is a summary of it, not a substitute.
@@ -68,7 +68,13 @@ load-bearing, and all four caught real defects the review-by-reading did not:
- **The decision to release.** Through 1.3.0 every merge, tag and publish was the owner's own
action. For 1.4.0 the owner delegated the mechanics, in writing, with the conditions attached —
CI green, and the installers matching `SHA256SUMS.txt` before the draft was published — and the
decision that 1.4.0 should ship remained theirs.
decision that 1.4.0 should ship remained theirs. 1.5.0 was released the same way: the owner
chose its scope from three options, approved a written plan that named every outward step — the
two pull requests, the tag, the published release, the repository description and label — and
the assistant carried it out under the same two conditions. The owner's own keyboard and
Narrator testing of 1.4.0 is theirs and is recorded as theirs in `ACCESSIBILITY.md`; the
assistant cannot run a screen reader, and that file says which checks were a person's and which
were a machine's.
- **Anything requiring a legal or security judgment** was raised for a decision rather than taken —
for example the PEP 668 override's default, and whether a `mailto:` scheme belonged in the
browser-launch allowlist.
@@ -78,7 +84,8 @@ load-bearing, and all four caught real defects the review-by-reading did not:
Copyright in PipDock is held by **Kokone (poli0981)**, and the work is licensed **GPL-3.0-only**.
Using an AI assistant does not change either. Commits carry a
`Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>` trailer through 1.3.0 and
`Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>` from 1.4.0, as an accurate record of how
`Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>` from 1.4.0, and
`Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>` from 2026-11-10, as an accurate record of how
the work was produced — it is attribution, not an assignment of rights, and Anthropic claims no
ownership of output produced with its models.
+1
View File
@@ -8,6 +8,7 @@
2. **Safe by default, scriptable on request.** Interactive prompts appear on a TTY; in scripts (`--yes` / no TTY), a held-back package keeps its compatible version and an impossible one is **skipped** — never forced, unless `--strategy latest` asked for exactly that (§4). Off a TTY, a command that would ask first refuses instead unless `--yes` is given; `uninstall` and `pip-upgrade` ask nothing (§3).
3. **Machine-readable everywhere.** `--json` makes every command print one JSON document on stdout — the structs the GUI receives, wherever one exists (§6).
4. English-only in v1 (GUI carries EN/VI); messages reuse catalog codes so they stay greppable.
5. **Plain text, and nothing that moves.** No colour, no spinner, no progress bar, no line that rewrites itself with a carriage return: progress is whole lines on stderr, and `--quiet` drops them. This was true of the code since the first command and written nowhere, which is how a contract gets broken by someone adding a nicety. It is what makes the output readable by a screen reader, greppable in a log and the same in a pipe as on a terminal — so there is no `NO_COLOR` to honour, because there is no colour, and status is always a word (`ACCESSIBILITY.md`).
## 2. Global options
+4 -2
View File
@@ -59,6 +59,7 @@ permissions: { contents: read }
| Required approvals | **0** | a solo owner cannot approve their own PR, so 1 would deadlock. A PR is still required |
| `strict` | `false` | up-to-date-before-merge is friction on a repo that rebase-merges |
| Linear history | `true` | matches rebase-merge |
| Conversation resolution | `true` | a review thread left open blocks the merge — read from the API on 2026-11-10; this table did not list it |
| Force pushes / deletions | `false` | |
**`CI / Integration` is deliberately excluded, and this is the trap worth remembering:** its `pull_request` trigger is `paths:`-filtered, so on a docs-only or UI-only PR it never starts — and a required check that never starts stays *pending forever*. Requiring it would deadlock exactly the PRs it has no opinion about. `Re-capture against the latest engines` runs on no PR at all (Mondays and dispatch only) and is excluded for the same reason. The bare `CodeQL` check belongs to the `github-advanced-security` app rather than Actions and is left out too.
@@ -110,12 +111,13 @@ Two active lines at most: latest release gets features; previous minor gets secu
- [x] GPL-3.0 `LICENSE` at root; `legal/` committed **publicly** (the in-app legal gate links to these GitHub URLs — CommandForge lesson: don't leave them gitignored).
- [x] `.github/ISSUE_TEMPLATE/bug_report.yml` (shipped in this suite) + `config.yml` disabling blank issues.
- [x] `.github/dependabot.yml` covering cargo, npm, github-actions and the Code Health pins — and the Rust toolchain since 1.4.0.
- [x] `rust-toolchain.toml`, `.nvmrc` (24), `Cargo.lock`/`package-lock.json` committed.
- [x] `rust-toolchain.toml`, `.nvmrc` (26 — it said 24 until 1.5.0, a month after every workflow had moved to 26), `Cargo.lock`/`package-lock.json` committed.
- [x] **Repo settings (owner, via the GitHub UI or `gh` — not committable):** branch protection on `main`; disable Advanced Security → CodeQL *Default setup* (the reusable is advanced-setup and is rejected at upload time otherwise); enable Discussions for the issue-template contact links.
- [x] **Secrets via `gh secret set`:** the Discord webhooks (`DISCORD_RELEASES_WEBHOOK`, `DISCORD_REPO_WEBHOOK`, `DISCORD_CI_WEBHOOK`). No signing key — see §3.
- [x] App icon settled (`src-tauri/icons/`). It was called a placeholder because nobody had chosen it; the owner chose it in Phase 4, which is what "a brand decision" needed.
- [x] README badges: CI, CodeQL, release, license.
- [ ] **Labels (owner, repo settings — opened by 1.4.0):** `dependencies`, `rust`, `frontend`, `ci` and `code-health` for Dependabot (§2), and `triage` for `bug_report.yml`. None existed on 2026-10-17, so Dependabot's PRs arrive unlabelled and a bug report gets `bug` alone.
- [x] **Labels (owner, repo settings — opened by 1.4.0):** `dependencies`, `rust`, `frontend`, `ci` and `code-health` for Dependabot (§2), and `triage` for `bug_report.yml`. None existed on 2026-10-17; all six did by 2026-11-10, when `accessibility` joined them for `accessibility.yml`.
- [x] **Community health files (1.5.0):** `ACCESSIBILITY.md`, `CONTRIBUTING.md` and `CODE_OF_CONDUCT.md` (Contributor Covenant 2.1) at the root; `.github/PULL_REQUEST_TEMPLATE.md` and `.github/ISSUE_TEMPLATE/accessibility.yml`; and a repository description. The ops repo's description says it carries community health files and it carries none, so nothing was inherited. `bug_report.yml` keeps its name: `crates/pipdock-core/src/report.rs` builds the in-app *Report bug* link from it.
**Closed 2026-08-14, and three of the last four were already true.** CodeQL *Default setup* read
`not-configured` and Discussions were already on — both had been done and never ticked, which is
+4
View File
@@ -58,6 +58,8 @@
Component tests for `PdConflictRow` (3-way state), `PdPreviewDiff` grouping, `PdSummarySheet` counts, dimming/badging rules on `PdPackageTable`, and the design-token contrast test — every text/surface pair ≥ WCAG AA, and since 1.4.0 every badge tint composited over every surface too; it is a test, so it gates every PR. Store tests include `ui/src/stores/races.test.ts` (1.4.0): each holds a command open, moves on — another environment, another timeline entry, Back out of a plan — and only then lets it answer, because five stores wrote whatever came back without asking whether the question was still the one being asked. Six of its seven tests fail on the stores before 1.4.0. `i18n.test.ts` fails on a catalog code that either language has no copy for.
**Accessibility has three tests of its own since 1.5.0**, and it matters which one holds what. `ui/src/a11y.test.tsx` runs **axe-core** over every screen inside the shell and over the components with structure of their own; axe is called directly (`ui/src/test/axe.ts`) because `eslint-plugin-jsx-a11y` peers ESLint 9 at most and the matcher packages are pinned to a runner's major. It holds roles, names and required parts — its first run failed on the package grid — and nothing else: `color-contrast` is off under jsdom, which computes no layout, and stays the token test's job. `ui/src/destructive.test.ts` reads the source, because forced-colors cannot be rendered: every button drawn in the danger colour carries `data-destructive`, and the stylesheet draws that attribute. And where focus goes is asserted where it happens — `App.test.tsx` for the four ways a screen is replaced without a tab change, the component tests for the tab, radio group and drawer patterns. **None of the three knows what a screen reader says**; that is §4's.
IPC is mocked at the typed wrapper layer (`ui/src/test/ipc.ts`, a factory each test file passes to its own `vi.mock`) with payloads **serialized from the real Rust types** by `cargo run -p xtask -- ipc-fixtures` into `ui/src/test/fixtures/`, and `cargo test` fails when the committed files are stale — which is what guarantees UI and core agree on shapes. Where production computes a value, the fixture is computed by the same function: the guard report and the dependency graph by the real graph over the scenario's rows, the preview's blockers by `blockers_for`, and since 1.4.0 `flow_step_forced.json` by `plan::derive_forced` and `release::mismatch`. A hand-written blocker list that matched the docs while the code had drifted is how the preview shipped a garbled sentence from S3 to 1.1.0 with every suite green. `fixtures.rs` is compiled only under `cfg(test)` or the `fixtures` feature xtask enables, never into a release build. Types are generated by `cargo run -p xtask -- bindings` over `schemars`, not by tauri-specta as this line once said, so **drift is a test failure rather than a compile error** — which means it fires at `cargo test`, locally as well as in CI. See `crates/pipdock-core/src/bindings.rs`.
### L4 — CLI (assert_cmd + insta)
@@ -85,3 +87,5 @@ This section once set targets — core ≥ 85 % line coverage, classifiers and p
## 4. Manual test charter (per release)
A short exploratory pass on a real machine: dirty 150+ package env, corporate-proxy simulation (PD-NET-002 copy), non-ASCII Windows username paths, VI locale sweep of all mutation dialogs, cancel mid-Phase-B, and SmartScreen/first-run installer experience.
**And an accessibility pass, since 1.5.0** — ten minutes, on the installed build: the mouse unplugged from the legal gate through an update and its summary (after every screen change, is focus somewhere you can see?); the same with Narrator, listening for the screen's name on arrival and for the run's progress; one Windows contrast theme, looking at a destructive confirm beside its Cancel and at the current sidebar tab; and 200 % zoom. `ACCESSIBILITY.md`'s "what has been tested" table is a record of this pass and is updated by whoever does it — a statement that outlives its last test is the failure it exists to prevent. The parts a machine can do were done for 1.5.0 over WebView2's remote-debugging port (ROADMAP): the accessibility tree, emulated forced-colors and `document.activeElement` after each step.
+33 -3
View File
@@ -408,11 +408,11 @@ either number. Screens (`ui/src/screens/`, `PdPlanPanel` among them) are not cou
- Empty states: one mono glyph + one sentence + one action (e.g. Updates empty: `▸ all packages up to date`).
- Offline: banner chip in top bar; search works (local index), metadata panel shows cached-at timestamp.
- Errors: inline with catalog code, human message (localized), and *Details* expanding stderr tail. Toasts only for background completions. *Report bug* opens a prefilled GitHub issue that nothing sends until the user submits it; since 1.4.0 the link is rebuilt at the click with the selected environment, so the issue carries its Python version and the configured engine's version — one subprocess per report, rather than one per error row mounted, which a summary of many failures would multiply.
- Destructive confirms (`Force latest`, uninstall with breakage, PEP 668 override, and — since P5 — `Fix with ruff`, the only one that writes outside an environment) use `--color-danger` primary buttons and require the dialog's default focus to be **Cancel**. The PEP 668 override was on this list while it was a bare checkbox with no confirm at all; it has been a `PdDialog` since 1.4.0. A `data-action` in `styles.css`'s forced-colors list gives a destructive control a 2 px border, because high contrast drops every tint and a destructive primary that looks like Cancel is worse than no colour at all. **The list is `force` (the guard's *Remove anyway*), `uninstall`, `rollback`, `upgrade-pip` and `fix`, and it is not complete:** the uninstall dialog's plain *Remove* (`remove`), the *Force latest* inline confirm's button, the override's *Allow* (`allow-override`), Disk usage's *Clear* confirm (`confirm-clear-cache`) and the plan panel's danger-treated Confirm (a rollback, or since 1.4.0 a forced plan) are not in it, so in high contrast each is told from the control beside it by its label alone. The active sidebar tab has the same problem by another route: it carries `aria-current="page"`, and the outline rule matches `'true'`. All of it is audit backlog U45, deferred to a High Contrast pass done by hand.
- Destructive confirms (`Force latest`, uninstall with breakage, PEP 668 override, and — since P5 — `Fix with ruff`, the only one that writes outside an environment) use `--color-danger` primary buttons and require the dialog's default focus to be **Cancel**. The PEP 668 override was on this list while it was a bare checkbox with no confirm at all; it has been a `PdDialog` since 1.4.0. **A destructive control carries `data-destructive`**, and under forced-colors `styles.css` gives every button with it a 2 px border, because high contrast drops every tint and a destructive primary that looks like Cancel is worse than no colour at all. Until 1.5.0 the stylesheet kept its own list of five `data-action` values instead, and the list was never complete: the uninstall dialog's plain *Remove*, the *Force latest* inline confirm, the override's *Allow*, Disk usage's *Clear* confirm and the plan panel's danger-treated Confirm (a rollback, or a forced plan) were not on it, so in high contrast each was told from the control beside it by its label alone (audit backlog U45). A list of names beside a list of buttons is two lists; `ui/src/destructive.test.ts` reads the source instead and fails on a button drawn in the danger colour without the attribute. The same pass fixed the active sidebar tab, which carries `aria-current="page"` under an outline rule that matched `'true'` alone. *Stop* carries the attribute too: it interrupts a run part-way, and is drawn in the danger colour for that reason.
## 8. Keyboard & accessibility
Full keyboard traversal: `Ctrl+1..9` sidebar tabs (by physical key), **`Ctrl+K` opens the command palette**, `/` focuses the Search field, `Space` toggles row selection, `Ctrl+A` select-all-visible, `Enter` primary action, `Esc` closes drawers, and **`←`/`→` move within a focused row** (P6).
Full keyboard traversal: `Ctrl+1..9` sidebar tabs (by physical key), **`Ctrl+K` opens the command palette**, `/` focuses the Search field, `Space` toggles row selection, `Ctrl+A` select-all-visible, `Enter` primary action, `Esc` closes drawers, and **`←`/`→` move within a focused row** (P6). Since 1.5.0: `←`/`→`/`Home`/`End` move between Code Health's tabs, the arrow keys move between a conflict's three choices, and `Ctrl` `+`/`-`/`0` zoom. [`ACCESSIBILITY.md`](../ACCESSIBILITY.md) is the user-facing statement of this section, with what has and has not been tested; About links to it.
**Four rules from 1.4.0:**
@@ -441,8 +441,38 @@ A dialog — `PdDialog`, and the palette — returns focus to whatever opened it
to fall to `<body>`, and a keyboard user lost their place in a 200-row table. The package grid itself
is focusable but not a tab stop: the row is.
**Five rules from 1.5.0**, the accessibility pass:
- **Focus moves whenever the screen is replaced, not only when the tab changes.** The shell focused
the new screen's heading on a `nav` change and on nothing else — but the plan panel and each of
its phases, the dependency view and an opened environment all replace what `<main>` shows without
changing `nav`, and each unmounts the control that was just pressed. Focus fell to `<body>`. A
second effect in `App.tsx` covers them, and **acts only when focus was actually lost**: a run
advancing from `resolving` to `preview` must not pull a keyboard user off *Back*, and an open
modal owns focus until it closes. The console drawer returns focus to its opener the same way,
and the legal gate — rendered instead of the shell — focuses its own heading.
- **An accessible name contains what is on screen** (WCAG 2.5.3). Health's tabs were named by an
`aria-label` reading "Dependencies, 3 findings" over a tab that says `deptry 3`. The name is the
content now: the tool, its count, then what the tab is about, visually hidden. A `PdDialog` is
named by its heading, followed by what it is about, and described by its body — it was named by
the package alone, so a reader heard "numpy, dialog" and never the question.
- **A composite widget is one tab stop.** Health's tabs follow the tabs pattern (one stop, arrows,
a `tabpanel`), and a conflict's three choices follow the radio group's — with one deliberate
difference: **the arrows move focus and choose nothing.** Checking whatever focus lands on would
open *Force latest*'s destructive confirm from an arrow key.
- **What a chip means is text, not a tooltip.** A `title` on a `<span>` that cannot take focus is
reachable by a pointer and by nothing else; a held pin read as a bare version number.
- **A status region exists before its first message.** Search's is mounted from the first render
and carries "preparing", "searching", the result count and "nothing matches". A live region
announces changes to itself, so one that arrives together with its text has nothing to differ
from. Several older regions still mount with their text; whether a reader says them is in the
Audit backlog, because only a reader can answer it.
**Zoom is on since 1.5.0** (`zoomHotkeysEnabled`, which on Windows is WebView2's own zoom control,
so it needs no permission and no code). The zoom level is the webview's and is not persisted.
**The arrow keys are not decoration, and the gap they close was real.** Making the row the only tab stop is what keeps 200 rows from becoming 600 — but every control inside one is `tabIndex={-1}`, and that left *Pin* and *Remove* reachable by mouse only: a WCAG 2.1.1 failure, found by tabbing to a row in the running app and discovering there was nowhere further to go. `←`/`→` are the ARIA grid pattern's roving tabindex, `Esc` returns focus to the row, and no tab stops are added.
**`Enter` on a row is the *non-destructive* primary.** On a package row that is pin, never uninstall: a row has one reversible annotation and one irreversible removal, and a destructive operation one keypress from a focused row is an accident waiting rather than a primary action. Everywhere else in the app `Enter` needs no binding at all, because every other primary action is a real `<button>`.
**"Select-all-visible" means the current filtered set, not the rendered window.** Resolved in S2: the package table is virtualized, so only ~25 of a 200-package environment are in the DOM at any moment and "visible" would otherwise mean whatever the scroll position happens to be. `Ctrl+A` selects every *selectable* row in the set the screen is showing — so on Updates that is the outdated rows, and pinned rows are excluded there as they are from the *Select all* button. The row, not its checkbox, is the tab stop and the target of `Space`; tabbing through two controls per row is not traversal at 200 rows. Contrast: all text tokens meet WCAG AA on their surfaces, and since 1.4.0 so does every badge's text on its own tint over every surface (§2; both verified in the design-token test); focus ring 2 px accent, never removed. Screen-reader labels on all icon buttons; live region announces execution progress summaries ("13 of 15 complete"). Windows high-contrast mode: tokens fall back to system colors.
**"Select-all-visible" means the current filtered set, not the rendered window.** Resolved in S2: the package table is virtualized, so only ~25 of a 200-package environment are in the DOM at any moment and "visible" would otherwise mean whatever the scroll position happens to be. `Ctrl+A` selects every *selectable* row in the set the screen is showing — so on Updates that is the outdated rows, and pinned rows are excluded there as they are from the *Select all* button. The row, not its checkbox, is the tab stop and the target of `Space`; tabbing through two controls per row is not traversal at 200 rows. Contrast: all text tokens meet WCAG AA on their surfaces, and since 1.4.0 so does every badge's text on its own tint over every surface (§2; both verified in the design-token test); focus ring 2 px accent, never removed — and since 1.5.0 a package row's ring is drawn *inside* the row in every mode, because a ring 2 px outside a row that is absolutely positioned in a scroller and stacked against its neighbours was clipped on three sides. Screen-reader labels on all icon buttons; live region announces execution progress summaries ("13 of 15 complete"). Windows high-contrast mode: tokens fall back to system colors. **Structure is held by axe-core** over every screen (`ui/src/a11y.test.tsx`, TESTING L3) — which checks roles, names and required parts, and cannot check speech, forced-colors or focus order.
+1 -1
View File
@@ -461,7 +461,7 @@
"docsHash": "Legal documents",
"docsHashDetail": "Your acceptance is recorded against this value. Editing any of the documents changes it, and the acceptance screen appears once more on the next launch.",
"aiTitle": "How this was built",
"aiBody": "PipDock was written with substantial help from an AI coding assistant — Claude Opus 5, and from 1.4.0 Claude Opus 5.5, made by Anthropic — under human review. It wrote source code, tests and translations. The maintainer decides what ships: through 1.3.0 they read and merged every change themselves, and 1.4.0 was released by the assistant on their written instruction, once its checks had passed. Copyright and the GPL-3.0-only licence are unchanged.",
"aiBody": "PipDock was written with substantial help from an AI coding assistant — Claude Opus 5, then Claude Opus 5.5 for 1.4.0 and Claude Fable 5.2 for 1.5.0, made by Anthropic — under human review. It wrote source code, tests and translations. The maintainer decides what ships: through 1.3.0 they read and merged every change themselves, and 1.4.0 and 1.5.0 were released by the assistant on their written instruction, once the checks had passed. Copyright and the GPL-3.0-only licence are unchanged.",
"aiRead": "Read the full disclosure",
"openRepo": "Open the repository",
"reopen": "Show the documents again",
+1 -1
View File
@@ -419,7 +419,7 @@
"docsHash": "Tài liệu pháp lý",
"docsHashDetail": "Việc bạn chấp nhận được ghi lại kèm giá trị này. Sửa bất kỳ tài liệu nào cũng làm nó đổi, và màn hình chấp nhận sẽ hiện lại một lần ở lần mở tiếp theo.",
"aiTitle": "Ứng dụng này được làm ra thế nào",
"aiBody": "PipDock được viết với sự hỗ trợ đáng kể của một trợ lý lập trình AI — Claude Opus 5, và từ 1.4.0 là Claude Opus 5.5, do Anthropic phát triển — dưới sự rà soát của con người. Nó viết mã nguồn, kiểm thử và bản dịch. Người bảo trì quyết định những gì được phát hành: tới 1.3.0, họ tự đọc và hợp nhất mọi thay đổi; bản 1.4.0 do trợ lý phát hành theo chỉ thị bằng văn bản của họ, sau khi các bước kiểm tra đã đạt. Bản quyền và giấy phép GPL-3.0-only không thay đổi.",
"aiBody": "PipDock được viết với sự hỗ trợ đáng kể của một trợ lý lập trình AI — Claude Opus 5, ở 1.4.0 là Claude Opus 5.5 và ở 1.5.0 là Claude Fable 5.2, do Anthropic phát triển — dưới sự rà soát của con người. Nó viết mã nguồn, kiểm thử và bản dịch. Người bảo trì quyết định những gì được phát hành: tới 1.3.0, họ tự đọc và hợp nhất mọi thay đổi; bản 1.4.0 và 1.5.0 do trợ lý phát hành theo chỉ thị bằng văn bản của họ, sau khi các bước kiểm tra đã đạt. Bản quyền và giấy phép GPL-3.0-only không thay đổi.",
"aiRead": "Đọc bản công bố đầy đủ",
"openRepo": "Mở kho mã nguồn",
"reopen": "Xem lại các tài liệu",