Notes
What we're reading and writing
Notes on web accessibility, WCAG 2.1 AA, and building sites that work for everyone.
Accessible Payment Forms: Card Masking, Iframes, and What WCAG Actually Requires
A card-number field that auto-inserts spaces as you type, a card-brand icon with no text alternative, a third-party payment iframe with no accessible name — three quiet failures hiding in the one form every paying customer has to complete. What WCAG 2.1 AA requires for each, and what a scanner can't see.
Quietramp ·
Making Sortable Table Columns Accessible: The aria-sort Attribute for E-Commerce
A sortable 'My Orders' history table or product-comparison table usually shows its sort state with nothing but a bold arrow icon — invisible to a screen reader. Here's what the aria-sort attribute actually requires, where it goes, and the WAI-ARIA worked example's own pattern for labeling the sort buttons without repeating instructions on every column.
Quietramp ·
The HTML autocomplete Attribute: Meeting WCAG 1.3.5 on Checkout Forms
A name field and an address field look identical to a browser or screen reader unless the markup says otherwise. What WCAG SC 1.3.5 Identify Input Purpose requires for checkout forms, and the exact autocomplete tokens that satisfy it.
Quietramp ·
Sticky Headers, Cookie Banners, and Chat Widgets: Meeting WCAG 2.4.11 Focus Not Obscured (Minimum)
A keyboard user can tab to a perfectly visible, perfectly labeled form field and still not see it — because a sticky header, cookie banner, or chat launcher is sitting on top of it. Here's what WCAG 2.2's SC 2.4.11 actually requires, the e-commerce patterns that fail it, and the CSS fix.
Quietramp ·
Stock Status Indicators: Making Out-of-Stock and Low-Stock Labels Accessible
Out-of-stock badges, low-stock warnings, and disabled "Add to Cart" buttons fail WCAG 2.1 AA in three quiet, easy-to-miss ways — a color-only cue, a disabled control that doesn't say why, and a live update that never gets announced. Here's what actually fixes each one.
Quietramp ·
Order Confirmation and Shipping Emails: The Accessibility Gap After Checkout
An accessible checkout doesn't end at the confirmation page. Order confirmation and shipping-update emails are still HTML read by the same screen readers your site is — and Gmail and Outlook don't even agree on whether images show up by default. Here's what to check.
Quietramp ·
prefers-reduced-motion: Why Parallax Scrolling and Hover Animations Need an Off Switch
WCAG SC 2.3.3 Animation from Interactions lets users disable motion effects that aren't essential to a page's function — parallax hero banners, hover-triggered product tilts, add-to-cart 'fly' animations. What the criterion actually covers, the one CSS media query that fixes most of it, and why it's a Level AAA criterion your AA audit won't flag.
Quietramp ·
Structured Negotiation and Mediation: Two Ways ADA Web Accessibility Disputes Get Resolved Without a Lawsuit
Not every ADA web accessibility dispute ends in a lawsuit. The DOJ's own ADA Mediation Program and private structured negotiation are two documented, real alternatives — how each one actually works, how they differ, and where a demand letter fits in.
Quietramp ·
How to Prioritize Accessibility Fixes When You Can't Fix Everything at Once
A real audit or a self-check will usually turn up more issues than you can fix on day one. A W3C-grounded framework for deciding what to fix first — by task, by page, and by effort — instead of guessing.
Quietramp ·
New York's Human Rights Laws and Website Accessibility: What E-Commerce Sellers Should Know
New York leads the U.S. in ADA website-accessibility lawsuit filings, and most of those suits also plead the state's own laws — NYSHRL (NY Executive Law § 296) and NYCHRL (NYC Administrative Code Title 8). How they differ from each other, and from California's Unruh Act. Educational content, not legal advice.
Quietramp ·
Accessible Price-Range Sliders: The WAI-ARIA Multi-Thumb Slider Pattern for E-Commerce Filters
Most price-range filter sliders are custom-built div widgets, not native form controls — and most of them only respond to a mouse drag. The WAI-ARIA multi-thumb slider pattern that makes a two-handle range filter keyboard- and screen-reader-operable, with code.
Quietramp ·
Making Referral and Loyalty Program Widgets Accessible: Copy-to-Clipboard Codes, Share Buttons, and Status Messages
A referral or loyalty widget's whole job is three small controls: a code you can copy, a button that copies it, and a confirmation that it worked. Here's what WCAG 2.1 AA requires for each one, and why the confirmation is the part almost every implementation gets wrong.
Quietramp ·
Does WCAG Apply to Your Store's Mobile App the Same Way It Applies to Your Website?
WCAG was written for web pages, but courts have already treated a store's app and website as one accessibility question. WCAG2ICT — the W3C's own guidance on applying WCAG to non-web software — explains what changes (and what doesn't) when the thing you're testing is a screen, not a page.
Quietramp ·
The European Accessibility Act: What U.S. E-Commerce Sellers Need to Know If They Sell to the EU
The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 and explicitly covers e-commerce — including U.S.-based stores selling to EU consumers. Scope, the micro-enterprise exemption, deadlines, and how it relates to WCAG. Educational content, not legal advice.
Quietramp ·
Shipping Method Selection at Checkout: Building an Accessible Radio Group for Delivery Options
Why the shipping-speed cards on a checkout page often fail WCAG 2.1 AA — and why a native <input type=radio> wrapped in a full label beats a synthetic ARIA pattern here.
Quietramp ·
Age Verification Gates: The Accessibility Failures Blocking Your Entire Store
Alcohol, tobacco, vape, and CBD storefronts often run behind a full-page age-verification gate. Unlike every other modal on a site, this one blocks all content until it's cleared — and its most common failure mode isn't trapping users, it's silently failing to.
Quietramp ·
How to Add Alt Text to Product Images in Shopify and WooCommerce (No Developer Required)
The exact admin screens and fields for adding alt text to product photos in Shopify and WooCommerce — a practical, non-developer walkthrough for store owners, not a markup guide.
Quietramp ·
Making Product Configurators and Bundle Builders Accessible for E-Commerce
Build-your-own bundles, engraving tools, and multi-option product configurators stack several custom controls into one flow. Here's what WCAG 2.1 AA requires for the option pickers, the live preview, the running total, and the personalization field — and how each one fails on its own.
Quietramp ·
Horizontal Product Rails Aren't Carousels: What WCAG Actually Requires for Keyboard Scrolling
'You May Also Like' and 'Recently Viewed' rows scroll sideways but never auto-rotate, so the carousel rules don't apply to them. Here's the real requirement — a scrollable region a keyboard user can actually get into — sourced to WCAG, a W3C ACT rule, and axe-core's own rule set.
Quietramp ·
Social Proof and Urgency Notification Popups: The Accessibility Problems Behind "X People Are Viewing This"
The small toast that pops up in a corner of a product page — 'Someone in Austin just bought this,' '14 people are viewing this item' — is one of the most common third-party e-commerce widgets, and one of the least accessible. Here's what WCAG actually requires for it, and the counterintuitive part most fixes get wrong.
Quietramp ·
ADA vs. Section 508 vs. WCAG: What Each One Actually Requires (and Which Applies to Your Online Store)
ADA, Section 508, and WCAG get used interchangeably, but they're three different things: a civil-rights law, a federal procurement rule, and a technical standard with no legal force of its own. What each one actually covers, which one binds a private e-commerce business, and why a vendor or government buyer might still ask you about Section 508. Educational content, not legal advice.
Quietramp ·
Making "Quick View" Product Modals Accessible
Quick View lets shoppers preview a product from a category grid without leaving the page — but the trigger, the dialog it opens, and the content it loads async each fail a different WCAG 2.1 AA success criterion. Here's what to check for each.
Quietramp ·
Return and Exchange Request Forms: Getting File Uploads and Item Selection Right
A return request form usually has three moving parts most sites get partly wrong: which items to return, why, and a photo upload for damaged goods. Here's what WCAG 2.1 AA requires for each — including a file-input hiding technique that silently breaks screen reader access even when it looks fine visually.
Quietramp ·
Order Tracking and Shipment Status Pages: Making Live Delivery Updates Accessible
A shipment-status page updates its text after the page has already loaded — sometimes on a timer, sometimes only on refresh — with no reload to announce it. What WCAG SC 4.1.3 requires for that update, and why role="status" and role="alert" aren't interchangeable here.
Quietramp ·
Gift Card and Promo Code Fields: The Error States Most Checkout Forms Get Wrong
Gift card and promo code fields at checkout usually work fine when the code is right. Here's what WCAG 2.1 AA requires for the moment it's wrong, or a shopper wants to stack more than one.
Quietramp ·
Loyalty Points and Rewards Progress Bars: Getting the ARIA Meter Pattern Right
The 'X of Y points to Gold status' bar on a loyalty or rewards page is almost always a plain div with a percentage-width fill — no accessible name, no exposed value, and often the wrong ARIA role even when someone tries to fix it. Here's the actual spec-correct pattern.
Quietramp ·
WCAG SC 2.5.1 Pointer Gestures: Swipe, Pinch, and Path-Based Gestures on E-Commerce Sites
A pinch-to-zoom product viewer or a swipe-only carousel with no button alternative fails WCAG SC 2.5.1 Pointer Gestures. What the criterion actually requires, the W3C's own worked examples, and the two-technique fix.
Quietramp ·
Making Store Locator Maps and Location Widgets Accessible for E-Commerce
A store locator's interactive map often fails three ways at once: no text alternative for the map itself, markers that aren't keyboard-operable, and a bare iframe embed with no descriptive title. What WCAG requires and how the most widely used map API actually behaves by default.
Quietramp ·
What the WebAIM Million 2026 Report Shows About E-Commerce Site Accessibility
Shopify, Magento, and PrestaShop storefronts all scored worse than the average website in WebAIM's 2026 scan of one million home pages. What the numbers actually show, and the six fixable issues causing 96% of the errors.
Quietramp ·
Custom Video Player Controls: Why Replacing Native Video Controls Breaks Keyboard and Screen Reader Access
Branded video player skins routinely replace native browser video controls with custom play, seek, and volume widgets — and lose keyboard and screen-reader access in the process. The WCAG 2.1 AA rules that govern custom media controls, and how to rebuild them correctly.
Quietramp ·
Flashing Content and WCAG SC 2.3.1: Why "Flash Sale" Banners and Autoplay Video Need a Safety Check
WCAG SC 2.3.1 Three Flashes or Below Threshold governs any content that flashes more than three times a second — animated GIF promo banners, autoplay hero video, and fast CSS pulse effects included. What it actually requires, why axe-core can't test it, and how to check your own site.
Quietramp ·
What Should Be in an Accessibility Audit Report? A Buyer's Checklist
Most store owners have no way to judge whether an accessibility report they were sold is rigorous or a reskinned single-page scanner export. A checklist grounded in the W3C's own evaluation methodology (WCAG-EM) for what a real audit report should show.
Quietramp ·
Buy Now, Pay Later Widgets: The Accessibility Gaps in Klarna, Afterpay, and Affirm Embeds
Klarna, Afterpay, and Affirm badges are now standard on product pages and at checkout. They're also almost always third-party embeds a store owner can't fully edit — here's where that structure breaks WCAG 2.1 AA, and what's actually fixable from your own code.
Quietramp ·
Character Key Shortcuts and WCAG SC 2.1.4: Why a Global "Press S to Search" Shortcut Breaks Accessibility
A single-letter keyboard shortcut like 'press / to search' can hijack a screen reader user's typing and derail speech-input dictation. What WCAG SC 2.1.4 requires, and the three ways to fix a global character-key shortcut.
Quietramp ·
Windows High Contrast Mode and forced-colors: What Breaks on an E-Commerce Site, and How to Fix It
Windows High Contrast Mode strips box-shadow, background images, and custom colors down to a user-chosen palette — silently deleting selection rings, badges, and custom checkboxes that rely on them. What the CSS forced-colors media feature actually does and the fix that keeps your UI visible.
Quietramp ·
Language of Page and Parts: What WCAG SC 3.1.1 and 3.1.2 Require for Multi-Language E-Commerce Sites
A country switcher that changes visible copy without updating the lang attribute, or a foreign-language customer review pasted in with no language markup, both miss WCAG SC 3.1.1 and 3.1.2. What each criterion actually requires, the one-attribute fixes, and what a scanner can and can't catch.
Quietramp ·
Orientation Lock and Mobile E-Commerce: What WCAG SC 1.3.4 Actually Requires
A checkout that force-locks to portrait, or a fullscreen product video that only plays in landscape with no way back, both risk failing WCAG SC 1.3.4 Orientation. What the criterion actually requires, the two ways sites lock orientation without meaning to, and what a scanner can and can't catch.
Quietramp ·
Accessible Sale Prices: Why a Struck-Through Price Alone Fails Screen Reader Users
A strikethrough on an original price is a visual relationship, not an announced one — most screen readers say nothing about it by default. What WCAG SC 1.3.1 and 1.4.1 require for sale-price display, what real screen-reader testing shows, and the markup fix that actually works.
Quietramp ·
Images of Text in E-Commerce: What WCAG SC 1.4.5 Requires (and When a Sale Banner Is Fine)
A '20% OFF' banner flattened into a single image can't be resized, recolored, or read in a different font by someone who needs that. What WCAG SC 1.4.5 Images of Text actually requires, its two real exceptions, and the CSS fix.
Quietramp ·
WCAG 3.2.1 On Focus: Why Tabbing to a Control Shouldn't Change Anything
A newsletter field that pops a modal the instant it's tabbed into, or a help icon that steals focus into a panel before it's even activated, fails WCAG 3.2.1 On Focus. What the criterion actually requires, how it differs from On Input, and the one-line fix.
Quietramp ·
Pointer Cancellation: What WCAG SC 2.5.2 Requires for "Add to Cart" and Swipe-to-Remove
A button wired to fire on touchstart instead of click can't be aborted once a finger lands on it. What WCAG 2.5.2 Pointer Cancellation actually requires, where it breaks on e-commerce sites, and the two sufficient fixes.
Quietramp ·
Auto-Submitting Dropdowns and Unexpected Context Changes: WCAG 3.2.2 On Input for E-Commerce
A country selector or sort-by menu that navigates the instant its value changes fails WCAG 3.2.2 On Input. What the criterion actually requires, the two sufficient fixes, and when an onchange handler is fine.
Quietramp ·
Consistent Navigation and Consistent Identification: What WCAG SC 3.2.3 and 3.2.4 Require
An A/B test that reorders the header nav for half your visitors, or a cart icon labeled "Bag" on one page and "Cart" on another, can quietly fail two WCAG 2.1 AA criteria. What SC 3.2.3 and 3.2.4 actually require for e-commerce sites, and where templated stores break them.
Quietramp ·
Making Product Comparison Tables Accessible for E-Commerce
The 'Add to Compare' checkbox, the side-by-side spec table, and the floating comparison tray each fail WCAG 2.1 AA in a different way — no accessible name or state on the checkbox (SC 4.1.2), unlabeled table cells (SC 1.3.1), and a silent item count (SC 4.1.3). Here's what actually fixes each one.
Quietramp ·
aria-label vs. aria-labelledby vs. aria-describedby: A Practical Guide for E-Commerce Sites
aria-label, aria-labelledby, and aria-describedby all sound interchangeable, but they answer different questions and follow a strict precedence order. What each one actually does, which one wins when two are set on the same element, and the e-commerce failure (WCAG SC 2.5.3) that shows up when they're mixed up.
Quietramp ·
Vague Link Text on Product Grids: What WCAG SC 2.4.4 Link Purpose Requires
Every card on a category page says "Read More" or "Shop Now." WCAG SC 2.4.4 doesn't ban that pattern outright, but it does require the destination to be determinable — here's where product grids actually fail it, and the fix.
Quietramp ·
Multiple Ways to Find Content: What WCAG SC 2.4.5 Requires for E-Commerce Navigation
WCAG SC 2.4.5 requires at least two ways to reach any page that isn't a step in a process. For an e-commerce site, that means checking whether your category pages actually survive if the mega menu — or the search box — goes down.
Quietramp ·
Page Titles for E-Commerce Storefronts: What WCAG 2.4.2 Actually Requires (and Why It's an SEO Issue Too)
Every product, category, and checkout page needs a real, descriptive <title> — not just for WCAG 2.4.2, but because the same fix is also a basic SEO fundamental and the exact signal AI answer engines use to identify what a page is about. Here's what the spec requires and the four ways e-commerce sites commonly break it.
Quietramp ·
Sensory Characteristics in E-Commerce Instructions: What WCAG SC 1.3.3 Actually Requires
"Click the round button" or "tap the icon on the right" feel harmless, but WCAG 1.3.3 fails any instruction that identifies a control only by shape, color, size, position, orientation, or sound. What the criterion requires, and the fix for size guides, checkout copy, and help-center articles.
Quietramp ·
Accessible Loading States: What Spinners and Skeleton Screens Need for Screen Reader Users
What WCAG 4.1.3 Status Messages and the aria-busy state actually require for "Add to Cart" spinners, skeleton-screen placeholders, and filtered-results loading indicators — and why aria-busy alone doesn't announce anything.
Quietramp ·
Focus Order in E-Commerce Product Grids: What WCAG 2.4.3 Actually Requires
CSS Grid and Flexbox make it trivial to visually reorder a product grid — featured items first, sale badges promoted, price moved above the description on mobile — without touching the underlying markup. That gap between what's on screen and what's in the DOM is exactly what WCAG 2.4.3 Focus Order exists to catch.
Quietramp ·
Reflow and Text Spacing: What WCAG 1.4.10 and 1.4.12 Require for E-Commerce Pages
What WCAG 2.1 AA success criteria 1.4.10 Reflow and 1.4.12 Text Spacing require, why fixed-width cart columns and sticky checkout bars are the usual e-commerce failure points, and how to test both in minutes.
Quietramp ·
Accessible Checkout Step Indicators: What aria-current="step" Actually Requires
A visual step tracker ("Cart → Shipping → Payment → Review") tells a sighted shopper exactly where they are in checkout. Here's the WAI-ARIA token built for that exact case, and the three failures that show up before you even get to it.
Quietramp ·
Making "Notify Me When Back in Stock" Forms Accessible
The email-capture form behind a sold-out product's "Notify me" link fails WCAG 2.1 AA in four small, easy-to-miss ways — from a placeholder-only input to a confirmation message that never gets announced. Here's what actually fixes each one.
Quietramp ·
Making Pagination, "Load More," and Infinite Scroll Accessible for E-Commerce
Category pages, search results, and review lists all use one of three patterns to show more than one page of items. Here's what WCAG actually requires for numbered pagination, "Load more" buttons, and auto-loading infinite scroll — and where each one commonly breaks.
Quietramp ·
Making Date Pickers Accessible: The WAI-ARIA Dialog Pattern for E-Commerce Delivery Scheduling
Delivery-date scheduling, gift-card send dates, and appointment booking all lean on custom calendar widgets. Here's the WAI-ARIA dialog + grid pattern that makes one keyboard- and screen-reader-operable, and the failures that show up when it's skipped.
Quietramp ·
Accessible Mega Menus and Dropdown Navigation: Why Site Nav Shouldn't Use role="menu"
Category flyouts and mega menus are usually built with the wrong ARIA role. Here's what the WAI-ARIA Disclosure pattern actually recommends for e-commerce site navigation, and why role="menu" makes it worse, not better.
Quietramp ·
Consistent Help: What WCAG 3.2.6 Actually Requires
WCAG 2.2's SC 3.2.6 Consistent Help doesn't require you to add a contact link — it requires the one you already have to stay in the same relative position across every page in a flow. What that means for checkout, and the failure that trips up most sites.
Quietramp ·
Custom Dropdown Menus: The WAI-ARIA Select Pattern for E-Commerce Sort, Currency, and Country Selectors
Sort-by menus, currency switchers, and country selectors are almost never a native HTML <select> anymore. The WAI-ARIA select-only combobox pattern that keeps a custom-styled dropdown keyboard- and screen-reader-accessible, with code.
Quietramp ·
Making Quantity Steppers Accessible: The WAI-ARIA Spinbutton Pattern for E-Commerce
The +/- quantity control on nearly every product and cart page is a custom widget, not a native form field. Here's the WAI-ARIA spinbutton pattern that makes it usable by keyboard and screen reader, and the failures that show up when it's skipped.
Quietramp ·
Making Wishlist and Save-for-Later Buttons Accessible
The heart-icon wishlist button on almost every product card fails WCAG 2.1 AA in three separate, easy-to-miss ways — no accessible name, no state exposed to assistive technology, and a saved/unsaved signal that's color alone. Here's what actually fixes each one.
Quietramp ·
Website Accessibility Statements: What to Include and Why
A store owner's guide to writing an accessibility statement: what W3C WAI says to include, how to phrase it in plain language, and where to put it on your site.
Quietramp ·
Don't Require Dragging: WCAG 2.2's Single-Pointer Rule for Sliders, Carousels, and Reorderable Lists
WCAG 2.2's SC 2.5.7 Dragging Movements says any drag-based interaction needs a single-tap-or-click alternative. Here's what that means for price-range sliders, draggable product carousels, and drag-to-reorder wishlists.
Quietramp ·
Session Timeouts, Cart Timers, and Countdown Banners: What WCAG 2.2.1 Requires for E-Commerce
WCAG SC 2.2.1 Timing Adjustable governs every timer on an e-commerce site — checkout session logout, cart-hold countdowns, flash-sale banners. Here's what it actually requires, and what's exempt.
Quietramp ·
Making Accordions and Expandable Sections Accessible: The WAI-ARIA Pattern for E-Commerce
FAQ blocks, shipping/returns panels, and product-description 'read more' sections are usually a div with a click handler. Here's the WAI-ARIA Accordion pattern — role, state, and heading structure — that actually works with a keyboard and a screen reader.
Quietramp ·
Accessible Breadcrumb Navigation: The WAI-ARIA Pattern for E-Commerce Category Pages
A breadcrumb trail built from plain text and ">" characters looks fine and tells a screen reader nothing. Here's the WAI-ARIA Breadcrumb pattern — nav landmark, list markup, and aria-current — for category and product pages.
Quietramp ·
Don't Make Shoppers Re-Enter Information: WCAG 2.2's Redundant Entry Rule for E-Commerce Checkout
WCAG 2.2's SC 3.3.7 Redundant Entry says a checkout process can't ask for the same information twice without carrying it forward. Here's what that requires for billing/shipping addresses, checkout errors, and multi-step forms.
Quietramp ·
Accessible Authentication for E-Commerce: What WCAG 2.2's SC 3.3.8 Actually Requires
WCAG 2.2's SC 3.3.8 bans login and checkout steps that require remembering, transcribing, or solving something with no alternative. Here's what that means for password fields, OTP codes, and CAPTCHAs on e-commerce sites.
Quietramp ·
Accessible Tooltips and Info Icons: What WCAG 1.4.13 Requires
WCAG 1.4.13 sets three conditions for any hover/focus popup — dismissible, hoverable, persistent. Here's what that means for the "?" info icons e-commerce sites use for size guides, materials, and financing terms, and why the HTML title attribute alone doesn't meet the bar.
Quietramp ·
PDF Accessibility for E-Commerce: Making Size Guides, Spec Sheets, and Policy Documents Usable
Why the PDFs an e-commerce site links — size guides, spec sheets, warranty and return policies — need their own accessibility check, and the tagging, heading, and alt-text fixes that make them usable with a screen reader.
Quietramp ·
Touch Target Size on E-Commerce Sites: What WCAG 2.5.8 Actually Requires
WCAG 2.2's SC 2.5.8 sets a 24×24 CSS pixel minimum for tap targets. Here's what it actually requires, its five exceptions, and where e-commerce icon buttons — wishlist hearts, cart-remove ×, quantity steppers — typically fail it.
Quietramp ·
Why You Shouldn't Remove the Focus Outline: A Practical Guide to WCAG 2.4.7 Focus Visible
Removing outline: none in a CSS reset is one of the most common accessibility mistakes on e-commerce sites. Here's what WCAG 2.4.7 actually requires, why it breaks keyboard navigation, and the modern fix (:focus-visible) that doesn't.
Quietramp ·
Making Auto-Rotating Carousels and Sliders Accessible for E-Commerce
Homepage banner carousels and product sliders fail WCAG 2.1 AA in the same handful of ways on almost every site that runs one. The fixes for auto-rotation, keyboard operability, and icon-only controls — with code, sourced to WCAG and the WAI-ARIA APG.
Quietramp ·
Making Live Chat and Customer Support Widgets Accessible for E-Commerce Sites
Live chat launcher buttons, message bubbles, and third-party support iframes fail WCAG 2.1 AA in the same handful of ways on almost every site that has one. The fixes for the launcher button, incoming-message announcements, focus containment, and iframe labeling — with code.
Quietramp ·
Making Product Info Tabs Accessible: The ARIA Tabs Pattern for E-Commerce Product Pages
Description, Specifications, Shipping & Returns, Reviews — the tabbed panels on almost every product page are usually built as unlabeled clickable divs. Here's the WAI-ARIA Tabs pattern that fixes accessible name, keyboard support, and the tab-to-panel relationship.
Quietramp ·
California's Unruh Act and Website Accessibility: What E-Commerce Sellers Should Know
How California's Unruh Civil Rights Act creates a separate, state-law claim for website accessibility — a $4,000 statutory-damages floor, an automatic link to ADA violations, and the current carve-out for online-only sellers. Educational content, not legal advice.
Quietramp ·
Cookie Consent Banners: The Accessibility Failures Hiding in Plain Sight
Cookie consent banners run on almost every US e-commerce site and are frequently the first thing every visitor's assistive technology encounters. Here's exactly where they fail WCAG 2.1 AA — and how to fix each pattern.
Quietramp ·
Making Search Autocomplete Accessible: The ARIA Combobox Pattern for E-Commerce
Why the predictive-suggestions dropdown on a site search box breaks for keyboard and screen-reader users by default, and the WAI-ARIA combobox pattern — roles, states, and keyboard behavior — that fixes it.
Quietramp ·
Making Star Ratings and Review Widgets Accessible for E-Commerce Product Pages
Star ratings and review widgets fail WCAG 2.1 AA in three separate, common ways — a decorative rating display, an unlabeled review-submission picker, and icon-only helpful/not-helpful buttons. Here's how to fix each one.
Quietramp ·
Making Color and Size Variant Swatches Accessible on Product Pages
Why the clickable color and size swatches on a product page are one of the most common WCAG 2.1 AA failures in e-commerce, and the specific markup — accessible names, grouping, and selected-state — that fixes it.
Quietramp ·
ARIA Landmarks and Heading Structure: A Screen-Reader Navigation Guide for E-Commerce Pages
How ARIA landmark regions, a logical heading hierarchy, and skip links work together as the navigation system screen-reader users rely on — and the specific WCAG 2.1 AA rules and markup that make it work on an e-commerce page.
Quietramp ·
Making Size Charts and Spec Tables Accessible for E-Commerce
Why size charts and spec tables rendered as images fail screen-reader users, and the WCAG 2.1 AA table markup — headers, scope, caption, and irregular-header handling — that actually fixes them.
Quietramp ·
Making Product Videos Accessible: Captions, Transcripts, and Audio Description
The WCAG 2.1 AA rules that govern product-demo, unboxing, and size-guide videos on e-commerce sites — captions, audio description, silent hero-video alternatives, and autoplay audio — with a practical WebVTT example.
Quietramp ·
How to Talk to Your Developer About Accessibility Fixes: A Plain-Language Guide
A non-technical store owner's guide to translating common accessibility audit terms — accessible name, focus order, keyboard trap, contrast ratio, skip link — into specific requests a developer can act on, plus how to check a fix actually landed.
Quietramp ·
A 5-Minute Accessibility Self-Check Any Store Owner Can Do Before Hiring Anyone
A five-minute, no-developer-required checklist any e-commerce store owner can run to spot obvious accessibility problems before paying for an audit or a fix: keyboard navigation, 200% zoom, color contrast, and a short screen-reader spot-check.
Quietramp ·
Screen Reader Testing 101: A Basic Manual Pass Without Being an Expert
A practical, no-expertise-required guide to running one manual screen reader pass on your site — which free screen reader to start with, the handful of commands you actually need, and what to check on a product or checkout page.
Quietramp ·
What Automated Accessibility Scanners Actually Miss (And Why Manual Testing Still Matters)
axe-core, WAVE, and Lighthouse can automatically find roughly half of WCAG issues on a typical page — sourced to the tools' own data. Here's exactly what the other half requires a human to catch, and why.
Quietramp ·
Accessibility Pitfalls Specific to Subscription and Auto-Ship Checkout Flows
Plan-selector cards, subscribe-and-save toggles, delivery-frequency pickers, and skip-shipment controls are almost entirely custom UI. The WCAG 2.1 AA rules that apply and the fixes that meet them.
Quietramp ·
Form Labels and Error Messages: The WCAG 2.1 AA Rules Most Sites Get Wrong
The four WCAG 2.1 success criteria that govern accessible forms — labels, error identification, input purpose, and error prevention for checkout — explained in plain language with concrete markup fixes for e-commerce account and checkout forms.
Quietramp ·
Why Promo Modals and Exit-Intent Popups Are an Accessibility Landmine
Email-capture and discount-code popups are one of the riskiest UI patterns for keyboard and screen-reader users. The WCAG 2.1 AA rules that govern focus trapping, dismissibility, and dialog announcement — and how to fix them.
Quietramp ·
Accessible Product Filtering and Faceted Search: Filter Sidebars, Chips, and Results Announcements
How to make e-commerce filter sidebars, applied-filter chips, and dynamic results counts work for keyboard and screen-reader users — the WCAG 2.1 AA rules that govern faceted search and the concrete fixes that meet them.
Quietramp ·
Making Product Image Galleries and Zoom Accessible
Product thumbnail selectors and zoom/lightbox overlays are two of the most common places e-commerce sites lose keyboard and screen-reader accessibility. The WCAG 2.1 AA rules that apply and the concrete fixes that meet them.
Quietramp ·
Color Contrast for E-Commerce: WCAG Ratios and the Fixes That Actually Work
WCAG 2.1 AA's contrast rules in plain numbers, why low-contrast text is the single most common accessibility failure on the web, and the specific e-commerce patterns — hero banners, sale badges, disabled-looking buttons — that pass an automated scan and fail a real reader anyway.
Quietramp ·
Fixing Keyboard Traps: A Developer's Guide to Focus Management
A practical guide to WCAG 2.1 keyboard-trap and focus-management failures in e-commerce UI — cart drawers, modals, and custom dropdowns — with concrete code patterns to fix each one.
Quietramp ·
Serial Plaintiffs and Repeat Defendants: What ADA Web Accessibility Litigation Data Actually Shows
What 2025–2026 ADA Title III litigation-tracking data shows about repeat-defendant lawsuits and plaintiff/law-firm concentration, sourced to Seyfarth Shaw and UsableNet. Educational content, not legal advice.
Quietramp Editorial ·
Writing Alt Text That Passes a Manual Review, Not Just axe
Automated scanners like axe-core only check whether an image has alt text, not whether it's any good. A practical guide to writing alt text that actually helps screen reader users, with e-commerce examples and the checks a human reviewer runs that a scanner can't.
Quietramp ·
ADA Compliance Risk for E-Commerce SMBs: What Actually Triggers a Demand Letter
A plain-language guide to ADA Title III risk for small e-commerce businesses: whether the law applies to your site, what typically triggers a demand letter, and what a reasonable business can do about it. Educational content, not legal advice.
Quietramp Editorial ·
ADA Website Demand Letters: What Actually Happens After You Get One
What an ADA website demand letter actually contains, why there's no legal notice-and-cure period, how common these letters really are versus lawsuits, and general first-response steps. Educational content, not legal advice.
Quietramp Editorial ·
Do Accessibility Overlay Widgets Work? What the Evidence Actually Shows
An evidence-based look at accessibility overlay widgets: what a major practitioner survey, a 2025 FTC enforcement action, and 2025 ADA lawsuit data actually show about whether these tools make a site accessible or reduce legal risk.
Quietramp ·
The Most Common WCAG 2.1 AA Issues in E-Commerce Checkout & Cart Flows (And How to Fix Them)
A practical WCAG 2.1 AA checklist for e-commerce checkout and cart flows: the accessibility failures that show up most often, why they block real customers, and concrete fixes developers can ship today.
Quietramp ·