Accessibility statement

In short

• BarrierOps has not completed an evaluation of its own product against WCAG 2.1 level AA, so it does not claim a conformance status.
• What runs today is automated, and it runs on every change: every route of the product and of this site is scanned in 3 browser engines, and any violation fails the build. That is the floor, not the finish line. The cookie banner on this site is outside that scan: another company serves it, and it can change without a build. We last checked it by hand on 10 October 2026.
• If something in the product or on this site is blocking you now, write to accessibility@barrierops.com and a person will do it for you while we fix it.
• We acknowledge within 1 business day and answer within 5 business days.
• The conformance report this statement will summarise is not written yet. This page says so rather than linking one.

Conformance status

BarrierOps does not yet claim a conformance status for its own product. The 3 phrases above are conclusions of an evaluation, and none of the 8 flows our accessibility contract names has been run against assistive technology by a person. What exists today is the automated floor below, and the defects it has already found and closed.

Our own rubric for reviewing a vendor’s conformance report treats zero non-supporting entries as a red flag rather than a green one. A vendor who tells you nothing is broken has usually not looked.

We have not finished looking. This page is where that is written down, and it stays here until the evaluation is done and this section says something else.

What was evaluated, and how

Eight flows, named individually, not “the application”.

1. Sign-in, including multi-factor authentication
2. Asset creation and ownership verification
3. The issue list, with filtering and sorting
4. Issue detail and a status change
5. Evidence export and chain verification
6. Report download
7. A manual test run, executed end to end
8. The public barrier-report form

The 8 flows above are the test scope. None of them has been executed against assistive technology, so this page names them as the plan rather than as a record.

What runs today

• Every route of the application and of this site is scanned against WCAG 2.1 A and AA in Chromium, Firefox and WebKit, on every push. Any violation fails the build; there is no allowlist and none may be added. One automated engine runs today — the footer names the three the product is built to use.
• Every colour pair the design system declares is recomputed from the stylesheet and fails below its threshold, rather than being read off a table somebody wrote once.
• Every route is measured at 320 px for horizontal scrolling, and this site’s tables are rendered to the print stylesheet to confirm each one is still a table, with its column headers, on paper.
• This site is measured by Lighthouse at accessibility 100, performance and SEO at 95 or better, three runs per page, and a page that misses fails the build.

Automated testing detects roughly 30–40% of real barriers. Manual testing covers the rest.

Self-assessed, not third party. The full conformance report, criterion by criterion, is not written yet. What it will contain, the method behind it and why there is nothing in it today are on our conformance report page, which is linked from the footer of every page on this site.

What does not work today

• If you use a screen reader, we do not know how this product sounds. No flow has been run against one by a person. If something is announced twice, or announced as the wrong thing, or not announced at all, we have not heard it — and you may be the first person who does.
• If you use speech input, nothing has been tested with it. Dragon is in our test plan for 2 of the 8 flows and it has not been run against either.
• If you use TalkBack on Android, it is not on our testing schedule at all. That is a gap in the programme rather than a result, and it is in the plan below.
• If you magnify to 400%, half of that is checked on every change and half is not. Every route is measured at a 320 px viewport for horizontal scrolling; the browser zoom setting is not something an automated run applies, so a person has to do it and has not.
• If you use Windows High Contrast Mode, the product is built for it — every icon is drawn in the current text colour and every status carries a shape as well as a colour — and nobody has opened it in either system theme to confirm that the build matches the intent.
• If you tell 4 severities apart by shape rather than by colour, the 4 shapes are drawn and the check that matters has not been done: print them at 16 px, remove the colour, and confirm they are still 4 different things.

The remediation plan

There are no criterion rows yet, and it is not because nothing is wrong. A row here is an entry in our conformance report that is not “Supports”, and the report has not been written because the evaluation behind it has not been run. Rows published without it would be rows invented, which is the failure this page exists to make impossible for us as well as for anybody else.

The gaps in our own testing programme

Naming a gap in our own testing programme, rather than only in our results, is the difference between a statement and a status report.

Criterion rows 0 · Dates met 0 · Dates missed 0 · Programme gaps 7

When we miss a date

A missed date keeps its original date. The row shows the date we said, the new date, and the reason in one sentence, and its status reads Date missed until it is fixed. We do not quietly move a date, we do not remove the row and re-add it, and we do not describe a slippage as a re-prioritisation.

No date has been set and missed, because no date has been set. The rule is published before it is needed, which is the only moment at which publishing it proves anything.

Tell us

Address, and who reads it

accessibility@barrierops.com — a named person, not an alias with nobody behind it. It is checked every business day.

Acknowledgement, and answer

1 business day to acknowledge, 5 business days to answer. The same windows as our security disclosure policy and our privacy notice.

Support hours

09:00–17:00 US Eastern, Monday to Friday, excluding US federal holidays

What to include

What you were trying to do, what happened, and what you were using — the browser, and the assistive technology with its version if you know it. None of that is required; a sentence is enough.

Other ways

Use the contact page for anything else. If email is not workable for you, say so in one line through the contact page and we will find another way.

What you send is treated as a defect report against our own product, not as a support conversation that closes when the thread does. You can ask for its id and we will give it to you.

The evidence ledger that will record who verified the fix, on what date and by what method is specified and not built yet. Until it is, what you get is the id, the change, and an email when it moves — and this sentence is here so that the difference is yours to see rather than ours to gloss.

If that is painful for us, the product is wrong, and we have just received the highest-value bug report we are going to get.

There is no form on this page. An email address is a channel that works with a screen reader, a phone, a colleague and no JavaScript at all.

If you need something done today

If anything named on this page is stopping you doing your job today, we will do it for you while we fix it. Write to accessibility@barrierops.com and say what you need.

• If a table in the product is unusable with your assistive technology, tell us which asset and which filter, and we will send you the same rows in whatever format works for you.
• If a page on this site is unreadable at 400% zoom, tell us which one and we will send you its content as plain text.
• If the 2028 checklist does not read correctly as a PDF, the same content is already published as Markdown and as JSON beside it, and we will send you either.

This is not a favour and it is not a workaround we are proud of. It is the alternative we owe you until the gap is closed, and every time we do it, the corresponding issue moves up the list.

What we test with

Measured on every change, in Chromium, Firefox and WebKit: every route scanned against WCAG 2.1 A and AA with any violation failing the build, every declared colour pair recomputed from the stylesheet, and every route measured at a 320 px viewport for horizontal scrolling.

Planned twice a year and before any revision of the conformance report, and not yet run once:

• NVDA with Firefox
• NVDA with Chrome
• JAWS with Chrome
• VoiceOver with Safari on macOS
• VoiceOver with Safari on iOS
• Narrator with Edge
• Dragon, on two of the eight flows
• Keyboard only
• 400% zoom in a 320 px viewport
• Windows High Contrast Mode

Not on a schedule, and it should be: TalkBack + Chrome on Android. It is in the plan above.

Escalating

• If you do not hear back within 1 business day, write again and put “no reply” in the subject. It goes to a second person. If that does not work, use the contact page and say the accessibility channel did not answer.
• We have no legal obligation to publish this page or to run this channel. We do it because we sell accessibility, and a vendor whose own feedback address does not answer has told you what its product is like.
• If you would rather escalate outside the company, the entity you work for has its own Americans with Disabilities Act (ADA) coordinator and its own grievance procedure, and we will not stand between you and them.

This statement’s own history

• Versioned and immutable per version. This is version 1. When a second version supersedes it, this text stays retrievable — a statement whose earlier wording has vanished is not a record, and there is nothing to link to yet because nothing has been superseded.
• Reviewed at least every six months, and always after a revision of the conformance report. Next review 18 March 2027.
• It is not yet served at /.well-known/accessibility, which is the convention we ask customers to use for their own statements. That is written down as owed rather than left unsaid.

What this statement is not

• It is not a certification. Nobody issues one and we would not display one. It is not legal advice, and it is not a statement about any customer’s own website.
• It is not a claim that this product makes any website conformant. BarrierOps finds and reports issues against WCAG 2.1 AA success criteria and records what your team fixed and who verified it.
• It is not permanent. It describes 18 September 2026 and it is reviewed every six months.

Our vulnerability disclosure policy is at barrierops.com/security/disclosure and it is a different channel with a different clock. A barrier is not a vulnerability and neither address is a redirect to the other.