Reviewed October 14, 2026

How to document Shopify accessibility fixes so they hold up

Keep a dated log for every fix: the barrier found, how it was reported or tested, what changed, who changed it, and how you verified it afterward. Store the log with your accessibility statement updates. If a complaint or demand letter arrives, that record shows good faith effort in a way memory and good intentions cannot.

Why the record matters as much as the fix

Accessibility work is judged over time. A store that can show two years of audits, fixes, and retests looks very different from a store that fixed the same issues the week a letter arrived, even if both sites are identical today.

Documentation also protects you internally. Staff change, developers rotate, and themes get replaced. Without a record, a fixed barrier quietly returns in the next redesign and nobody knows it was ever addressed.

What each entry should contain

Five fields cover almost everything: the date, the page and barrier in plain language, how it was found, the fix applied, and the verification step. Add a screenshot or a short note of the test used when you can.

Keep the language factual. Write keyboard focus not visible on cart drawer, fixed by restoring outline style, verified by keyboard test, rather than vague entries like improved accessibility. Specific entries are credible; vague ones read as decoration.

Where to keep the log

A shared document or spreadsheet linked from your accessibility statement working files is enough for most stores. The point is that one named person owns it and every fix, audit, and complaint response gets an entry the week it happens.

Note your audits too, including audits that found nothing major. A pattern of regular checking is itself evidence of an ongoing program, which is what reviewers and courts look for.

Document complaints and your response

When a customer reports a barrier, log the report, the date you replied, and the fix or the reason a fix is scheduled later. A prompt, recorded response is one of the strongest signals that a store takes access seriously.

If a barrier cannot be fixed quickly, document the interim help you offered, such as taking an order by email, and the date the real fix shipped. Temporary workarounds count when they are real and recorded.

Turn the log into a routine

Review the log quarterly alongside your accessibility statement date. Update the statement, close out stale entries, and schedule the next audit from the same document so documentation and the work itself stay in step.

Tie entries to theme and app changes. When a redesign launches, a fresh audit entry and a round of fixes is normal. Showing that rhythm over years is the whole point of keeping the record.

Frequently asked questions

Does documenting fixes create legal risk by admitting problems?

Stores worry about this, but a record of finding and fixing barriers generally shows good faith and an active program. The bigger risk is having no record at all when asked what you have done.

How long should I keep accessibility records?

Keep them for years, not months. Older entries showing a consistent pattern are valuable, and storage costs nothing. Treat the log like tax records rather than chat messages.

What should I do if a fix is too expensive to do now?

Log the barrier, the quote or reason, the interim workaround you offer customers, and the planned date. A documented plan with interim help is far stronger than silence.

Who should own the accessibility log?

One named person, usually whoever owns the website or ecommerce operations. Shared ownership in theory becomes no ownership in practice, and entries stop happening after the first busy month.