Repository navigation
Improve web accessibility and responsive reflow with browser evidence - #3
Merged
Merged
Conversation
tomlin7
marked this pull request as ready for review
November 4, 2026 14:46
tomlin7
added a commit
that referenced
this pull request
Nov 4, 2026
tomlin7
added a commit
that referenced
this pull request
Nov 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The web client had unassociated form labels, low-contrast text, and long names/titles that expanded a 320px viewport to thousands of pixels. This adds explicit labels, keyboard bypass and focus styling, announced feedback, navigation/filter semantics, and responsive long-content handling while retaining the existing design.
Validation: TypeScript checking and 38 local Chromium/Playwright tests passed without skips. The suite scans eight screens at four viewport widths with axe and verifies keyboard interaction, search, login recovery, registration/profile persistence, and authoring through the real Go API and isolated SQLite database. Recorded baseline: 32 repeated rule/viewport violations and 76 affected element/viewport instances; final scan: zero detected targeted-rule violations. Long-content story/reader widths changed from 2,957/10,371px to 320px. Measurements and screenshots are in docs/ui-quality.md and docs/ui-quality-results.json.
Automated results are partial coverage: 36 incomplete rule/viewport observations still need manual review, and no screen-reader or participant study is claimed. A moderator protocol and blank observation sheet are included for real user testing. A new CI workflow reruns the browser suite and uploads evidence.
Linux CI passed the full 38-test suite with no skips: https://github.com/hiroshi-os/inkwell/actions/runs/41838576627. Local Windows evidence is preserved separately in docs/ui-quality-results.json.