Is a store liable for its chat widget's barriers?

Yes, in practical terms. The widget is part of the store's public facing service. Vendor contracts should require conformance and fixes, but a shopper's complaint and a regulator's attention land on the store first.

What is the quickest chat widget check?

On a phone, go to checkout and see whether the bubble covers any checkout control, then open and close the panel using only a keyboard or switch device. Those two passes catch the failures that block purchases.

Should chat be removed from checkout pages?

Often, yes. Suppressing the widget during payment removes the overlap and focus risks entirely. Provide a clearly named alternative contact method in the checkout help section instead.

Does the chat button need more than an icon?

It needs an accessible name describing the action, such as chat with support. An unlabelled icon button is announced as just button, which tells a screen reader user nothing about what will happen.

ADA Risk in Embedded Size Charts, Fit Guides, and Care PDFs

November 2, 2026

Size charts arrive as vendor iframes and PDFs that nobody tagged, nobody labelled, and nobody can use with a screen reader. Where the risk sits and how to clear it.

The product page passed its review. Then someone finally opened the size chart. On many stores that chart is an embedded iframe from a fit app, a scanned image of a table, or a PDF uploaded in 2021 and never touched again. A screen reader user gets a frame with no title, a table announced as a picture, or a document that reads as one long run of numbers with no row or column meaning. The store's most practical buying information is the least accessible content on the page.

This is not an edge case in Title III work. Plaintiffs and testers go looking for exactly these components because they are easy to document and hard to wave away: the chart either conveys chest, waist, and inseam measurements to assistive technology or it does not. The good news is that size information is tabular by nature, which makes it one of the easiest content types to publish properly once someone owns it.

Pick the format that can actually be fixed

A real HTML table on the page, or in a properly built dialog, is the gold standard. Headings for the measurement columns, a header cell for each size row, and text a screen reader can move through cell by cell. It is also the format your own team can update when a supplier changes sizing, instead of begging a vendor for a new embed.

PDFs can be made accessible with tagged structure, reading order, and real table markup, but most vendor PDFs have none of that and the store has no source file to remediate. If the PDF cannot be tagged properly, do not keep publishing it alongside good intentions. Replace it with the HTML table and keep the PDF, if you keep it at all, as a secondary download. An untagged PDF as the only route to sizing information is a decision, and it will be read as one.

Iframes and the title that is always missing

If an embed stays, test the frame itself first. WCAG 4.1.2 and 2.4.6 expect a frame title that says what the frame is, like Size chart for the trail jacket, not a blank title or the vendor's name. Then tab inside. Focus should enter, move through the chart controls in order, and leave without trapping. Vendor iframes fail the exit test often enough that it should be the second thing you check, right after the title.

Ask the vendor, in writing, for their accessibility conformance report and their remediation contact. Some fit and sizing vendors have accessible modes that are off by default, or newer embeds that replace the old inaccessible one for the asking. If a vendor cannot answer basic WCAG questions about a component that sits on your checkout path, that is procurement information, and it belongs in the renewal conversation.

Own the measurements centrally

The durable fix is a single owned source for sizing data per product family, rendered as HTML wherever it appears: product page, fit finder result, and help centre. One source means one remediation, one update when measurements change, and no archaeology through nine embedded copies in three formats.

Add size charts to the pre-season checklist. New ranges arrive with new charts, often supplied by the brand as images, and that is the moment inaccessible content enters the site. Catching it at upload, when converting an image table to HTML takes twenty minutes, beats catching it in a demand letter, when the same work comes with a settlement discussion attached.

Frequently asked questions

Is an image of a size chart ever acceptable?

Only if the same measurements are fully available as text or a real table nearby. An image alone, even with alt text that says size chart, does not give a screen reader user the row and column relationships that make a chart usable. A paragraph of alt text listing every number is a poor substitute for a table.

Who is responsible, us or the sizing app vendor?

The store publishing the page carries the legal exposure, whatever the vendor contract says. That is why the vendor's conformance report, remediation route, and an accessible mode setting belong in procurement and renewal, not just in a support ticket after a complaint.

Can we keep offering the PDF as well?

Yes, as a secondary format, if the primary HTML version carries the full information. If the PDF itself is offered as a document customers are expected to use, it should be tagged with correct reading order and table structure. An untagged PDF as the only version is the risky pattern.

What should an iframe title say?

What the frame contains, in the language of the shopper: Size chart for the product name, or Care instructions. Not the vendor name, not embed, and never blank. The title is announced when a screen reader user enters the frame, and it is their only signpost for what is inside.