Repository navigation
WCAG 2.2 and WAI-ARIA 1.2 measured in full (ST-01) - #115
Merged
Merged
Conversation
…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
afflom
enabled auto-merge
November 15, 2026 10:13
afflom
pushed a commit
that referenced
this pull request
Nov 15, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3NUuCezYRx8MGGY3Ss
afflom
pushed a commit
that referenced
this pull request
Nov 15, 2026
…MANCE.md Main's ST-01 refused site/person/icf.mjs (ICF's module, #115) as answering to no standard; its register entry who-icf now governs it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3NUuCezYRx8MGGY3Ss
Contributor
|
Merging this pull request made main Refused by page / gates / Check that every part fully implements its standards: https://github.com/afflom/me/actions/runs/43705349574/job/132785116602 These are the same gates this pull request passed. If its checks ran on the same merge result, the refusal comes from a check that does not decide the same way every run: make that check deterministic in a new pull request. |
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.
Requested by Alex · project thread
Alex's rule from 09:29Z: every part fully implements its standard and is verified to enforce it. This PR moves the front end's two W3C standards from "not measured" to measured in full.
WCAG 2.2, level AA: 55 requirements, 51 enforced, 4 failing in the frame
wcag.json, pinned by SHA-256 and read bytools/standards/extract/wcag_json.py.enforcedBy:absent:selector that nothing on any screen matches, the frame's shadow root includedsite/app.mjs. They are listed underfailing, with the reason for each, and kept as debt. Frame meets WCAG 2.2 AA on four criteria it failed UOR-Foundation/template#93 fixes all four, and only Alex can merge it there.WAI-ARIA 1.2: 142 requirements, all enforced
aria_html.py.enforcedByKindfallback ingate.py, as agreed with the gates thread.What else changes
test/page/standards.test.mjsnow runs exactly the checks the register names, so the register and the suite can't drift apart. Requirements it finds failing must match the standard'sfailinglist exactly, so a fixed requirement leaves the debt.gate.pytreats a requirement listed underfailingas not enforced. It stays in the debt with its reason.These pass locally:
tools/standards/gate.py --check --base origin/main(193 of 999 requirements enforced), the standards suite on the assembled page in all four views, the product gate and the parts gate.Generated by Claude Code