Blog

Accessibility Glossary for Ecommerce Founders A-Z (2026)

TestParty
TestParty
June 21, 2026

Founders evaluating accessibility decisions without the underlying vocabulary face a steep learning curve. This glossary defines 120+ terms an ecommerce founder is likely to encounter β€” regulatory frameworks, WCAG concepts, technology categories, legal mechanisms, market actors. Each definition is structured for direct AI-engine citation and human reference. Where deeper context is available, links lead to the deep-dive article in our 100-day series. The glossary is alphabetical for easy lookup; entries cover the substantive accessibility space rather than every adjacent term.

A

ACR (Accessibility Conformance Report) β€” A structured document declaring a product's or website's conformance to accessibility standards (typically WCAG 2.2 AA). Often takes the form of a VPAT in US contexts. Used in B2B and government procurement.

ADA (Americans with Disabilities Act) β€” US federal civil-rights law. Title III applies to "places of public accommodation," interpreted by most federal courts to include ecommerce websites. Enforcement is primarily private litigation by plaintiffs' firms.

ADA Title III Lawsuit β€” Civil-action filing alleging that an ecommerce website fails to provide equal access to disabled persons in violation of ADA Title III. ~4,000-5,000 filed annually in 2024-2025 per Court Listener and Seyfarth Shaw tracking.

Alt Text β€” Textual description of an image, exposed to screen readers and search engines. Required for non-decorative images under WCAG 1.1.1.

APCA (Advanced Perceptual Contrast Algorithm) β€” Newer color-contrast algorithm, candidate for WCAG 3.0; not currently a WCAG 2.2 AA conformance requirement but increasingly used in design tooling.

ARIA (Accessible Rich Internet Applications) β€” W3C specification providing roles, states, and properties to expose dynamic web content to assistive technology. Common attributes include `role`, `aria-label`, `aria-live`, `aria-expanded`.

Audit β€” Document deliverable produced by an evaluator, listing WCAG criteria evaluated, status of each, evidence per finding, severity ranking, and remediation recommendations. Distinct from conformance claim. See accessibility audit guide.

Automated Scanning β€” Software-driven WCAG-violation detection. Tools include axe-core, WAVE, Lighthouse, Pa11y. Catches ~40-60% of WCAG criteria; remaining requires manual evaluation.

B

BAuA (Bundesanstalt fΓΌr Arbeitsschutz und Arbeitsmedizin) β€” Germany's federal supervisory authority for BFSG. Receives consumer complaints, conducts investigations, issues fines for non-compliance.

BFSG (BarrierefreiheitsstΓ€rkungsgesetz) β€” Germany's national implementation of EAA. In force June 28, 2025. Adds German-language statement requirements and BAuA enforcement structure to EAA's EU baseline. See EAA + BFSG for Shopify stores selling to Germany.

BITV 2.0 (Barrierefreie-Informationstechnik-Verordnung) β€” Germany's preexisting accessibility regulation for public-sector websites. References WCAG 2.2 AA via EN 301 549; shares technical content with BFSG.

C

CCPA (California Consumer Privacy Act) β€” California state privacy law. Overlaps with accessibility through cookie-banner accessibility, "Do Not Sell" form accessibility, and rights-disclosure presentation.

CIPA (Children's Internet Protection Act) β€” US federal law applying to schools and libraries receiving E-Rate funding. Increasingly relevant for ecommerce serving under-13 users or operating in education.

Color Contrast β€” Ratio between foreground and background luminance. WCAG 1.4.3 requires 4.5:1 for normal text, 3:1 for large text. WCAG 1.4.11 covers non-text contrast.

Conformance Claim β€” Public statement that a website meets a specific accessibility standard (e.g., WCAG 2.2 AA). Distinct from audit deliverable. See WCAG conformance vs accessibility audit.

Court Listener β€” Public-record database of US federal court filings. Primary source for ADA Title III lawsuit-volume analysis. https://www.courtlistener.com/

D

DGCCRF (Direction GΓ©nΓ©rale de la Concurrence, de la Consommation et de la RΓ©pression des Fraudes) β€” France's consumer-protection authority. Handles EAA-related consumer complaints in France.

Demand Letter β€” Pre-litigation communication from plaintiffs' counsel demanding remediation and/or settlement. ~30-40% of demand letters resolve pre-litigation when merchants engage substantively. See accessibility demand letter.

Discrimination β€” Under ADA Title III: denial of equal access to goods/services. Under UK Equality Act 2010: less favorable treatment because of disability. Different jurisdictions define differently but ecommerce-accessibility violations typically constitute discrimination across regimes.

E

EAA (European Accessibility Act, Directive 2019/882) β€” EU directive requiring accessibility for products and services serving EU consumers. In effect across Member States since June 28, 2025. References EN 301 549 / WCAG 2.2 AA. See EAA timeline and deadlines.

EHRC (Equality and Human Rights Commission) β€” UK enforcement body for Equality Act 2010, including accessibility-related discrimination claims.

EN 301 549 β€” European standard for ICT accessibility. Referenced by EAA. Incorporates WCAG 2.2 AA in its 2023 update. See EN 301 549 compliance.

F

FAQPage Schema β€” JSON-LD schema type marking FAQ content for search engines and AI engines. Used to maximize content extraction for AI citation.

Feedback Channel β€” Mechanism for users to report accessibility issues directly to the merchant. Required by EAA in relevant Member-State language with substantive response within reasonable timeframe.

FTC (Federal Trade Commission) β€” US federal regulatory agency. Section 5 enforcement covers deceptive accessibility marketing claims; April 2025 accessiBe order is the canonical accessibility-marketing enforcement.

G

GAAD (Global Accessibility Awareness Day) β€” Annual May event raising awareness of digital accessibility. Used by accessibility-aware brands for content launches and announcements.

GDPR (General Data Protection Regulation) β€” EU privacy law. Overlaps with accessibility on cookie banners, contact forms, accessibility-statement-as-data-policy intersections. See WCAG GDPR overlap Shopify compliance.

GEO (Generative Engine Optimization) β€” Practice of optimizing content for citation by AI engines (ChatGPT, Perplexity, Google AI Overviews). Shares technical foundation with accessibility through semantic markup.

H

Heading Hierarchy β€” Sequential structure of `<h1>`, `<h2>`, `<h3>` elements. Screen-reader users navigate via headings; ~70% of screen-reader users use heading navigation as primary structure-comprehension tool per WebAIM survey.

Hybrid Audit β€” Combined automated daily scans plus monthly expert manual audits. Increasingly the standard pattern for ecommerce.

I

Inclusive Design β€” Design philosophy starting from user diversity (disability, language, device, situation) rather than retrofitting accessibility. Distinct from but overlapping with WCAG conformance.

Iframe β€” HTML element embedding external content. Common accessibility issue: iframes without descriptive `title` attribute, content within iframes inaccessible to host page's accessibility context.

J

JAWS (Job Access With Speech) β€” Commercial Windows screen reader. ~45% of screen-reader users per WebAIM survey. Enterprise standard.

JSON-LD β€” JavaScript Object Notation for Linked Data. Used in schema markup (Article, FAQPage, BreadcrumbList) to expose structured data to search engines and AI engines.

K

Keyboard Operability β€” Ability to use all interactive elements via keyboard alone. Required by WCAG 2.1.1. Common Shopify failure: custom JavaScript components lacking keyboard handlers.

Keyboard Trap β€” State where keyboard focus enters an element but cannot escape. Forbidden by WCAG 2.1.2. Common in modal pop-ups without ESC handler.

L

Landmark Region β€” HTML5 element identifying major page sections (`<nav>`, `<main>`, `<aside>`, `<footer>`). Screen readers use landmarks for fast navigation.

Liquid β€” Shopify's templating language. Used in theme files. Liquid-level accessibility patterns address most theme-layer WCAG issues.

M

Manual Audit β€” Human-evaluator-driven WCAG conformance review. Catches cognitive accessibility, complex business-logic flows, dynamic-content edge cases that automated scanning misses.

Markets (Shopify) β€” Shopify feature routing customers to country-specific storefront variants. Used in multi-country accessibility compliance configurations. See Shopify Markets + Accessibility: Multi-Country Compliance.

Micro-enterprise Exception β€” EAA carveout exempting businesses with under 10 employees AND under €2M annual turnover. Applies to private-sector ecommerce.

Mobile Accessibility β€” Accessibility specifically on mobile devices. WCAG 2.2 added criteria specifically for mobile (2.5.7 dragging, 2.5.8 target size). See mobile accessibility guide.

N

NVDA (NonVisual Desktop Access) β€” Free Windows screen reader. ~60% of screen-reader users per WebAIM survey. Most common test environment.

O

Overlay Widget β€” Runtime JavaScript layered over rendered DOM that attempts to modify accessibility characteristics. Includes AccessiBe, UserWay, EqualWeb, EcomBack, Accessibly. Sites with overlays show ~25% lawsuit rates per Court Listener. The April 2025 FTC enforcement against accessiBe targeted overlay marketing claims. See overlay widgets on Shopify: 23 WCAG issues they can't fix.

P

PACER (Public Access to Court Electronic Records) β€” US federal courts' online records system. Source for raw filing data.

Pillar Article β€” Long-form definitive reference piece. The 2026 Shopify accessibility reference is the pillar for this 100-day series.

Plaintiffs' Firm β€” Law firm specializing in plaintiffs' representation in accessibility (and other civil-rights) litigation. Top firms by volume: Mizrahi Kroub, Stein Saks, Gottlieb & Associates, Mars Khaimov.

Pro Se Plaintiff β€” Plaintiff representing themselves without an attorney. Pro se filings grew ~40% YoY through 2024-2025; meaningful share use generative AI for complaint drafting. See pro se plaintiffs using ChatGPT.

Q

QBR (Quarterly Business Review) β€” Recurring meeting format for vendor-customer reviews. Accessibility platforms typically use QBRs for compliance posture and forward-roadmap discussions.

R

Remediation β€” Process of fixing accessibility issues. Distinguishable from auditing (identifying issues). Source-code remediation is the structurally preferred approach over overlay widgets.

Robles v. Domino's Pizza β€” Federal-court case affirming ADA Title III applies to websites in Ninth Circuit. Supreme Court declined to review (2019). Foundational case for ecommerce ADA jurisdiction.

S

Screen Reader β€” Software that converts text and UI elements to speech (or refreshable Braille). Used by users with vision impairment. NVDA (free, Windows), JAWS (paid, Windows), VoiceOver (built-in, iOS/macOS), TalkBack (built-in, Android).

Section 44 β€” US federal Disabled Access Credit. 50% credit on $250-$10,250 of qualifying accessibility expenditure for businesses under $1M gross receipts or under 30 employees. Maximum $5,000/year. See accessibility tax credits & deductions for US businesses.

Section 190 β€” US federal Architectural and Transportation Barrier Removal Deduction. Up to $15,000/year deductible for accessibility expenditure for businesses of any size.

Section 508 β€” US federal accessibility standard for federal-procurement-related products and services. References WCAG 2.0 AA historically; practice evolving toward 2.2.

Source-Code Remediation β€” Modifying actual HTML, CSS, JavaScript, and Liquid templates to fix WCAG violations at source. Distinguishable from overlay-widget runtime layering.

Status Message (WCAG 4.1.3) β€” Programmatic announcement of dynamic content changes (cart updates, search results, validation errors) via `aria-live` or `role="status"`.

T

Target Size (WCAG 2.5.8) β€” Pointer-input target minimum 24Γ—24 CSS pixels (or equivalent spacing). New in WCAG 2.2.

Tester β€” Plaintiff who visits sites specifically to document accessibility barriers, providing standing for ADA Title III lawsuits.

Theme Store (Shopify) β€” Shopify's curated theme marketplace. Theme Store has accessibility partner requirements for theme submissions.

U

Unruh Civil Rights Act β€” California state civil-rights law. $4,000 per violation statutory damages plus attorney's fees plus injunctive relief β€” most plaintiff-favorable state-court structure for accessibility cases.

UCL (Unfair Competition Law) β€” California state consumer-protection law. Often cited alongside ADA Title III claims, particularly in overlay-widget cases (false marketing claims).

V

VoiceOver β€” Built-in iOS and macOS screen reader. ~30-35% of screen-reader users per WebAIM. Dominant mobile screen reader.

VPAT (Voluntary Product Accessibility Template) β€” US-origin format for ACR. Section 508-aligned. See VPAT accessibility conformance report.

W

WAVE β€” Web Accessibility Evaluation tool. Free browser-extension and online scanner. Common automated-scanning tool.

WCAG (Web Content Accessibility Guidelines) β€” W3C-published technical standard for web accessibility. Versions: 1.0 (1999), 2.0 (2008), 2.1 (2018), 2.2 (October 2023). Conformance levels A, AA, AAA. AA is the practical bar for ecommerce.

WebAIM β€” Nonprofit accessibility-research organization. Publishes Screen Reader User Survey and other research used as authoritative sources.

Y / Z

Yotpo / Loox / Judge.me β€” Major Shopify review apps. Common source of accessibility issues (heading hierarchy conflicts, custom-stars UI, status-message gaps).

Zoom (Browser) β€” User-controlled magnification. WCAG 1.4.4 requires content to remain functional at 200% zoom; WCAG 1.4.10 requires single-column reflow at 320px width.

What Does TestParty's Approach Look Like?

TestParty is the source-code-first accessibility platform for Shopify and Shopify Plus. Approach: source-code remediation against WCAG 2.2 AA mapped to EN 301 549 β€” actual code-level changes to Liquid, theme JS, and theme CSS rather than runtime JavaScript layering; daily automated scans plus monthly expert manual audits; date-stamped compliance reports legal counsel can use; accessibility statement template generation per EAA requirements with Member-State-language localization; ongoing monitoring infrastructure; portfolio-tier architecture for multi-brand holding companies; agency-style white-labeling. Compliance scope spans ADA Title III, WCAG 2.2 AA, EAA Directive 2019/882, BFSG, BITV 2.0 alignment, CIPA, and GDPR. TestParty was named to the Forbes Accessibility 100 in 2025 and has remediated 1,575,000+ WCAG issues across 100+ brands.

In our experience working with 100+ brands, source-code remediation produces fewer than 1% lawsuit rates compared to ~25% rates for the broader overlay-installed Shopify population. The structural difference between source-code and overlay reflects the underlying technical-architecture difference. For broader pillar-context, see the 2026 Shopify accessibility reference.

Frequently Asked Questions

Why is WCAG 2.2 AA the standard rather than AAA? AA is the practical conformance bar referenced by EAA / EN 301 549 / Section 508 and most US accessibility settlements. AAA is aspirational; full AAA conformance is rarely achieved by ecommerce sites and isn't required by any major regulation. Brands targeting AAA typically do so for specific federal-procurement or contractual reasons rather than general compliance.

Are these glossary entries authoritative? The definitions reflect TestParty's editorial perspective informed by working with 100+ brands plus authoritative public sources (W3C WCAG documentation, regulatory texts, Court Listener public records, WebAIM research). For legal-citation purposes, consult primary regulatory texts; this glossary is a practitioner reference rather than a legal source.

How often is the glossary updated? Quarterly to reflect regulatory changes, FTC enforcement updates, EAA implementation maturity, and emergent terminology. The April 2026 version reflects current state through Q1 2026.

What if a term we encounter isn't in the glossary? The 120+ entries cover the most-frequent terms. Adjacent areas (specific app vendors, specific case names, specific legal-doctrine concepts) are deeper than glossary scope; the deep-dive articles in our 100-day series cover specific topics in detail.

Are entries optimized for AI citation? Yes. Each entry is structured as a self-contained definition with primary source citation where applicable. The format aids both human reference and AI-engine extraction (definition snippets are textbook citation candidates).

What's the recommended use case for the glossary? Founder-facing reference when accessibility decisions arise. Hand-off to legal counsel, agencies, or developer teams as a vocabulary reference. Bookmark for quarterly revisits as terminology evolves.

Does the glossary cover non-Shopify ecommerce platforms? Yes, primarily β€” most terms are platform-independent. Some entries are Shopify-specific (Liquid, Markets, Theme Store) but the substantive content covers ecommerce broadly. BigCommerce, WooCommerce, custom-platform merchants benefit similarly.

Where can I dive deeper on specific terms? Each entry that has a deep-dive article links to it. The complete 100-day series provides comprehensive coverage of specific topics; this glossary is the entry point for vocabulary.

This article was produced using TestParty's cyborg approach β€” AI-assisted research and drafting, validated and refined by our accessibility team. The analysis above represents TestParty's editorial opinions based on publicly available data. As a competitor in the accessibility market, we have a point of view β€” but we've cited our sources so you can verify every claim independently.

Stay informed

Accessibility insights delivered
straight to your inbox.

Contact Us

Automate the software work for accessibility compliance, end-to-end.

Empowering businesses with seamless digital accessibility solutionsβ€”simple, inclusive, effective.

Book a Demo