# WCAG / ACT — Consolidated Completion and Outstanding Evidence Record

**As of:** 24 October 2026  
**Project:** AIWebPageSEO accessibility audit, W3C ACT implementation and saved Grabzies audit evidence  
**Method:** Consolidation of existing Library reconciliation records and browser/server output supplied in the conversation. **No new test, audit, or server change was performed to produce this document.**

## 1. Executive status

**Completed and verified within stated scope:** Production accessibility-audit frontend delivery, responsive smoke test, generated sample report and interpretation notice; saved ACT text-spacing and regression suites; saved scoped Grabzies responsive remediation checks; WCAG 2.4.1 report-classification regression; historical evidence reconciliation.

**Not established:** Full WCAG 2.2 Level A/AA conformance for Grabzies or AIWebPageSEO; a like-for-like closure test of the original Grabzies reflow finding; post-remediation closure of all eight originally flagged control-boundary contrast cases. These are evidence limitations, not instructions to repeat already completed work.

## 2. Verified work — AIWebPageSEO tool and frontend

| Work | Recorded result | Scope / limitation |
|---|---|---|
| Official ACT text-spacing examples | **38/38 matched** | Two scoped ACT rules; not all ACT rules or full WCAG conformance |
| Text-spacing regression suite | **30/30 passed** | Existing regression suite only |
| Custom-audit fixtures | **4/4 detected** | Corrected fixtures only |
| W3C readiness checks | **6/6 passed** | Publication, source integrity and recorded integration checks |
| WCAG 2.4.1 report classification | **5/5 passed** | Classification regression; not all keyboard/assistive technology behavior |
| Production frontend assets | **HTTP 200 for 4/4** | accessibility-audit.html, accessibility-audit.js, accessibility-audit.css, performance-tools.html |
| Browser responsive smoke test | **4/4 widths without horizontal overflow** | 1280, 768, 390 and 320 px on the accessibility-audit page |
| Browser report-generation smoke test | **PASS** | Sample HTML; 55 coverage entries; interpretation notice present; no page JavaScript errors |
| Sample-loading function and handler | **PASS** | Direct function invocation and DOM click each populated 1,200 characters |

**Generated report wording verified in browser:** “This report covers 55 WCAG 2.2 Level A and AA success criteria. Coverage is not a conformance pass ... 37 criteria require further review or a person to check, and 13 were not checked this time. Full WCAG conformance is not established by this automated report alone.” These **37/13 values belong to the later sample report**, not the historical Grabzies criterion-status table.

**Authentication observation:** An unauthenticated page load returned **401** for `GET /api/auth/me`; the audit page itself loaded with HTTP 200. No evidence here establishes that this expected-or-unexpected authentication response breaks the public page.

**Billing:** The final sample report test called local report-generation functions without clicking the gated paid-audit button. This demonstrates no chargeable audit submission was intentionally triggered; it does not independently inspect account transactions.

## 3. Grabzies — historical audit snapshot, retained unchanged

**Original automated report:** **50/100**; **19 passed checks**, **2 errors**, **4 warnings**. This is an issue-weighted automated score, not a WCAG conformance percentage.

**Historical criterion-level table (55 WCAG 2.2 Level A/AA criteria):**

| Historical status | Level A | Level AA | Total |
|---|---:|---:|---:|
| Failed | 0 | 2 | 2 |
| Warning | 1 | 0 | 1 |
| No problems found | 0 | 1 | 1 |
| Manual review needed / partial automated evidence | 30 | 0 | 30 |
| Needs a person to check | 0 | 20 | 20 |
| Not checked this time | 0 | 1 | 1 |
| **Total** | **31** | **24** | **55** |

**Originally failed criteria:** 1.4.10 Reflow and 1.4.11 Non-text Contrast. **Historical warning:** 2.4.1 Bypass Blocks. Historical 1.3.4 Orientation was labeled “No problems found” by the implemented check only.

**Reflow observations:** One saved rendered-report excerpt records **336px document width at a 320px viewport**; another historical finding records **352px at 320px**. They must remain separate observations unless identical page/run conditions are proven.

**Non-text contrast:** Eight controls were flagged for low-contrast boundaries; the need for each boundary to identify its control requires contextual assessment. The historical flag does not prove every one of the eight is a confirmed criterion failure after remediation.

## 4. Grabzies — subsequent remediation evidence

| Evidence | Recorded outcome | What it establishes |
|---|---|---|
| `/shop/` at 320, 375, 480px | **3/3 passed** | HTTP 200; no horizontal overflow at tested widths |
| `/google-seo-audit/` at 320, 375, 480px | **3/3 passed** | HTTP 200; no horizontal overflow at tested widths |
| **Combined responsive checks** | **6/6 passed within scope** | No horizontal overflow in six recorded page/viewport combinations |
| Later 2.4.1 classification regression | **5/5 passed** | Supersedes earlier classification behavior for the tested cases, not the historical snapshot |

**Scope limit:** The six responsive checks do not prove the original reflow failure was resolved under the exact original rendered page/content state and offending elements. They also do not constitute retests of the eight low-contrast control boundaries.

## 5. Completion decisions

- **Close as engineering-verified:** Frontend deployment and browser report-generation smoke test; interpretation note; recorded ACT text-spacing examples; regression suite; fixtures; readiness checks; WCAG 2.4.1 classification regression.
- **Close as scoped verification only:** Six Grabzies responsive checks at the listed URLs and widths. Do not mark the entire 1.4.10 criterion universally passed.
- **Retain as historically detected:** Original Grabzies 1.4.10 and 1.4.11 findings and the earlier 2.4.1 warning. Do not silently erase or relabel original audit results.
- **Remain evidence-unresolved:** Like-for-like closure of original reflow finding; post-fix adjudication of the eight control-boundary contrast findings; complete applicable manual assessment of WCAG 2.2 A/AA criteria and processes.
- **No repeat required:** Do not rerun the completed 38/38, 30/30, 4/4, 6/6, 5/5, frontend smoke test, or six responsive checks merely to regenerate evidence.

## 6. Source trail and authority

1. Library: `grabzies-wcag-evidence-reconciliation-2026-10-23.md` — saved historical report, later responsive checks, 2.4.1 regression and ACT/tool counts.
2. Library: `wcag-2.2-evidence-reconciliation-grabzies-2026-10-23.md` — independent saved reconciliation and scope distinctions.
3. Library: `reconcile_wcag_existing_evidence.sh` — reconciliation text preserving 352px and 336px as separate historical observations.
4. Library: `Pasted text(20261023-193215).txt` — server evidence summary recording six responsive results, URLs and viewports.
5. Current conversation, 24 October 2026 — live HTTP delivery; browser viewport smoke test; report-generation output: `reportGenerated=true`, `coverageCount=55`, `noticePresent=true`, no JavaScript errors.
6. Server canonical evidence directory cited in saved records: `/var/www/vhosts/aiwebpageseo.com/site-audit/test/act/act-w3c/`, notably `GRABZIES-WCAG-REMEDIATION-EVIDENCE.md`, `.json`, `ACT-RECONCILED-EVIDENCE-2026-10-22.md`, and `wcag-existing-evidence-reconciliation-20261023T160035Z.md`.

**Authority note:** This is a consolidated derivative record, not a fresh site assessment. Server-side canonical evidence files were not modified, and the original historical findings retain precedence for their own test dates and scopes.