OC Systems Agency
Accessibility Care

Your Store Changes Every Week. Its Accessibility Changes With It.

Technical accessibility auditing, remediation and monthly monitoring for e-commerce

We identify and remediate common digital accessibility issues and help businesses maintain a more accessible website over time. Not a one-off certificate and not a legal opinion — a technical review of what is actually broken, the work to fix it, and a check each month on what changed.

WCAG technical reviewKeyboard navigationForms & labelsAlt text & headingsContrastMonthly re-scan
Check Your Store for Accessibility IssuesContact Us

Accessibility is not a project you finish

A store that was carefully built and checked in March can be substantially less accessible by June, and nobody did anything wrong. E-commerce sites change constantly, and almost every kind of change can introduce a new issue.

  • ✗New products added with no alt text, or alt text auto-filled with the file name
  • ✗New landing pages built in a page builder with heading levels used for size, not structure
  • ✗A theme update that changes focus styles, or removes them entirely
  • ✗An app installed that injects a popup no keyboard user can dismiss
  • ✗A promotional banner with text over an image, at a contrast that fails on mobile
  • ✗A redesign that makes the whole checkout flow prettier and the form labels decorative
  • ✗Product variant selectors that work by mouse and are invisible to a screen reader

There are two reasons this matters and it is worth being clear about both. The first is that customers who cannot use your checkout do not complain, they leave — a broken variant selector is a conversion problem before it is anything else. The second is legal exposure, which is real for e-commerce and which we are not qualified to advise you on. What we can do is the technical work; a lawyer does the rest.

What the Audit Covers

Keyboard navigation — can the whole purchase path be completed without a mouse, and is focus ever visible
Forms: labels, required-field indication, error messages tied to the field they belong to
Alt text across product images, collection images, banners and decorative graphics
Heading structure — real document outline rather than headings picked for their size
Colour contrast on text, buttons, badges and text-over-image banners
Buttons and links: elements that behave as controls but are not marked up as controls
Theme-level issues that affect every page at once
App conflicts — popups, chat widgets, review widgets and upsell apps that trap or hide focus
Product page specifics: variant selectors, quantity controls, image galleries, size guides
Mobile accessibility, including touch target size and zoom behaviour
Checkout path, tested end to end as the highest-cost place to have a problem

What happens each month

The audit is the start. The reason this is a care plan is what comes after it.

What happens each month1Automated scan across templates, new products and new pages2Manual check of the paths automation cannot judge — keyboard,focus order, screen reader3Compare against last month: what regressed, what a theme orapp update changed4Fix what is fixable in the theme and templates5Re-test the fixes rather than assuming them6Report: what changed, what was fixed, what is still open andwhy

How We Work

1

Audit against WCAG criteria

Automated tooling for the things machines are good at, plus manual keyboard and screen-reader testing for the things they are not. You get findings written plainly, grouped by where they occur and ordered by impact on the buying path.

2

Remediate in the theme

We fix what the audit found, in the theme and templates rather than with an overlay script. Anything that cannot be fixed without breaking function gets documented with the trade-off explained, not quietly skipped.

3

Monitor as the store changes

Every month we re-scan new products, new pages, theme updates and newly installed apps, fix the regressions, and tell you what moved. This is the part that keeps the March audit from being obsolete by June.

Audit, Remediate, Then Maintain

Most stores need the first two once and the third continuously, because the store keeps changing.

Step 1

Accessibility Audit

A technical review against WCAG criteria across your templates: keyboard navigation, forms and labels, alt text, headings, contrast, buttons and links, and mobile.

$1,200 one-time

Step 2

Remediation

We fix what the audit found, in the theme and in the templates, and re-test. Issues we cannot fix without breaking something are written up rather than quietly skipped.

From $1,800

Ongoing

Monthly Accessibility Care

Stores change constantly. Each month we re-scan new products, pages, theme updates and newly installed apps, fix regressions, and report what changed.

$600 / month

Frequently Asked Questions

Will this make my website ADA compliant?
We will not tell you that, because nobody honestly can. Compliance is a legal determination, it depends on facts and jurisdiction, and it is not something a vendor certifies by finishing a task list. OC Systems provides technical accessibility auditing and remediation services and does not provide legal advice or guarantee legal compliance. What we do is identify and remediate common technical accessibility issues measured against WCAG success criteria, and help you keep the site in better shape as it changes. Be sceptical of the usual signals that a promise is being made anyway: a compliance badge for your footer, a certificate with a date on it, a guarantee against demand letters, or a fixed price to make you compliant. None of those describe work that can actually be delivered. If you need an opinion on legal exposure, that is a question for an attorney, and it is worth asking before you buy remediation rather than after.
What about the accessibility overlay widgets?
We do not install them as a fix. An overlay is a script that sits on top of your markup and adjusts what it can at runtime, which means the underlying issues stay exactly where they were: an unlabelled form field is still unlabelled, it is simply being guessed at by a second layer. Some assistive technology works less well with an overlay present, because it duplicates or overrides behaviour the user's own software already provides, and the people who rely on that software are the ones saying so. Overlays are also regularly named in the complaints they were sold to prevent. Fixing the theme is more work and it changes the actual experience, which is the only thing that matters to somebody trying to check out. If you already have one installed we will not make removing it a condition of working together, but we audit with it switched off, because that is the real state of your store.
Which standard do you test against?
WCAG success criteria, which is the reference point most commonly used in this area. We report against specific criteria rather than a single pass or fail score, because a score hides which issues sit on your checkout and which sit on a blog post nobody visits. Those two are not comparable, and averaging them into one number makes the report less useful rather than more. Findings come back grouped by where they occur, whether that is the theme, a template, an app or a single page, and ordered by their effect on the buying path, so the first thing you read is whatever stands between a customer and a completed order. It also matters that much of this is not machine-checkable. Automated tooling is good at contrast ratios and missing alt attributes, and useless at judging whether focus order makes sense or whether alt text describes the right thing, so those are tested by hand.
Can you fix everything you find?
Not always, and we will say which. Some issues live inside a third-party app, in checkout surfaces the platform does not let us edit, or in a widget served from somebody else's domain entirely. For those we document the issue, name who does control it, and where a replacement app is the realistic answer we say so, because swapping a review widget is usually cheaper than fighting one. There is a second category worth flagging: fixes that are technically possible but would break something a customer depends on. A variant selector rebuilt properly might lose an interaction the theme relies on, or a contrast fix might mean changing a brand colour. We write those up with the trade-off explained and let you decide, rather than quietly skipping them or shipping the change and hoping nobody mentions it. Anything we cannot fix stays on the report until it is resolved or consciously accepted.
Is this only for Shopify?
Shopify is where most of our e-commerce work is, so it is where we are fastest: we know which themes lose focus styles on update and which app categories tend to trap keyboard users. The audit itself applies to any e-commerce site, because WCAG criteria are not platform-specific and a keyboard test is a keyboard test. What changes is remediation, and that depends entirely on how much access we have. A Shopify theme we can edit directly. WooCommerce or a custom build we can usually work in given repository access, or we hand your developer a written list of specific changes with the criteria attached. The hard case is a hosted platform that does not expose its templates: there the audit is still worth having, but a share of the findings will be things only the vendor can fix, and we will tell you that before you buy rather than in the report.
Does accessibility work help SEO?
Some of it overlaps. Real heading structure, descriptive alt text, meaningful link text and proper form labels are all things search engines and AI systems read too, and a page with headings chosen for their size rather than their meaning is harder for a screen reader and harder for anything trying to extract a passage from it. So that part does double duty. But it is a side effect, and the overlap is smaller than accessibility vendors tend to imply. Colour contrast, focus visibility, touch target size and keyboard operability, which between them are most of what actually fails on a store, do nothing for rankings at all. If your reason for doing this is SEO, buy SEO, because it is the more direct route and you will get more of it for the money. Do accessibility work because customers cannot currently finish your checkout, which is the reason that pays for itself.

Last reviewed by the OC Systems Agency team.

OC Systems provides technical accessibility auditing and remediation services and does not provide legal advice or guarantee legal compliance.

Check Your Store for Accessibility Issues

Send us your store URL. We will run an initial technical review and show you what is failing today — the theme-level issues, the app conflicts and anything sitting on your checkout path.

Check Your Store for Accessibility Issues

👋 Hi! I'm Jordan

Tell me about your business — I'll find the right way to grow it.