@kenkaiiii/ggcoder 5.20.3 → 5.20.5

package/assets/skills/evidence-led-ui/LICENSES.md

@@ -44,6 +44,18 @@ The following works informed research comparisons. Their source text, assets, da
 - Status checked 2026-07-13: W3C Recommendation, 12 December 2024
 - Use here: linked accessibility conformance floor; W3C text is not redistributed.
 
+### WCAG2ICT
+
+- Source: https://www.w3.org/TR/wcag2ict-22/
+- Status checked 2026-07-21: W3C Group Note; informative guidance for applying WCAG 2 Level A and AA to non-web software.
+- Use here: linked native-software accessibility guidance; W3C text is not redistributed.
+
+### U.S. Department of Justice ADA web and mobile accessibility guidance
+
+- Sources: https://www.ada.gov/resources/web-guidance/ and https://www.ada.gov/resources/2024-03-08-web-rule/
+- Status checked 2026-07-21: current DOJ guidance and Title II rule fact sheet.
+- Use here: legal-context and equal-access boundary only; no source text is redistributed and no legal-compliance conclusion is inferred.
+
 ### WCAG 3.0
 
 - Source: https://www.w3.org/TR/wcag-3.0/

package/assets/skills/evidence-led-ui/SKILL.md

@@ -25,10 +25,13 @@ Apply these on every UI task. Read `references/craft-rulings.md` when implementi
 - **No edge-hugging control icons:** Select, dropdown, and combobox chevrons and other trailing icons need a deliberate inline-end inset plus enough reserved text padding for the icon and gap. They must never touch the control edge or overlap content; use logical properties so the anatomy also works in RTL.
 - **Reuse first:** Search for existing components, variants, tokens, utilities, icon wrappers, focus rings, and motion curves before creating new ones.
 - **Purposeful feedback:** Relevant hover, focus, press, selected, expanded, loading, success, and error states need clear feedback. Avoid abrupt changes when a short transition improves continuity.
+- **No soft semantic tint-on-tint:** Do not default badges, buttons, toasts, cards, selected states, or icon medallions to a low-opacity semantic-color background with saturated same-hue text or icons, with or without a matching border. Unless the user explicitly requests that treatment or an established system must be preserved, choose a product-specific alternative rather than imposing one universal replacement style.
 - **No sticky pointer focus:** Clicking or tapping must not leave a focus ring, highlighted border, shadow, background, or container `:focus-within` treatment stuck after the interaction ends, a native popup closes, or the user clicks elsewhere. Preserve immediate, visible keyboard focus by distinguishing input modality instead of suppressing focus globally.
 - **No generic hover lift:** Do not default to `translateY`, bobbing, floating, or scale-up on hover. Prefer color, border, underline, icon fill, opacity, or restrained shadow changes.
 - **No `transition: all`:** Name transition properties, reuse duration/easing tokens, and provide a reduced-motion path.
 - **Intentional type:** Reuse the existing type system. For net-new web work, select an appropriate modern family or pairing; do not use Arial, Helvetica, or bare `system-ui` as the aesthetic direction.
+- **WCAG 2.2 Level AA is the accessibility floor:** Every web UI and complete user flow must meet every applicable Level A and Level AA success criterion, not a hand-picked subset. Native apps apply WCAG2ICT where relevant plus current platform accessibility requirements. Stricter project, contract, platform, or jurisdiction rules win; accessibility cannot be traded for aesthetics, scope, delivery speed, or a higher rubric score.
+- **No unsupported accessibility claims:** Treat ADA as an equal-access legal obligation, not a badge earned by Lighthouse, axe, or another scanner. Never label a UI `ADA compliant` or `WCAG conformant` from source review or automated checks alone; a claim requires a defined scope, per-criterion evidence, manual keyboard and assistive-technology testing, and qualified legal or product-owner review when legal compliance is asserted.
 - **Measured contrast:** Meet WCAG 2.2 contrast for text, controls, icons, focus, and meaningful graphics. Muted text must remain readable.
 - **Consistent flow:** Repeated navigation and actions keep the same order, labels, icons, placement, and behavior across sections and pages.
 - **No generated em dashes:** Do not write em dashes in user-facing UI copy unless explicitly requested or exact supplied source text must remain unchanged.
@@ -38,7 +41,7 @@ Apply these on every UI task. Read `references/craft-rulings.md` when implementi
 Resolve every path from the installed skill root. Load only what the task needs:
 
 - `references/craft-rulings.md`: implementation detail for the binding defaults above.
-- `references/production-contract.md`: pass/fail semantics, forms, accessibility, performance, resilience, platform, trust, AI, media, theme, and release checks. Read it for broad features, behavior changes, forms, navigation, data/AI interfaces, native work, performance work, or release review.
+- `references/production-contract.md`: binding pass/fail semantics, WCAG/ADA accessibility, forms, performance, resilience, platform, trust, AI, media, theme, and release checks. Read its accessibility sections for every implemented or reviewed UI; read the full contract for broad features, behavior changes, forms, navigation, data/AI interfaces, native work, performance work, or release review.
 - `references/archetypes.md`: surface-specific direction and relevant source slugs. Read for net-new UI, redesigns, or unresolved visual direction.
 - `references/observed-patterns.md`: measured corpus observations. Read only sections that answer a real design question.
 - `references/anti-defaults.md`: transferable AI-generated patterns to challenge. Read for broad visual work or generic-looking output.
@@ -93,7 +96,7 @@ One thesis leads. Do not combine several aesthetic directions into a mood-board
 
 ### 5. Run the anti-default check
 
-For broad visual work, read `references/anti-defaults.md`. Flag emoji UI, mixed icon families, arbitrary misalignment, duplicated local styling, abrupt interaction, generic hover lift, generic type, generated em dashes, centered gradient heroes, glass cards, equal card grids, decorative eyebrows, random metric blocks, ubiquitous pills, dark-premium assumptions, fake terminals, floating screenshots, bento layouts, ambient motion, icon medallions, and invented proof.
+For broad visual work, read `references/anti-defaults.md`. Flag emoji UI, mixed icon families, arbitrary misalignment, duplicated local styling, abrupt interaction, generic hover lift, soft semantic tint-on-tint treatments, generic type, generated em dashes, centered gradient heroes, glass cards, equal card grids, decorative eyebrows, random metric blocks, ubiquitous pills, dark-premium assumptions, fake terminals, floating screenshots, bento layouts, ambient motion, icon medallions, and invented proof.
 
 Keep a flagged pattern only after completing: **“This belongs because…”** with a product-specific reason. Replace choices that could survive unchanged in an unrelated product.
 
@@ -106,9 +109,10 @@ Plan only relevant states, but include the complete primary path and recovery:
 - keyboard order, accessible names/status, overlay focus, and drag alternatives;
 - pointer-versus-keyboard focus behavior, including native popup dismissal and clicks onto non-focusable space;
 - narrow, intermediate, desktop, wide/resizable, pointer, touch, and no-hover behavior;
-- reduced motion, forced colors, zoom/reflow, long/localized/RTL text, missing media, and realistic data extremes.
+- reduced motion, forced colors, zoom/reflow, long/localized/RTL text, missing media, and realistic data extremes;
+- text alternatives and media equivalents, landmarks/headings, language, labels/instructions/errors, status announcements, timing, flashing, and sensory-independent instructions where applicable.
 
-For broad behavior, forms, navigation, native, data/AI, performance, or release work, read and apply `references/production-contract.md`. A visual score cannot compensate for a relevant contract failure.
+For every UI, read and apply the accessibility sections of `references/production-contract.md`. For broad behavior, forms, navigation, native, data/AI, performance, or release work, apply the full contract. A visual score cannot compensate for a relevant contract failure.
 
 ### 7. Document broad work
 
@@ -118,7 +122,7 @@ For a broad page, multi-screen feature, or redesign, create or update `DESIGN.md
 
 Use real project content and data. Label fixtures honestly. Never invent testimonials, customer logos, ratings, metrics, or claims as fact.
 
-Reuse dependencies and primitives. Use one coherent icon system. Maintain semantic controls, visible keyboard focus, keyboard operation, measured contrast, readable line lengths, stable adaptive layout, and reduced-motion support. Pointer interaction must not leave a false focus, active, or selected-looking highlight behind. Implement the complete planned flow, not only its first screenshot.
+Reuse dependencies and primitives. Use one coherent icon system. Meet every applicable WCAG 2.2 Level A and AA criterion across the complete flow, including its states and responsive variants. Maintain semantic controls, visible keyboard focus, keyboard operation, assistive-technology output, measured contrast, readable line lengths, stable adaptive layout, and reduced-motion support. Pointer interaction must not leave a false focus, active, or selected-looking highlight behind. Implement the complete planned flow, not only its first screenshot.
 
 The representative initial state must keep decision-critical information and the primary action visible or one obvious action away on desktop and mobile. Preserve selected context through master-detail recomposition. Keep demo, debug, and state-switching controls subordinate and non-obscuring.
 
@@ -128,7 +132,7 @@ Capture representative desktop and narrow/mobile output. Score broad work with `
 
 Default to one critique-and-revision cycle. Run another only when evidence still fails the score or production gate. If a check is unavailable, report it as unverified instead of looping or substituting more polish.
 
-Broad work is complete at **20/24 or higher**, with no zero in accessibility, consistency and flow, responsive behavior, state completeness, or content authenticity, and only after applicable production checks pass. A small component must score 2 on every applicable quality-floor criterion.
+Broad work is complete at **20/24 or higher**, with no zero in accessibility, consistency and flow, responsive behavior, state completeness, or content authenticity, and only after applicable production checks pass. Any applicable WCAG Level A or AA failure blocks completion regardless of score. A small component must score 2 on every applicable quality-floor criterion and pass its accessibility contract checks.
 
 ## Review-only mode
 

package/assets/skills/evidence-led-ui/references/anti-defaults.md

@@ -3,7 +3,7 @@
 ## Contents
 
 - Purpose and review method
-- Template composition: centered gradient hero, glass cards, equal card grids, eyebrows, metric blocks, pills, dark-premium assumptions, huge type, fake terminals, floating screenshots, and bento layouts
+- Template composition: centered gradient hero, glass cards, equal card grids, eyebrows, metric blocks, pills, soft semantic tint-on-tint treatments, dark-premium assumptions, huge type, fake terminals, floating screenshots, and bento layouts
 - Decoration and truth: ambient motion, icon medallions, false authenticity, emoji, and mixed icon language
 - Craft regressions: generic hover lift, abrupt states, accidental misalignment, reimplemented local styling, generic type, and generated em dashes
 - Final anti-default review
@@ -62,6 +62,14 @@ For every flagged pattern, write one sentence: **“This belongs because…”**
 
 **Legitimate when:** The project already uses an orbital/capsule motif, a control’s variable label length needs it, or tactile consumer friendliness is a deliberate material rule.
 
+## Soft semantic tint-on-tint
+
+**AI tell:** Badges, buttons, toasts, cards, selected states, status rows, and icon medallions repeatedly use low-opacity semantic-color backgrounds with saturated same-hue text or icons, sometimes with a matching border. Component libraries often name this formula `soft`, `subtle`, `surface`, or `tonal`.
+
+**Default action:** Replace the formula, then derive the new treatment from the product's actual aesthetic and component role. A neutral surface with one semantic marker, a solid fill with neutral high-contrast text, monochrome styling, product accent, typography, or another coherent local material model can work; none is the universal replacement.
+
+**Legitimate when:** The user explicitly requests tint-on-tint or exact reuse of an established design-system variant is required by scope. Unlike most patterns in this file, this is a binding craft default rather than a pattern justified by generic claims such as `clean`, `friendly`, or `modern`.
+
 ## Dark equals premium
 
 **AI tell:** Near-black canvas, purple glow, thin gray borders, and muted text chosen without product evidence.

package/assets/skills/evidence-led-ui/references/craft-rulings.md

@@ -154,6 +154,14 @@ Never use faint light-gray text on white, faint dark-gray text on black, or low-
 - Aim above the minimum for small, thin, long-form, or mission-critical text. Verify computed colors rather than judging from a screenshot alone.
 - Do not use color as the only status cue. Pair color with text, shape, icon, or pattern.
 
+### No soft semantic tint-on-tint
+
+Do not default badges, buttons, toasts, alerts, cards, selected states, status rows, or icon medallions to the familiar `soft`, `subtle`, `surface`, or `tonal` formula: a low-opacity red, green, amber, blue, or purple background paired with saturated same-hue text or icons, often finished with a same-hue border. The border is optional; the same-hue tinted surface plus same-hue foreground is the rejected pattern.
+
+Choose the replacement from the product's existing aesthetic and the component's role. Viable directions include a neutral surface with an isolated semantic icon, dot, or edge; a solid semantic fill with neutral high-contrast text; monochrome treatment; a product accent; plain typography; or another coherent local material model. These are options, not a new house style. Preserve hierarchy, measured contrast, and a non-color cue for status.
+
+Retain tint-on-tint only when the user explicitly asks for it or exact reuse of an established design-system variant is required by scope. Existing examples are evidence to inspect, not permission to spread the treatment into new component families.
+
 ## 7. Consistency and flow
 
 A polished interface feels like one system from section to section, component to component, and page to page.
@@ -187,5 +195,6 @@ Before calling UI work complete, verify:
 - reduced motion preserves state meaning;
 - typography is intentional, loaded efficiently, and stable during fallback;
 - all text and meaningful non-text contrast is measured;
+- no soft semantic tint-on-tint treatment was introduced without an explicit user request or required existing-system match;
 - repeated navigation/actions remain consistent across sections and pages;
 - generated UI copy contains no em dashes unless explicitly allowed.

package/assets/skills/evidence-led-ui/references/production-contract.md

@@ -3,7 +3,7 @@
 ## Contents
 
 1. Semantics and interaction architecture
-2. Accessibility beyond contrast
+2. WCAG and ADA accessibility conformance
 3. Forms, errors, and user control
 4. Responsive and international resilience
 5. Performance and visual stability
@@ -24,20 +24,32 @@ This is a binding, pass/fail quality floor for implemented web and native UI. Ap
 - Modal work uses the platform dialog primitive when suitable; non-modal top-layer content uses the Popover API when suitable. Manage initial focus, containment for modal UI, Escape/close behavior, background inertness, and focus return. A popover does not automatically supply menu or dialog semantics.
 - Preserve browser and platform navigation. Meaningful destinations and shareable state need stable URLs or routes; Back, Forward, refresh, deep links, and native back behavior must not discard work or trap the user.
 
-## 2. Accessibility beyond contrast
+## 2. WCAG and ADA accessibility conformance
 
-WCAG 2.2 Level AA is the web conformance floor. Project, platform, legal, or contractual requirements may be stricter.
+WCAG 2.2 Level AA is the default technical floor for web UI. Conformance means every applicable Level A and Level AA success criterion across full pages, complete processes, responsive variants, and all relevant states, not a selected checklist of visible issues. Native apps apply WCAG2ICT where relevant plus current platform accessibility requirements. Any stricter project, procurement, contract, platform, or jurisdiction requirement wins.
 
-- Keep a visible focus indicator and ensure sticky headers, footers, cookie bars, drawers, and overlays do not obscure the focused control.
+ADA is a civil-rights and equal-access obligation, not a technical certification. WCAG 2.2 Level AA is the engineering baseline, but meeting it does not by itself establish full ADA compliance. When ADA applies, verify the current Title II or Title III obligations, scope, exceptions, effective-communication duties, and alternative arrangements with the responsible product or legal owner. Never claim `ADA compliant` or `WCAG conformant` without evidence for a defined scope.
+
+- Define the conformance scope before broad implementation: routes/screens, complete user processes, content types, components and states, supported technologies, and the browser, device, input, and assistive-technology matrix. Audit against the current official [WCAG 2.2 Quick Reference](https://www.w3.org/WAI/WCAG22/quickref/), criterion by criterion; this summary is not a substitute. Track every applicable Level A and AA criterion as pass, fail, or not applicable with a rationale and evidence.
+- Satisfy all five WCAG conformance requirements: the claimed level, full pages, every page in each complete process, only accessibility-supported uses of technology, and non-interference from any non-conforming content. One unresolved applicable failure blocks conformance.
+- Use native semantics and controls first. Supply meaningful text alternatives for informative images, controls, and graphics; mark decoration as decorative. Preserve programmatic information and relationships, headings, landmarks, lists, tables, meaningful sequence, page and passage language, reading order, and a bypass route for repeated blocks.
+- Provide the required alternatives for every prerecorded or live media type, including synchronized captions, transcripts or equivalent alternatives, and audio description where the criterion requires it. Autoplaying audio needs an immediate pause, stop, or independent volume control. Do not use images of text when styled real text can communicate the same information.
+- Give every page or screen a descriptive title. Link purpose must be clear in context; headings and labels describe topic or purpose; users have more than one way to locate pages when required. Keep repeated navigation, component identification, and help mechanisms consistent.
+- Every function works by keyboard without a trap or timing race. Focus order follows meaning; focus is visible, not obscured, and restored after overlays. Keyboard shortcuts, character-key commands, and custom composite widgets follow the applicable WCAG and WAI-ARIA keyboard requirements.
 - Pointer activation, native popup dismissal, and clicks elsewhere must not leave a focus ring, highlighted border, shadow, background, or container focus treatment stuck as a false selected or active state. Distinguish pointer from keyboard focus and distinguish focus from genuine selected, expanded, and error states; never suppress visible keyboard focus globally.
+- Meet WCAG 2.2 contrast and appearance criteria in every theme and state: at least 4.5:1 for normal text, 3:1 for large text, and 3:1 for meaningful non-text controls, state indicators, focus cues, and graphics where the criterion applies. Never use color, shape, position, sound, motion, or another single sensory cue as the only instruction or status signal.
+- Content revealed by hover or focus must be dismissible, hoverable, and persistent where required. Text spacing overrides must not break content. Audio, animation, and visual effects cannot make text unreadable or block operation.
 - WCAG 2.2 Target Size (Minimum) is 24 by 24 CSS pixels with defined exceptions. Default touch-oriented web controls to a 44 by 44 CSS-pixel hit area where layout permits. Native work follows its platform target guidance, such as 44 by 44 points on Apple platforms and 48 by 48 density-independent pixels in Material guidance.
-- Provide a single-pointer alternative for every non-essential drag interaction. Reordering also needs keyboard and assistive-technology operation.
-- Do not require users to re-enter information already supplied in the same process when it can be selected or populated. Preserve data across validation errors and recoverable navigation.
-- Authentication must work with password managers, copy/paste, and accessible alternatives. Do not make memory, transcription, puzzles, or blocked paste the only route unless an applicable exception is verified.
-- Announce important asynchronous status and validation changes without moving focus unnecessarily. Do not rely on color, motion, position, or an icon alone to communicate meaning.
-- Verify text resizing to 200%, reflow at 320 CSS pixels where WCAG applies, keyboard operation, reduced motion, and forced-colors/high-contrast behavior.
+- Provide a single-pointer alternative for every non-essential drag interaction. Reordering also needs keyboard and assistive-technology operation. Do not require path-based gestures, multipoint gestures, or device motion when a simpler accessible input can perform the task. Support pointer cancellation, and ensure an accessible name contains the visible label so speech-input users can target the control.
+- Give every control a programmatic name that includes its visible label, and expose role, value, state, instructions, requirements, and errors correctly. Announce important asynchronous status and validation changes without moving focus unnecessarily. Do not over-announce streaming or frequently updating content.
+- Do not trigger an unexpected context change merely on focus or input. Identify common input purposes programmatically, make required fields and formats explicit, identify errors in text, suggest corrections when known, and prevent or confirm consequential legal, financial, test, and data changes where WCAG requires it.
+- Preserve use at 200% text resize and at 320 CSS-pixel reflow where WCAG applies, without loss, overlap, two-dimensional scrolling except for allowed content, or essential truncation. Support required orientation, browser zoom, text spacing, reduced motion, forced colors/high contrast, and user font or platform text scaling.
+- Users can pause, stop, hide, extend, or adjust time limits and moving, blinking, auto-updating, or autoplaying content where required. Do not ship content that violates flash thresholds. Reduced-motion alternatives preserve information and task completion.
+- Do not require users to re-enter information already supplied in the same process when it can be selected or populated. Preserve data across validation errors and recoverable navigation. Authentication must work with password managers, copy/paste, and accessible alternatives; memory, transcription, puzzles, or blocked paste cannot be the only route unless an applicable exception is verified.
+- Include first-party, embedded, vendor-supplied, document/PDF, and authenticated content in scope unless a verified legal and standards exception applies. An exception does not erase ADA duties for effective communication, reasonable modification, or equal access; route those decisions to the responsible legal or product owner.
+- Accessibility overlays, injected widgets, and a separate `accessible version` do not substitute for fixing the primary experience. Use an alternate route only when the governing standard and law permit it and it provides genuinely equivalent, current information and functionality. Provide a discoverable way to report accessibility barriers when the product has a public support or feedback surface.
 
-Automated accessibility tooling is a defect detector, not proof of conformance. Manual keyboard, focus, zoom/reflow, and assistive-technology checks remain required for relevant flows.
+Automated accessibility tooling is a defect detector, not proof of conformance. Run the project's scanner, then manually verify semantics, keyboard use, focus, zoom/reflow, contrast, media alternatives, and representative assistive-technology output across the primary flow and high-risk states. Record the tested tool/browser/assistive-technology combinations. Unavailable checks remain `unverified`, never silently pass, and block a conformance claim.
 
 ## 3. Forms, errors, and user control
 
@@ -78,6 +90,7 @@ For web surfaces, use current Core Web Vitals as the shared target at the 75th p
 ## 7. Tokens and component contracts
 
 - Reuse the host system first. For a net-new scalable system, separate primitive values from semantic roles and component tokens; define modes without duplicating meaning.
+- Do not introduce soft semantic tint-on-tint as the default status variant: low-opacity semantic backgrounds paired with saturated same-hue text or icons, with or without matching borders. Derive a replacement from the host aesthetic and preserve non-color status cues; retain the treatment only when explicitly requested or exact established-system reuse is required.
 - The Design Tokens Community Group 2025.10 format is a stable interoperability option, not a W3C Standard and not a mandatory migration target. Use it only when tools need a portable source of truth.
 - Each shared component documents anatomy, semantic element, variants, sizes, content limits, states, keyboard behavior, responsive behavior, and accessibility name/description rules.
 - Keep one source of truth. Generated platform outputs must not become competing hand-edited token stores.
@@ -110,14 +123,18 @@ For web surfaces, use current Core Web Vitals as the shared target at the 75th p
 
 For every broad implementation, record:
 
-1. representative desktop and narrow/mobile renders, plus native/adaptive sizes when applicable;
-2. primary-flow keyboard completion, visible focus, focus return, and no obscured focus;
-3. project accessibility-tool output plus manual semantics and status review;
-4. 200% text, 320 CSS-pixel reflow where applicable, longest content, and one localization stress case;
-5. reduced-motion and forced-colors/high-contrast results where supported;
-6. loading, empty, error, retry, disabled, success, destructive, and offline/slow-network states that apply;
-7. route, refresh, deep-link, Back/Forward or native-back behavior that applies;
-8. measured performance evidence or an explicit unverified item with the exact missing measurement;
-9. the project's supported browser, device, and input matrix.
-
-A small component records only applicable evidence, but semantics, keyboard/focus, content extremes, and relevant states cannot be skipped. Report contract failures plainly and fix them before calling broad UI work complete.
+1. the defined accessibility conformance scope plus a WCAG 2.2 Level A/AA criterion matrix or an explicit changed-scope audit with pass, fail, and justified not-applicable results;
+2. representative desktop and narrow/mobile renders, plus native/adaptive sizes when applicable;
+3. primary-flow keyboard completion, visible focus, focus return, no traps, and no obscured focus;
+4. project accessibility-tool output plus manual semantics, accessible-name, reading-order, media-alternative, and status review;
+5. primary-flow output from at least one representative screen-reader or native assistive-technology combination in the supported matrix;
+6. 200% text, 320 CSS-pixel reflow where applicable, browser zoom or platform text scaling, longest content, and one localization stress case;
+7. reduced-motion and forced-colors/high-contrast results where supported;
+8. loading, empty, error, retry, disabled, success, destructive, and offline/slow-network states that apply;
+9. route, refresh, deep-link, Back/Forward or native-back behavior that applies;
+10. measured performance evidence or an explicit unverified item with the exact missing measurement;
+11. a first-party, embedded, vendor, document/PDF, and authenticated-content inventory with any exception and responsible owner recorded;
+12. the accessibility-feedback route and remediation owner when the product has a public support surface;
+13. the project's supported browser, device, input, and assistive-technology matrix.
+
+A broad implementation is not complete while an applicable WCAG Level A or AA criterion is failed or unverified. A small component records only applicable evidence, but semantics, accessible naming, keyboard/focus, assistive-technology output, content extremes, and relevant states cannot be skipped. Report failures plainly and fix them before calling the UI accessible. Never turn partial evidence into an ADA-compliance or WCAG-conformance claim.

package/assets/skills/evidence-led-ui/references/provenance.md

@@ -42,12 +42,14 @@ As fetched on 2026-07-13, [`styles.refero.design/robots.txt`](https://styles.ref
 
 Therefore this skill must not bulk-scrape Refero, call undocumented Refero endpoints, or mirror its catalog. Refero may be used only through an authorized Refero MCP or a user-provided export the user is entitled to share. Live access is optional; the skill works without it.
 
-## Accessibility standards
+## Accessibility standards and ADA context
 
-- **Conformance floor:** [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/), W3C Recommendation dated 12 December 2024 in the current W3C publication fetched 2026-07-13.
+- **Web conformance floor:** [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/), W3C Recommendation dated 12 December 2024 in the current publication fetched 2026-07-21. The [W3C WCAG overview](https://www.w3.org/WAI/standards-guidelines/wcag/) encourages the latest version and states that WCAG 2.2 conformance is backward compatible with WCAG 2.1 and 2.0.
+- **Native application guidance:** [WCAG2ICT](https://www.w3.org/TR/wcag2ict-22/) explains how Level A and AA criteria apply to non-web software. It is informative guidance, not a normative standard, and native work still needs platform and product-specific accessibility requirements.
+- **U.S. ADA context:** The Department of Justice [ADA web accessibility guidance](https://www.ada.gov/resources/web-guidance/) explains equal access and effective communication under Titles II and III. The current [Title II web and mobile app rule fact sheet](https://www.ada.gov/resources/2024-03-08-web-rule/) names WCAG 2.1 Level AA as its technical standard and documents scope, exceptions, and compliance timing. These sources were checked 2026-07-21.
 - **Not the conformance target:** [W3C Accessibility Guidelines (WCAG) 3.0](https://www.w3.org/TR/wcag-3.0/) is a W3C Working Draft dated 3 March 2026. W3C says publication as a Working Draft does not imply endorsement and that it is inappropriate to cite as anything other than work in progress.
 
-Project or jurisdictional requirements may exceed this floor. Use the current official standard and product-specific accessibility requirements at implementation time.
+WCAG 2.2 Level AA is the default engineering floor because it includes and extends WCAG 2.1, but technical WCAG conformance alone does not prove compliance with the ADA or another law. Project, procurement, contractual, platform, and jurisdictional requirements may exceed this floor. Use the current official standard and obtain qualified product or legal review before making a legal-compliance claim.
 
 ## UI craft research checked 14 July 2026
 
@@ -68,11 +70,11 @@ The motion recommendations were also checked against the pinned local corpus. Se
 
 Refero content was not accessed for this update because no authorized Refero MCP or user-provided export was available. The existing Refero boundary remains unchanged.
 
-## Production-practice research checked 14 July 2026
+## Production-practice research checked 21 July 2026
 
 The pass/fail contract in `references/production-contract.md` was checked against current primary guidance:
 
-- [What's New in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) and the linked Understanding documents: focus not obscured, target size minimum, dragging alternatives, redundant entry, and accessible authentication;
+- [WCAG 2.2](https://www.w3.org/TR/WCAG22/), its [conformance requirements](https://www.w3.org/TR/WCAG22/#conformance-reqs), [How to Meet WCAG 2](https://www.w3.org/WAI/WCAG22/quickref/), and [What's New in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/): all applicable Level A and AA criteria across full pages and complete processes, plus focus not obscured, target size minimum, dragging alternatives, redundant entry, and accessible authentication;
 - [WAI-ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/) and its dialog, menu button, combobox, and keyboard-interface patterns: native semantics first and complete keyboard/focus behavior for custom composites;
 - [WAI Forms Tutorial](https://www.w3.org/WAI/tutorials/forms/): labels, grouping, instructions, validation, notifications, and accessible custom controls;
 - the [WHATWG HTML Standard for dialog](https://html.spec.whatwg.org/multipage/interactive-elements.html#the-dialog-element) and [popover](https://html.spec.whatwg.org/multipage/popover.html), plus [MDN Popover API guidance](https://developer.mozilla.org/en-US/docs/Web/API/Popover_API): modal versus non-modal top-layer behavior and the semantics authors must still provide;

package/assets/skills/evidence-led-ui/references/quality-rubric.md

@@ -48,7 +48,7 @@ Maximum: **24 points**. Ship broad UI work only at **20/24 or higher**, with no
 - **1:** Most patterns repeat, but spacing cadence, icon treatment, controls, actions, or section transitions contain visible inconsistencies.
 - **2:** Existing primitives are reused; one icon family, spacing rhythm, component anatomy, navigation order, action placement, and surface logic carry through the full flow.
 
-**Test:** Compare adjacent sections and pages side by side. Trace one repeated action through every occurrence, then inspect container edges, control heights, icon weight, spacing, borders, labels, and state behavior. For selects, dropdowns, and comboboxes, verify the trailing icon has intentional edge inset and reserved text clearance at every size, in RTL, and with the longest plausible value.
+**Test:** Compare adjacent sections and pages side by side. Trace one repeated action through every occurrence, then inspect container edges, control heights, icon weight, spacing, borders, labels, and state behavior. For selects, dropdowns, and comboboxes, verify the trailing icon has intentional edge inset and reserved text clearance at every size, in RTL, and with the longest plausible value. Flag any low-opacity semantic background paired with saturated same-hue text or icons; it fails unless the user requested it or exact established-system reuse is required.
 
 ## 5. Typography
 
@@ -84,11 +84,11 @@ Maximum: **24 points**. Ship broad UI work only at **20/24 or higher**, with no
 
 ## 9. Accessibility quality floor
 
-- **0:** Keyboard path, focus, semantics, contrast, labels, icon meaning, status, drag-only operation, or target sizes block use.
-- **1:** Basics exist but focus order/visibility, text/non-text contrast, motion, icon labels, status cues, composite-widget behavior, forced colors, or assistive naming has gaps.
-- **2:** Native semantics or verified APG behavior, visible and unobscured focus, keyboard operation, meaningful labels/status, WCAG 2.2 target minimums with platform-appropriate touch targets, reduced motion, forced colors, text contrast of at least 4.5:1 (3:1 for large text), and meaningful non-text contrast of at least 3:1 are verified.
+- **0:** Any applicable WCAG 2.2 Level A or AA criterion fails, or keyboard use, focus, semantics, contrast, labels, media alternatives, status, drag alternatives, target sizes, or assistive-technology output blocks use.
+- **1:** Basics work, but the changed-scope criterion audit is incomplete or focus order/visibility, text/non-text contrast, motion, icon labels, status cues, composite-widget behavior, forced colors, zoom/reflow, media alternatives, or assistive-technology verification has gaps.
+- **2:** The changed scope has evidence that every applicable WCAG 2.2 Level A and AA criterion passes. Native semantics or verified APG behavior, visible and unobscured focus, complete keyboard operation, meaningful names/instructions/status, media alternatives, target minimums, reduced motion, forced colors, 200% text and 320 CSS-pixel reflow where applicable, representative assistive-technology output, text contrast of at least 4.5:1 (3:1 for large text), and meaningful non-text contrast of at least 3:1 are verified.
 
-**Test:** Complete the primary task by keyboard; inspect accessible names and status; verify overlay focus and drag alternatives; measure text, icon, control, and focus contrast; run project accessibility tooling; test 200% text/reflow, `prefers-reduced-motion`, and forced colors; verify color is not the only cue.
+**Test:** Audit every applicable Level A and AA criterion for the changed scope against the official WCAG Quick Reference and all five conformance requirements. Complete the primary task by keyboard and with a representative screen reader or native assistive technology. Inspect names, roles, values, status, reading order, page and passage language, titles, link purpose, multiple navigation paths, consistent help, text/media alternatives, images of text, hover/focus content, overlay focus, context changes, timing, forms and error prevention, pointer cancellation, and gesture/drag alternatives. Measure text, icon, control, state, and focus contrast; run project accessibility tooling; test 200% text, 320 CSS-pixel reflow, zoom or platform text scaling, `prefers-reduced-motion`, and forced colors. Record pass, fail, or justified not applicable. Automated output alone never earns a pass or supports an ADA-compliance or WCAG-conformance claim.
 
 ## 10. Motion purpose
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kenkaiiii/ggcoder",
-  "version": "5.20.3",
+  "version": "5.20.5",
   "type": "module",
   "description": "CLI coding agent with OAuth authentication for Anthropic, OpenAI, and Gemini",
   "license": "MIT",
@@ -114,9 +114,9 @@
     "typescript-language-server": "^5.3.0",
     "wrap-ansi": "^10.0.0",
     "zod": "^4.4.3",
-    "@kenkaiiii/gg-agent": "5.20.3",
-    "@kenkaiiii/gg-ai": "5.20.3",
-    "@kenkaiiii/gg-core": "5.20.3"
+    "@kenkaiiii/gg-agent": "5.20.5",
+    "@kenkaiiii/gg-ai": "5.20.5",
+    "@kenkaiiii/gg-core": "5.20.5"
   },
   "optionalDependencies": {
     "@huggingface/transformers": "^3.6.0",