Repository navigation
Frame meets WCAG 2.2 AA on four criteria it failed - #93
Merged
Merged
Conversation
…1 address border, a visible home focus ring, Tab reaches GitHub and share - 2.1.4: the spec panel no longer toggles on "." alone; its link and Escape remain. - 1.4.11: the address field's border is the muted foreground, 3:1 or more on the chrome. - 2.4.7: the home link draws its focus ring on itself. - 2.1.1: Tab out of the address ends editing first, so GitHub and share are reachable. frame.lock resealed for the three changed files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QT5NNFBXXmoeroHvT
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3QT5NNFBXXmoeroHvT
afflom
pushed a commit
to afflom/me
that referenced
this pull request
Nov 15, 2026
…ata, each enforced as the register says WCAG 2.2: all 55 success criteria at A and AA from W3C's wcag.json (pinned by SHA-256), each mapped to the check that holds it: axe-core 4.10.3 rules, a verified not-applicable (nothing on any screen matches), a probe following W3C's test procedure, or the review-before-send suite. WAI-ARIA 1.2: all 142 roles, states and properties from the Recommendation, each kind enforced alike (enforcedByKind, a fallback the gate now reads). test/page/standards.test.mjs runs exactly the register's checks. Four criteria fail only in the canonical frame and are listed as failing with why: UOR-Foundation/template#93 fixes them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3LnihjghMFtJj7tkWm
…me-sync --lock Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3PGsfg89X6ENdzMWQQ
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3PGsfg89X6ENdzMWQQ
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.
What changes
Four WCAG 2.2 AA failures, found on a page built from this frame with W3C's own test procedure for each criterion:
site/app.mjs, the spec panel no longer toggles on "." alone. Its link and Escape still work.--field-borderis now--muted-foreground, which is 3:1 or more on the chrome.#homenow draws its focus ring on itself.#githuband#share, because editing hid them. Now Tab forward ends editing first, so both are reachable.frame.lockis resealed for the three changed files.Checks
The
site/worker.test.mjsresults are identical on main and on this branch. The fullvalidategate needs the digest-selected PrismPM SDK, so it runs in CI.Generated by Claude Code