AccessWatchHQ blog

Plain answers to the questions Shopify brands ask about ADA compliance, WCAG 2.2, and accessibility monitoring.

• Error Identification: What WCAG 3.3.1 Actually Requires Beyond the Red Border
  2026-11-14

  WCAG 3.3.1 wants the error identified in text, not just a red border. Most checkouts fail it on the field that matters most.

• The Checkout Button Nobody Can Reach: Focus Order Through Payment Steps
  2026-11-14

  A keyboard user experiences checkout as a sequence of tabs. When focus jumps, vanishes, or loops, the checkout is broken even though every field works.

• The Error Summary at the Top of the Form Is the Whole Fix
  2026-11-13

  Inline errors tell a screen reader user what is wrong with one field. They do not tell them how many fields are wrong, or where to start. The summary does.

• When the Modal Closes, Focus Has to Go Home
  2026-11-13

  A modal that traps focus correctly and then dumps it at the top of the page on close has only done half the job. Return focus to the element that opened it.

• Watching Password Reset and Account Recovery Flows for Barriers
  2026-11-12

  A shopper who cannot reset a password cannot buy. Reset flows stack three accessibility failures, a timed code, a paste-blocked field, and a CAPTCHA, and nobody watches them.

• Error Identification 3.3.1: Inline Errors Screen Readers Actually Find
  2026-11-12

  A red border is not an error message. WCAG 3.3.1 wants the error identified in text, tied to the field, and announced. Most checkout forms fail it with a color change and a summary at the top.

• Stop Making Shoppers Type the Same Address Twice: WCAG 3.3.7
  2026-11-11

  WCAG 3.3.7 is Level A: information entered once in a process must be auto-populated or selectable when it is needed again. Browser autofill does not count.

• The 24-Pixel Rule Has Five Exceptions. Learn Them Before You Remediate.
  2026-11-11

  WCAG 2.5.8 sets a 24 by 24 CSS pixel minimum for pointer targets, with five exceptions. Most teams either ignore the rule or over-fix it.

• Focus Appearance in WCAG 2.2: What 2.4.13 Actually Demands of Your Outline
  2026-11-10

  WCAG 2.2 added a measurable focus indicator rule in 2.4.13: a 2 CSS pixel perimeter and 3 to 1 contrast. Most sites fail it with a one-pixel outline they never tested.

• Accessible Authentication: WCAG 3.3.8 and the End of the Puzzle Test
  2026-11-10

  WCAG 2.2 says no cognitive function test at login without an alternative. The puzzle CAPTCHA is the test, and passkeys are the way out.

• Non-Text Contrast: Icons, Focus Indicators, and the 3:1 Rule
  2026-11-09

  Text contrast is the check everyone runs. Non-text contrast is the one most sites fail: input borders, icons, focus rings, and chart series at 3:1.

• Text Spacing Overrides: What Happens When Users Set Their Own Line Height
  2026-11-09

  WCAG 1.4.12 lets users set their own text spacing, and most layouts quietly break when they do. Here is the test and the two CSS habits that cause it.

• Zoom to 200%: What Breaks When Text Gets Bigger
  2026-11-08

  WCAG 1.4.4 requires text to survive 200 percent zoom, and 1.4.10 requires the page to reflow at 320 pixels. Fixed heights and widths are what break.

• Section 508 vs WCAG 2.1 AA: What Federal Procurement Actually Requires
  2026-11-08

  Section 508 applies to federal agencies and incorporates WCAG 2.0. Title II covers state and local government and names WCAG 2.1. The overlap is the plan.

• 3,117 Federal Filings in 2025, and Ecommerce Took the Biggest Share
  2026-11-07

  Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, up 27 percent from 2024. Ecommerce sites were the most-sued category, and the failures cited are the same six every year.

• The FAQ Accordion That Announces Nothing When It Opens
  2026-11-07

  An accordion button that expands a panel without telling a screen reader has failed WCAG 4.1.2 and 4.1.3 at once. The fix is aria-expanded, a real button, and a heading structure that survives the toggle.

• What an ADA Demand Letter Actually Asks a Store to Fix
  2026-11-06

  Demand letters follow a pattern: the standard cited, the barriers named, a deadline, and a settlement figure. Knowing the pattern takes the panic out of the first one.

• Watching Video Players: Captions That Lag the Audio
  2026-11-06

  Captions that trail the spoken words by two seconds are worse than no captions for a deaf viewer. Product videos are the worst offenders on storefronts.

• Repeat Defendants: What the 2025 Filing Numbers Say About Second Lawsuits
  2026-11-05

  Federal website accessibility filings rose 27 percent in 2025 to 3,117, and a large share targeted companies sued before. Why remediation that stops at settlement keeps failing.

• Reading Theme Release Notes Like an Accessibility Watch List
  2026-11-05

  Theme updates announce new sections and faster load times, never the focus style they removed. How to turn vendor release notes into a short regression checklist.

• Watching Live Chat Widgets for Keyboard Traps and Focus Loss
  2026-11-04

  Chat widgets are third party code dropped into every page, and they are a reliable source of keyboard traps, unlabelled buttons, and focus that never comes back. What to watch for.

• Watching Third Party Payment Buttons: Iframes, Titles, and Tab Order
  2026-11-04

  Express payment buttons arrive as iframes from another origin. You cannot fix their insides, but you can watch their titles, their order in the page, and whether they appear at all.

• Watching Autoplay Video Backgrounds and Their Pause Controls
  2026-11-03

  A looping hero video with no pause button fails more than taste. WCAG 2.2.2 Pause Stop Hide, motion sensitivity, and what to check on every hero that moves.

• Watching Breadcrumb Navigation for Landmarks, Labels, and Keyboard Use
  2026-11-03

  Breadcrumbs are small, structural, and routinely built as a row of divs. Checking the nav landmark, its label, and the current page marker that assistive technology depends on.

• Watching Cookie Preference Links Buried in the Footer
  2026-11-02

  The footer cookie settings link is the control shoppers use to change a choice they made months ago. If it is a dead span, a tiny low contrast link, or a button that reopens nothing, the consent record is fiction.

• Watching Image Zoom Controls for Keyboard Traps and Lost Focus
  2026-11-02

  Product image zoom opens a lightbox that swallows focus, hides the close button from keyboards, and strands shoppers inside a gallery. The checks that catch it before customers do.

• Watching Filter and Sort Controls on Mobile Collection Pages
  2026-10-30

  On mobile, filters hide behind buttons that do not announce state, panels that open off screen for screen readers, and sort controls that reset focus. What to watch.

• Watching Homepage Carousels: Autoplay, Pause, and Focus Order
  2026-10-31

  Hero carousels move on their own, hide their pause buttons, and pull focus in odd orders. What to watch for on the most visited page of the store.

  On mobile, filters hide behind buttons that do not announce state, panels that open off screen for screen readers, and sort controls that reset focus. What to watch.

• Watching Sticky Help Buttons and Chat Bubbles Cover Focus
  2026-11-01

  Fixed chat bubbles and back to top buttons sit exactly where keyboard focus travels. When they cover the focused element or the checkout button, the failure is visual, positional, and common.

  On mobile, filters hide behind buttons that do not announce state, panels that open off screen for screen readers, and sort controls that reset focus. What to watch.

• Watching Wishlist and Save for Later Controls Drift
  2026-11-01

  Heart icons with no accessible name, wishlist buttons that announce nothing, and save for later controls that vanish for keyboard users. What to watch on product grids and carts.

  On mobile, filters hide behind buttons that do not announce state, panels that open off screen for screen readers, and sort controls that reset focus. What to watch.

• Watching Checkout Progress Indicators That Screen Readers Miss
  2026-10-31

  Step indicators tell sighted shoppers where they are in checkout. If the current step exists only as a colour or a filled circle, that information never reaches a screen reader.

  On mobile, filters hide behind buttons that do not announce state, panels that open off screen for screen readers, and sort controls that reset focus. What to watch.

• Watching Loyalty Popups That Appear Right After Login
  2026-10-30

  Loyalty and points popups fired on login steal focus, hide balances from screen readers, and trap keyboard users. What to watch for in these post login interruptions.

  On mobile, filters hide behind buttons that do not announce state, panels that open off screen for screen readers, and sort controls that reset focus. What to watch.

• Watching Age Verification Prompts for Barriers That Lock People Out
  2026-10-29

  Age gates fail hard: modal date pickers nobody can type into, ID upload steps with no instructions, and sessions that reset before a screen reader user finishes. Here is what to watch.

• Watching Countdown Timers and Live Sale Clocks
  2026-10-29

  Sale countdowns announce every second to screen readers, vanish at 200 percent zoom, and create pressure that timed checkout steps then punish. Here is how to watch them during a promotion.

• Watching Currency Switchers So Prices Stay Honest and Reachable
  2026-10-28

  A currency switcher that keyboard users cannot open, or that quietly desyncs from checkout, erodes trust fast. Here is what to watch in this small but critical control.

• Watching Gift Card Purchase Flows for Quiet Breakage
  2026-10-28

  Gift card flows break in small ways: lost denominations, silent delivery failures, and balance checks that vanish. Here is a watch routine that catches problems before the holiday rush.

• Watching Announcement Bar Rotations for Accessibility Drift
  2026-10-27

  Rotating announcement bars change messages, links, and timing without a code review. How to watch them so offers stay readable, pausable, and reachable for everyone.

• Watching Third Party Review Widgets for Accessibility Drift
  2026-10-27

  Review widgets inject stars, forms, and photo galleries that the store does not control. How to watch them for labelling, keyboard, and contrast problems.

• Accessibility Scans for Seasonal Landing Pages and Gift Guides
  2026-10-15

  Seasonal pages are built fast, copied from last year, and deleted in January. That speed is why they ship barriers the core site fixed long ago. A scan routine for campaign pages.

• What to Watch When Your Store Updates Its Theme Version
  2026-10-16

  Theme version updates promise bug fixes and new features, and they quietly revert accessibility fixes made in the old version. A watch plan for update day and the week after.

• What to Watch When Your Store Adds a Chat or Support Widget
  2026-10-17

  Chat widgets arrive as a small script and change the accessibility of every page on the store. The checks to run at install, and the regressions to watch for afterward.

• Watching Product Quick View Modals for Accessibility Failures
  2026-10-18

  Quick view modals concentrate every hard accessibility problem into one small box. What a watch should test every time the modal changes.

• Store Locators and Maps: Watching the Hardest Widget on Your Site
  2026-10-19

  Embedded maps are where accessibility goes to struggle. How to watch a store locator and give every shopper a usable alternative.

• Watching Third Party Embeds: Maps, Videos, and Social Feeds
  2026-10-20

  Embedded content arrives with its own barriers and its own update schedule. How to inventory embeds and hold each one to a simple standard.

• Auditing Product Filter and Sort Controls on Collection Pages
  2026-10-21

  Filters and sorting are how shoppers actually shop a large catalogue. An audit guide for the controls that decide who can narrow a range and who cannot.

• Watching Sale and Clearance Templates as They Rotate
  2026-10-22

  Sale pages are rebuilt under deadline, run for a fortnight, and vanish. A watching routine sized for pages that live fast and are replaced before an audit would ever see them.

• Watching Embedded Forms in Newsletter and Signup Blocks
  2026-10-23

  Newsletter blocks, waitlist forms, and signup embeds arrive from marketing platforms and drift out of step with the site. What to watch in the small forms everyone forgets.

• Watching Exit Intent and Timed Popups for Harm
  2026-10-24

  Exit intent and timed popups interrupt reading, trap focus, and reappear after dismissal. A watching brief for keeping promotional popups within bounds.

• Watching Age Verification Modals for Barriers
  2026-10-25

  Age gates block every shopper at the door, and their date fields and modal behaviour often block assistive technology users completely. What to watch.

• Watching PDF Lookbooks and Size Charts for Access Problems
  2026-10-26

  PDF lookbooks and size charts often ship untagged and unreadable to assistive technology. How to watch them, and when an HTML page is the better answer.

• Watching Live Chat Widgets for Accessibility Drift
  2026-10-26

  Live chat widgets update on their own schedule and drift out of accessibility shape. What to watch: launch buttons, focus handling, and unreadable message history.

• Watching Third Party Payment Buttons for Access Failures
  2026-10-25

  Express payment buttons arrive as vendor iframes with their own labels and focus behaviour. What to watch when wallet buttons join a product page.

• Watching Third Party Review Widgets on Product Pages
  2026-10-24

  Review widgets inject stars, forms, and photo galleries from another codebase. How to watch them for accessibility and layout failures after vendor updates.

• Watching Consent Dialogues That Cover the Page
  2026-10-23

  Consent banners, chat bubbles, and promo popups compete for the same corner of the screen. What to watch when stacked dialogues start hiding the store itself.

• Watching Chat Widgets and Support Tools for Accessibility Drift
  2026-10-22

  Chat and support widgets update themselves, move themselves, and quietly cover the page. What to watch so the help tool does not become the barrier.

• Watching Popups and Promotional Overlays for Accessibility Drift
  2026-10-21

  Discount popups and exit offers are added fast and tested rarely. What to watch so a promotion does not become the first barrier a shopper meets.

• Accessibility Watch for Holiday Landing Pages
  2026-10-20

  Gift guides and sale pages are built fast and retired fast. How to watch short lived landing pages so speed does not ship barriers.

• Watching Subscription and Replenishment Pages for Barriers
  2026-10-19

  Subscribe and save flows stack modals, toggles, and account pages. A watch list for the subscription journey shoppers repeat monthly.

• Watching Holiday Gift Guide Pages for Accessibility Regressions
  2026-10-18

  Gift guides are rebuilt fast, stuffed with media, and deleted in January. A watch plan for the seasonal pages your regular scans forget.

• Watching Accessibility Across Multiple Storefronts and Markets
  2026-10-17

  Multi market stores run one theme across many storefronts, and each market drifts differently. A watch plan that catches divergence before it becomes twenty separate problems.

• Watching Accessibility in Store Pickup and Local Delivery Flows
  2026-10-16

  Pickup and local delivery add location pickers, stock states, and time slots to checkout. Those small widgets carry a steady stream of accessibility problems worth watching.

• Watching Accessibility When Your Store Adds Subscription Widgets
  2026-10-15

  Subscription options add some of the busiest controls on a product page: frequency pickers, one time versus subscribe toggles, and account portals. What to watch after adding them.

• Watching Accessibility When You Add a New Sales Channel
  2026-10-14

  A new sales channel brings new templates, widgets, and checkout paths that your existing scans do not cover. How to extend accessibility watching when a channel launches.

• Accessibility Regression Testing After a Theme Update: A Repeatable Checklist
  2026-10-13

  Theme updates quietly undo accessibility fixes. A repeatable regression checklist to run after every update, so old barriers do not return unnoticed.

• Accessibility Drift After a Shopify App Uninstall
  2026-10-12

  Uninstalling an app does not always remove its markup. Why leftover code causes accessibility drift, and how continuous monitoring catches it.

• Accessibility Regression Budgets: How Many New Issues Per Release Is Acceptable?
  2026-10-11

  Zero new violations sounds noble and fails in practice. A regression budget gives teams a number they can actually hold.

• Should you gate Shopify theme deployments on accessibility scan results?
  2026-10-10

  Blocking deploys on scan results sounds rigorous until it blocks every release. Here is how Shopify teams gate deployments on accessibility findings without freezing the business.

• Should a Shopify store run accessibility scans on staging, production, or both?
  2026-10-09

  Staging catches issues before they ship. Production catches what staging hides. Most stores need both, scheduled differently and read differently.

• Why your first accessibility scan should set a baseline, not a grade
  2026-10-08

  The first scan of any site looks bad. The mistake is treating it as a grade to defend. Treat it as a baseline, and every scan after it becomes a progress report instead of a judgment.

• What should a Shopify store do when a third-party app widget keeps failing accessibility scans?
  2026-10-07

  Third-party widgets are the most common source of repeat scan failures, and you cannot fix someone else's code. Document the failure, pressure the vendor with evidence, and contain the widget so one app cannot sink your conformance.

• How do you test Shopify checkout accessibility without touching checkout code?
  2026-10-06

  Shopify locks down checkout code, but that does not make checkout untestable. Keyboard walkthroughs, screen reader passes, and checkout extensibility audits cover most of what matters.

• What should a Shopify store do when accessibility scan results change between runs?
  2026-10-05

  Scan results that shift between runs are usually telling you something true about the store, not something broken about the scanner. Triage the change: real regression, dynamic content, or scan noise, in that order.

• What should a Shopify accessibility statement promise, and what should it avoid?
  2026-10-04

  An accessibility statement is evidence, not marketing. Promise the standard you meet, the parts you are still working on, and how to contact you. Avoid promises the theme cannot keep.

• How should a Shopify store test accessibility on a mobile device?
  2026-10-03

  Most accessibility testing happens on a desktop browser, but most shoppers are on phones. A mobile accessibility pass checks touch targets, zoom, focus, and the checkout flow where mobile shoppers actually convert.

• What should a Shopify store do when an accessibility audit finds nothing?
  2026-10-02

  A clean audit is the best possible outcome and the most dangerous one. Nothing found does not mean nothing wrong, and how a store treats a clean result decides whether it stays clean.

• How should a Shopify store write up accessibility findings so developers actually fix them?
  2026-10-01

  Developers fix findings they can reproduce in under a minute. Every accessibility finding needs the same five lines: where it is, what is wrong, how to reproduce it, what fixed looks like, and which standard it violates.

• How often should a Shopify store re-run a full accessibility audit?
  2026-09-30

  The honest answer depends on how fast the store changes. Continuous monitoring for the drift, a full audit quarterly or after big changes, and a deep manual pass once a year.

• How should a Shopify store audit the accessibility of its checkout extensions?
  2026-09-29

  Checkout UI extensions inherit platform limits but still introduce real barriers. Audit them with keyboard, screen reader, and error-path tests, then document what you cannot fix.

• How should a Shopify store vet a new app for accessibility before installing it?
  2026-09-28

  Apps inject their own markup, and their accessibility becomes your liability. Run a 20-minute vetting pass before installing anything new.

How should a Shopify store handle accessibility for user-generated content?
2026-09-27

Reviews, photos, and Q&A come from customers, not your theme. You are still responsible for the accessible parts: the widgets that display them, the images without alternatives, and the keyboard traps they can introduce.

• How should a Shopify store protect accessibility during a theme redesign?
  2026-09-26

  A redesign resets accessibility to whatever the new theme ships with. Freeze a baseline of the old store, write accessibility into the design brief, test new templates before launch, and keep monitoring through the cutover.

• Do accessibility overlays help or hurt a Shopify store?
  2026-09-25

  What overlays do, the barriers testers keep finding in the widgets themselves, why they have not stopped lawsuits, what the subscription money buys instead, and how to evaluate one a client already has.

• What should a store do when an accessibility issue comes from Shopify itself?
  2026-09-24

  Identify what you control, work around what you cannot change, file what you cannot work around, and document the boundary in your accessibility statement.

• How should a store watch the accessibility of third-party embeds?
  2026-09-23

  Inventory every video, review widget, chat launcher, and social embed on the storefront, test each one, and re-verify whenever the vendor ships changes.

• What accessibility barriers hide in a typical Shopify checkout?
  2026-09-22

  Unlabeled fields, color-only error messages, keyboard traps around payment iframes, and silent timeouts are the most common checkout failures.

• What accessibility evidence should a Shopify team keep?
  2026-09-20

  Keep dated evidence showing scope, test method, failures, ownership, fixes, and human verification.