Agentic Commerce and Digital Accessibility: What Online Shops Need to Know Now

For online shops, that means structure, semantics, and clean data now decide visibility in this new sales channel, not visual design. These requirements align closely with the WCAG 2.2 criteria that online shops already need to meet. Shops that build for accessibility are, at the same time, building for Agentic Commerce, without running a separate project.

What Is Agentic Commerce?

Agentic Commerce means buying through AI agents instead of the traditional path through a search engine and a website. Rather than searching, comparing, and adding items to a cart themselves, shoppers hand these steps to an assistant such as ChatGPT, Gemini, or Copilot, which finds products, evaluates them, and prepares or completes the purchase. OpenAI, together with Stripe, launched Instant Checkout in ChatGPT on September 29, 2025, and built the Agentic Commerce Protocol (ACP) as an open standard to power it. Google followed on September 16, 2025 with the Agent Payments Protocol (AP2), now supported by more than 60 partners, including Mastercard, PayPal, Salesforce, and Adobe. Visa and Mastercard have introduced their own standards for trusted, agent-based payments as well, the Trusted Agent Protocol and Agent Pay.

For merchants in e-commerce, this adds a new sales channel that runs on technical clarity rather than visual design. If a shopper asks an assistant for slip-resistant running shoes for wet weather under 120 euros, the agent has to match price, availability, and attributes correctly within seconds, without anyone ever looking at the product photo or reading the description. An agent can only recommend and buy what it can clearly understand.

The Protocols Shaping Agentic Commerce

A handful of standards are currently setting the pace for this new channel.

• ✓ ACP, Agentic Commerce Protocol, from OpenAI and Stripe, governs product search and checkout inside ChatGPT, live since September 29, 2025
• ✓ AP2, Agent Payments Protocol, from Google, live since September 16, 2025 with more than 60 partners, including Mastercard, PayPal, and Salesforce
• ✓ MCP, Model Context Protocol, connects AI agents to data sources and systems and underpins many agent integrations
• ✓ Trusted Agent Protocol and Agent Pay, Visa's and Mastercard's own standards for trusted, agent-based payments

Which of these standards ends up mattering for your shop depends on your platform and your target market, and the list is likely to keep changing over the coming months. Either way, an agent can only work with clean, accessible base data, no matter which protocol connects it. Shops that invest in structure now, rather than in a single protocol, are already prepared for whatever comes next.

Why Accessibility Is the Technical Foundation for Agentic Commerce

AI agents parse a website much like a screen reader does, reading the code rather than the visual layout. The very criteria that semantic HTML, ARIA labels, and alt text require under WCAG 2.2 for people with disabilities are what make product data reliably readable and matchable for agents too.

The scale of the gap shows in the WebAIM Million Report 2026, the annual analysis of the world's most visited home pages: 95.9 percent of the pages examined had detectable WCAG failures. The most common error types sit exactly where AI agents also depend on clean data.

• ✓ Low color contrast, affecting 83.9 percent of home pages and making content harder to perceive for people with low vision
• ✓ Missing image descriptions, affecting 53.1 percent, leaving both screen readers and AI agents without any information about the product photo
• ✓ Missing form labels, affecting 51.0 percent, making it harder to fill out cart and checkout fields automatically
• ✓ Empty links and buttons, affecting 46.3 and 30.6 percent respectively, giving neither people nor agents a recognizable purpose

None of these errors are new. They are the same barriers screen reader users have run into for years, and now AI agents run into them too when they try to evaluate product data for a purchase. If the alt text is missing, neither a person with a visual impairment nor an agent knows the color or material of the product, and both move on to a better documented alternative. Accessible structure is therefore also what makes a shop legible to search engines and AI-driven answer systems in the first place.

The European Accessibility Act and the Legal Duty for Online Shops

Independent of Agentic Commerce, the European Accessibility Act (Directive 2019/882) has applied across the EU since June 28, 2025, through each member state's national implementing law, Germany's being the Barrierefreiheitsstärkungsgesetz. It covers any provider offering e-commerce to consumers in the EU, regardless of where that provider is based, and its requirements align with WCAG 2.2 and EN 301 549. A narrow exemption exists for microenterprises with fewer than 10 employees and annual turnover or balance sheet totals of no more than 2 million euros, but only for those providing services, not for those placing covered products on the market. A small shop that sells goods is therefore still bound by the accessibility duty in almost every case.

The requirements the EAA already demands are the same ones that prepare a shop for Agentic Commerce. Meeting the legal duty gets you most of the way into the new sales channel as a side effect.

Practical Steps for Your Online Shop

None of this requires a full relaunch. Most of these steps can be rolled out gradually, without touching your design or platform. To make product data accessible to both people and AI agents, focus on the following.

• ✓ Structured product data, consistent and complete for price, availability, and attributes, ideally marked up with Schema.org
• ✓ Meaningful alt text for every product image instead of placeholders or file names
• ✓ Semantic HTML instead of unstructured div elements, so headings, lists, and product cards are clearly identifiable
• ✓ ARIA labels for interactive elements such as the cart, filters, and size selection
• ✓ Sufficient color contrast and labeled form fields throughout the checkout, so neither people nor agents stumble over price or quantity fields

None of these points are new, all of them are already part of the WCAG 2.2 criteria and therefore a legal requirement already. What is new is simply who is reading along now.

How SiteCockpit Prepares You for Agentic Commerce

easyMonitoring automatically scans your shop for WCAG barriers, flagging missing alt text, weak contrast, and unclear structure, and prioritizes what to fix first instead of leaving you with one long, unsorted error list. easyAlt fills in missing image descriptions automatically with AI, and the Contrast Checker tests color contrast in real time, right in the browser, before a new product page even goes live. Step by step, that builds a product data foundation that is both WCAG-compliant and cleanly readable for AI agents, whichever protocol ends up connecting to it.

Accessibility is no longer just a compliance checkbox, it is the technical foundation for being found and selected at all in the new Agentic Commerce channel, on top of the existing duty under the EAA and, in Germany, the BFSG. Shops that lay this foundation now are ready on both fronts, for people and for agents, and will not have to start from zero with the next protocol that comes along.