About BarrierOps
We build accessibility compliance operations software for state and local government. We do not build overlays, scores or compliance verdicts, and this page says why.
Why we built this
A public entity does not need to learn that it has 14,000 problems. It needs to prove what it tested, what it fixed, who verified it, what remains open, and why. Every competitor sells discovery and treats the evidence as a PDF export.
The two most visible vendors in this market sell a script you paste into your page. The claims made for those scripts have drawn regulatory action and public-sector exclusions, and the buyers we talk to have already met them. We do not name them on this page; what we will not build says the same thing about us instead of about somebody else.
The evidence ledger is the product. Scanning is a feature of it. The tamper-evident record is the thing a lawyer can use, so it is the thing we built first.
What we will not build
- An overlay, a widget, or any injected script
- It does not fix the site, it cannot be verified, and the claims made for it are what brought regulatory action to this category.
- A score, a grade or a ranking of one entity against another
- A single number that averages contrast against keyboard operability means nothing, and it is the number that gets quoted after everything else is forgotten.
- Automatically generated alternative text
- No code path in the product generates, suggests or applies it, and a test reads the whole repository on every build to confirm that none has appeared.
- AI-generated fixes presented as verified
- The product makes no AI suggestions. If it ever does, they will be off by default, never applied on their own, never counted as verification, and labelled “AI suggestion — not verified. Review before applying.”
- A certificate, a seal or a badge
- We are not an accrediting body, and neither is any vendor selling you one.
- The verdict that a site meets the law
- That sentence does not exist in any report, export, template or string table in the product, and a build-time grep is what keeps it out.
- A product tour, a coach mark or a modal on load
- They are a focus-management minefield in a product sold to people who navigate by keyboard.
- A CAPTCHA in any public form
- A cognitive-function test in front of a barrier report is the failure the barrier report exists to catch.
Who does the work
Arsene Ion — Builds the product and answers support
A full-stack engineer working in PHP, Drupal, React and TypeScript, based in Constanța, Romania. Founded BarrierOps in September 2026 and runs it through PTECHIT S.R.L., the company named below.
BarrierOps is 1 person, who writes the code. Support is answered by the person on this list, not by a queue.
Where we are, and how to reach a person
The registered office of PTECHIT S.R.L., as recorded in Romania’s trade register.
- hello@barrierops.com — sales, support and procurement questions
- corrections@barrierops.com — a figure on this site that is wrong
Support hours 09:00–17:00 US Eastern, Monday to Friday, excluding US federal holidays.
How the company is set up
- BarrierOps is run by PTECHIT S.R.L., a limited liability company registered in Romania.
- Romanian trade register number J2025043440008, tax ID 51988476.
- All data is hosted in US regions.
- We invoice in US dollars against a purchase order, net 30 by default.
How we test our own product, and what we have not tested yet
The interface is the sales demonstration in this category: a procurement officer is told to keyboard-test the vendor’s own site before scoring the bid. So our own product and this site are held to the standard we sell, by gates that fail the build rather than by intent.
- 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.
We test eight flows, not “the whole application”, and we say which eight.
No run of the matrix below has been completed yet, and this page will not say otherwise until one has. When it is run, the date, the software versions and the outcome are published with it — including the parts that failed.
- Sign-in, including multi-factor authentication
- Asset creation and ownership verification
- The issue list, with filtering and sorting
- Issue detail and a status change
- Evidence export and chain verification
- Report download
- A manual test run, executed end to end
- The public barrier-report form
Against 10 configurations:
- 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
Full matrix twice a year and before any revision of our conformance report. Keyboard-only and 400% zoom on every release.
- Our conformance report (VPAT 2.5Rev)
- Every one of the 50 WCAG 2.1 AA success criteria, with what supports it and what does not. Not published yet.
- Our accessibility statement
- The known barriers in our own product, and a feedback channel a person monitors. Not published yet.
- Our dated remediation plan
- Every entry that is not “Supports”, what fails, and the target date. Not published yet.
A conformance report claiming “Supports” on all 50 criteria reads as untested. When ours is published, every entry that is not “Supports” will carry a dated plan beside it, and this page will link the plan and the report together.
How we make money
- We sell software at a published price. The price is on the pricing page and it is not negotiable below the published figure without a written reason.
- We take no commission on remediation work, no referral fee from any agency, and no payment from any vendor named anywhere on this site. If that ever changes, it is disclosed on this page and beside every affected recommendation.
- We pay for no reviews, no placements and no articles. Any paid or incentivised review, article or post about us is disclosed as such wherever it appears.
Every price is on the pricing page, not behind a form.
What we will not say
- That your website meets the ADA, conforms to WCAG in full, or has no barriers left. No report, badge, export or tooltip we produce says any of it.
- That we guarantee compliance or protect you from litigation.
- Any percentage of the WCAG standard satisfied. A percentage of automatically detectable issues is a real number and we use that instead.
- That any government body has accredited, endorsed or approved us.
- Nothing implying government endorsement — no federal seal, no agency logo, no department name used as a badge.
- No testimonial from a serving public official with their title attached.
When we get it wrong
Every figure on this site is sourced or it is not stated. If you find one that is wrong — a procurement threshold, a deadline, a coverage percentage, a claim about a standard — write to corrections@barrierops.com and we will correct the page and say when it changed. Corrections are dated in place, not silently edited.
Questions people ask before buying
How big is the company?
Small: 1 person, named above. The price reflects that, and so does the support model: you reach the person who builds the product.
What happens to our data if you are acquired or stop trading?
The evidence ledger is hash-chained, and the chain verifies with your own tools — it does not depend on us being here to check it. What happens to the rest of the account in that event is a term in the contract rather than a sentence on a marketing page, and we will send you that clause before you sign.
Do you have SOC 2?
Not yet, and we will not claim it before the report exists. Ask for the current status, the date of the last penetration test and each subprocessor’s own attestation, and you get them in writing.
Who answers support?
The person named above, during the hours above. Support is not a queue in front of a different company, and it is not charged for.
Can you name a customer?
Only with written permission, and never a serving public official with their title. Where a customer permits it, the reference is a real conversation, not a quote on a page.
Why no customer logos?
A logo wall implies an endorsement no customer has agreed to give, and in this market a public entity’s mark is close enough to a government seal to be a problem for both of us.
Anything this page does not answer goes to hello@barrierops.com.