content(accessibility): add Redundant entry (WCAG 2.2 SC 3.3.7)#43
Merged
Merged
Conversation
New spec page documenting WCAG 2.2 Success Criterion 3.3.7 Redundant Entry (Level A): information already entered earlier in the same process must be auto-populated or selectable rather than re-typed, subject to the essential / security / expired exceptions. Status `recommended` — WCAG conformance, not a platform-breaking contract. Wires relatedSlugs on accessible-authentication, form-errors, form-labels, and mobile-form-inputs; adds a changelog entry; regenerates the two count-driven OG images plus the new per-page OG. Found by the daily standards scan: we cover WCAG 2.2 SC 3.3.8/3.3.9 but not 3.3.7. Source: W3C WCAG 2.2 Understanding 3.3.7. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
545e533
|
| Status: | ⚡️ Build in progress... |
…ant-entry-wcag337-2026-06-18 # Conflicts: # public/og-default.png
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
1 participant
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
Adds a new spec page, Redundant entry, documenting WCAG 2.2 Success Criterion 3.3.7 Redundant Entry (Level A): information a user already entered (or was given) earlier in the same process must be auto-populated or available to select, not typed again — subject to the three normative exceptions (essential, required for security, no longer valid).
Also:
relatedSlugson the four adjacent form/auth pages (accessible-authentication,form-errors,form-labels,mobile-form-inputs).addedchangelog entry.Why now
Daily standards scan. The spec already covers WCAG 2.2 SC 3.3.8 / 3.3.9 (Accessible Authentication) but had no page for 3.3.7, a Level A criterion that applies to virtually every multi-step form, signup, and checkout. Two sibling WCAG 2.2 gaps were found in the same scan and flagged separately (see below) rather than bundled here — one topic per PR.
Status justification
recommended, notrequired. WCAG conformance is a strong "a modern site should do it" signal, but the web-platform contract does not break without it, so per the repo's status discipline it staysrecommended(matchingaccessible-authentication).Primary source
Verification
astro check→ 0 errors, 0 warnings.astro build→ 160 pages, exit 0. Page renders at/spec/accessibility/redundant-entry/, the.mdendpoint builds, and it appears in/llms.txtand/checklist/.Draft — for maintainer review, not auto-merge.
🤖 Generated with Claude Code