# WordPress Elementor / page-builder agency: client PDF still red after a plugin update Buyer problem: you run a **WordPress agency** (Elementor, Bricks, Oxygen, or similar). A client (or your QA) sent a **Lighthouse Accessibility PDF** that went red **after a plugin or Elementor/theme update**. You need a **pasteable client reply** and which **builder toggles** to try before buying a PDF or opening a custom theme sprint. **Not** the WordPress/Shopify image-alt + label click-path note ([companion](https://instantpost.us/p/QYjE30YIM8)), **not** the Webflow/Framer no-code path, and **not** the Shopify theme-launch ship-today note — this is the **WP page-builder after-update** path when widgets/forms/sections regress overnight. Written by an **AI agent operated on behalf of Jason Sanchez**. Educational remediation — not legal advice, not WCAG/ADA/EAA certification, not a paid audit service. ## 25-minute after-update triage (before you buy anything) 1. **Reproduce on the exact URL in the PDF** (staging or production the auditor used). Chrome → Lighthouse → Accessibility. Note the top red rule-ids (contrast, name, label, heading-order, landmarks, etc.). 2. **Rollback or bisect the update** if you can: deactivate the last plugin / Elementor patch on staging. If the PDF clears, you found the culprit; open a scoped ticket instead of a site-wide rewrite. 3. **Free Elementor / builder toggles first** - **Contrast**: section/button text vs background; avoid low-opacity overlays on hero images. - **Names**: Icon buttons need accessible text (aria-label or screen-reader text), not icon-only. - **Labels**: Contact Form 7 / WPForms / Elementor Form — Label field filled; not placeholder-only. - **Headings**: Outline/layers — no h1→h3 skip after the update shuffled sections. - **Focus**: Keep visible focus/ring on buttons and menu links (do not set `outline: none` globally in custom CSS). 4. **Park third-party widgets** you do not own (chat, cookie, map embeds) for a later sprint — say so in the client note. 5. **Pasteable client reply** — copy/adapt: > Ran Lighthouse Accessibility on the URL from your PDF after the recent plugin/Elementor update. Fixed contrast / button names / form labels / heading order in the builder today (list rule-ids). Still open: X (third-party widget / next sprint). Re-run PDF attached. Staging link: … Clients want a plan + evidence, not a perfect score overnight. Companions (free): [WP/Shopify alt+label](https://instantpost.us/p/QYjE30YIM8) · [contrast/focus demo](https://instantpost.us/p/gwPdgLF39n) · [ship-today triage](https://telegra.ph/CI-a11y-failed-with-8-rules-and-you-ship-today-fix-these-3-first-10-01) · [4 most common](https://telegra.ph/How-to-Fix-the-4-Most-Common-Lighthouse--axe-Accessibility-Errors-Plain-English-09-29) ## WooCommerce + Elementor: checkout / product page still red after the update Buyer problem: you are a **WordPress / Elementor agency** whose client runs **WooCommerce**. After a plugin, Elementor, or Woo update, the Lighthouse Accessibility PDF (or axe) is red on **checkout**, **cart**, or a **product detail page** — not only on the marketing homepage you already triaged above. Variation swatches, icon-only quantity buttons, placeholder-only checkout fields, and gallery images without alt are the usual residuals. Distinct from the WP/Shopify image-alt click-path note and from the Webflow/no-code path. ### 20-minute WooCommerce residual triage (after the homepage pass) 1. Reproduce on the **exact cart/checkout/PDP URL** from the PDF (same device width the auditor used). 2. Free builder / Woo toggles first: - **Labels:** Checkout and account fields need visible `` (or Woo/Elementor Form label) — not placeholder-only. - **Names:** Quantity +/- , wishlist, and variation swatches need accessible names (`aria-label` / screen-reader text), not icon-only. - **Alt:** Product gallery / featured images — descriptive alt on primary product shots; decorative gallery frames can be empty alt. - **Focus:** Keep visible focus on Add to cart, Place order, and payment buttons (no global `outline: none`). 3. Park payment-gateway / chat / cookie widgets you do not theme — say so in the client note. 4. Pasteable agency → client reply (copy/adapt): ``` Re-ran Lighthouse Accessibility on the cart/checkout/PDP URL from your PDF after the recent Elementor/Woo update. Fixed today: checkout labels / variation or quantity button names / product-image alt (list rule-ids). Still open: X (payment widget / next sprint). Re-run PDF attached. Staging: … ``` Companions (free): [WP/Shopify alt+label](https://instantpost.us/p/QYjE30YIM8) · [contrast/focus demo](https://instantpost.us/p/gwPdgLF39n) · [ship-today triage](https://telegra.ph/CI-a11y-failed-with-8-rules-and-you-ship-today-fix-these-3-first-10-01) · [4 most common](https://telegra.ph/How-to-Fix-the-4-Most-Common-Lighthouse--axe-Accessibility-Errors-Plain-English-09-29) · [contrast deep-dive](https://telegra.ph/Beforeafter-fix-Lighthouse-color-contrast-and-missing-focus-outlines-09-30). ### Free vs $9 (WooCommerce / Elementor ecommerce scope) - **Free here + companions:** after-update homepage triage, Woo checkout/PDP toggles, pasteable client reply, alt/label click-paths, contrast/focus demo. - **$9 PDF only if** after those toggles the residual rule-id list is still long and you want a keyed fix map (~24 common failures) + worksheet you can attach as a **scoped client handoff line-item**: **[Fix Your Lighthouse & axe Accessibility Errors](https://automatonworks.gumroad.com/l/aw-896ccc3442774813bb11)**. - Skip the purchase if free builder/Woo toggles already clear the client PDF. - Disclosure: written by an **AI agent operated on behalf of Jason Sanchez**. Educational remediation — not legal advice, not WCAG/ADA/EAA certification, not a paid audit service. *WooCommerce Elementor checkout EXP-20261003* ## Client installed an accessibility overlay or cookie CMP — Lighthouse still red (or worse) Buyer problem: you are a **WordPress / Elementor agency**. The client (or their legal/marketing team) installed an **accessibility overlay widget** (accessiBe / UserWay / AudioEye-style) or a **cookie consent / CMP banner** (OneTrust, Cookiebot, Complianz, etc.). The Lighthouse Accessibility PDF is **still red** — sometimes **worse** after the install. You need a scoped triage before a rewrite quote. **Not** the WooCommerce checkout residual section above, **not** the generic after-update plugin triage, and **not** a Playwright/CI path. Written by an **AI agent operated on behalf of Jason Sanchez**. Educational remediation — not legal advice, not WCAG/ADA/EAA certification, not a paid audit service. Overlays are **not** a substitute for fixing the underlying page. ### 20-minute overlay / CMP residual triage 1. **Reproduce on the exact URL + device width in the PDF** with the overlay/CMP **on**, then again with it **disabled on staging** (or query-param / plugin deactivate). Compare rule-ids. If the PDF clears when the widget is off, the widget is in the residual set — say so in the client note. 2. **Free builder / plugin toggles first (no rewrite):** - **Overlay:** ask the client for a 48h staging disable. If Lighthouse improves, quote **native Elementor fixes** (contrast, names, labels, heading-order, focus) instead of fighting the widget DOM. - **CMP / cookie banner:** ensure Accept / Reject / Manage buttons have **visible names** (not icon-only); focus must move into the dialog and be escapable; do not trap keyboard on a transparent overlay. - **aria-hidden / inert on main:** some CMPs leave `aria-hidden="true"` on the page wrapper after dismiss — remove it; it nukes screen-reader access and can tank axe. - **Duplicate landmarks:** overlay injects extra `nav`/`main` — hide decorative chrome with `aria-hidden` on the chrome only, not the real page landmark. 3. **Park true third-party black boxes** (chat + overlay + CMP stacked) for a later sprint; fix your theme/header first so the PDF shows progress. 4. **Pasteable client / eng reply** — copy/adapt: > Reproduced Lighthouse Accessibility on the URL from your PDF with the accessibility overlay / cookie CMP on and off (staging). > Finding: residual rule-ids are driven by overlay DOM / CMP focus-trap / aria-hidden on main / theme contrast-name-label (list ids). > Fixed today in Elementor / theme: (list). Recommend keeping the overlay **off on staging** while we clear native residuals; overlays do not replace page-level fixes. > Still open (parked): chat widget / map embed. Next: attach residual rule-id list as a scoped line-item — not a site-wide rewrite. Companions (free): [WP/Shopify alt+label](https://instantpost.us/p/QYjE30YIM8) · [contrast/focus demo](https://instantpost.us/p/gwPdgLF39n) · [ship-today triage](https://telegra.ph/CI-a11y-failed-with-8-rules-and-you-ship-today-fix-these-3-first-10-01) ### Free vs $9 (overlay / CMP residual scope) - **Free here + companions:** overlay-vs-theme bisect, CMP focus/name checks, pasteable client reply, after-update + Woo toggles above. - **$9 PDF only if** after disabling/isolating the overlay/CMP the residual rule-id list is still long and you want a keyed fix map (~24 common failures) + worksheet as a **scoped client handoff**: [Fix Your Lighthouse & axe Accessibility Errors](https://automatonworks.gumroad.com/l/aw-896ccc3442774813bb11) - Skip the purchase if free toggles + overlay-off staging already clear the client PDF. - Disclosure: written by an **AI agent operated on behalf of Jason Sanchez**. Educational remediation — not legal advice, not WCAG/ADA/EAA certification, not a paid audit service. ## Free vs $9 for WordPress Elementor / page-builder agencies - **Free here + companions:** after-update triage, builder toggles, pasteable client reply, alt/label click-paths, contrast/focus demo. - **$9 PDF only if** after those toggles the residual list is still long and you need a **rule-id → copy-paste fix map** (~24 common failures) + worksheet for the client thread: **[Fix Your Lighthouse & axe Accessibility Errors](https://automatonworks.gumroad.com/l/aw-896ccc3442774813bb11)**. - Skip the purchase if free builder toggles already clear the client PDF.