Should a cookie banner move keyboard focus on load?

It should be reachable early and predictably. Whether it takes focus automatically depends on whether it blocks the page. If it blocks interaction, focus belongs inside it until the shopper chooses, and then it must be released.

Is a reject button required in the first layer?

For a fair choice, yes in practice. Hiding reject inside preferences while accept sits in the first layer draws criticism from privacy regulators and makes the keyboard path far longer for refusal than for acceptance.

How often should banner accessibility be checked?

After every consent platform or theme change, and on a regular monthly pass. Vendor updates ship independently of your release calendar, so a check tied only to your own deploys will miss them.

Can an automated scan verify banner focus behaviour?

No. Scans catch missing names and contrast. Focus order, traps, and focus return need a manual keyboard pass. That is why monitoring programmes pair the scan with a short scripted manual check.

Monitoring Alt Text Drift When Templates and Feeds Rewrite It

November 1, 2026

Alt text rarely breaks all at once. It drifts: a theme update, a feed import, a new app writing filenames into alt attributes. What to monitor and how to sample it.

Nobody deletes alt text in one dramatic commit. It erodes. A theme update changes how the product image component renders. A feed import starts pushing image filenames into the alt field. A merchandising app injects a gallery whose images carry alt text copied from the product title, word for word, including the price.

That is why alt text belongs in monitoring rather than in a once a year audit. The audit tells you the state on the day someone looked. The drift happens on the other 364 days, one deploy at a time, and by the time a complaint arrives the bad pattern is on four hundred products.

The three drift patterns worth alerting on

First, filename alt text. Anything matching an image file pattern, ending in .jpg or carrying a string like IMG underscore a number, is an import or a template fallback doing the writing. Second, title duplication, where alt, product title, and image caption are the same string. A screen reader user then hears the identical text three times in a row, which is worse than a short honest alt in the first place.

Third, the empty alt that is not decorative. Alt attributes go blank when a component is reused for a different kind of image: a lifestyle banner component, correctly marked decorative in the hero, gets reused for an infographic carrying the size information. The attribute is valid. The meaning is gone. Monitoring can flag which templates ship empty alt on which page types, and that template level view is where the fix belongs.

Sample pages, but sample the right ones

A homepage and two product pages will pass while the collection template rots. Sample by template, not by traffic: one page per template type, plus the newest products added since the last check, because new products are where feed and import problems land first.

Keep the check cheap enough to run after every theme change. Pull the rendered pages, list every image with its alt value, and diff against the previous run. New filename patterns, new empty alts on informational images, and alt text that suddenly matches titles across a whole category are the diffs worth a human look. The rest is noise, and a monitoring check that produces noise gets switched off.

Fix the writer, not the image

When a drift pattern shows up on dozens of products, the instinct is to open the first product and fix its alt text by hand. That product gets better and the import rewrites it next week. Every drift pattern has a writer: a feed mapping, a template fallback, an app setting. The monitoring report should name the suspected writer alongside the affected pages, so the fix goes to the source and the same report next month can confirm it stayed fixed.

Frequently asked questions

How often should alt text be monitored?

After every theme or app change at minimum, and on a regular monthly sample by template. Drift follows deploys and imports, so tie the check to those events rather than to an annual audit.

What is the clearest sign of alt text drift?

Filenames appearing as alt text, or alt text that suddenly duplicates the product title across many products at once. Both point to a feed or template change, not to individual editing mistakes.

Is empty alt text always a failure?

No. Decorative images should have empty alt so assistive technology skips them. It is a failure when the image carries information, like a size chart or infographic, and still ships with an empty attribute.

Should monitoring cover every page?

Sample by template and by newest products instead. Drift is a template and feed problem, so one page per template plus recent additions catches the patterns that matter without an alert flood.