Pre-Launch Accessibility and Performance Gate (QA)

Pre-Launch Accessibility and Performance Gate (QA)

1. 01

   Freeze the generated build and tag the exact platform version used for the client site

   AI builders change their generation models and templates without notice, so record the platform, plan tier, and generation date in the project file before any QA pass begins.

2. 02

   Run an automated accessibility scan and triage findings by WCAG level

   Flag contrast failures, missing alt text on AI-selected imagery, and unlabeled form fields; anything below AA gets fixed or documented as a client-accepted exception in writing.

3. 03

   Test keyboard-only navigation through every template section the generator assembled

   AI layout assembly frequently produces focus traps in menus and modals; tab through the full page on desktop and mobile widths and log each break.

4. 04

   Measure Core Web Vitals on the hosted staging URL, not the editor preview

   Editor previews strip CDN and caching behavior. Pull field-equivalent lab scores for LCP, CLS, and INP, and set a pass threshold with the client before the audit so the number is not argued later.

5. 05

   Audit every AI-generated copy block for factual claims, pricing, and legal language

   Generated copy invents credentials, guarantees, and service areas. Route anything touching regulated claims to the client for sign-off and keep the approval in the delivery record.

6. 06

   Verify export and portability before the site goes live

   Confirm whether the platform allows full HTML/CSS export or only CMS data export, and store a current backup. Agencies that skip this discover the constraint at the worst possible moment.

7. 07

   Confirm content governance controls are configured for the client's team

   Set role permissions, publishing approval steps, and edit history retention so the client cannot push unreviewed changes to a live page after handoff.

8. 08

   Log the QA result as a signed checklist attached to the retainer file

   A dated pass record protects the agency when a client later reports a defect and shortens the next build because the same checks repeat.