Enterprise DNA

Instead of Siteimprove

Review your Siteimprove renewal. Own the work behind every fix.

We build your accessibility worklist and evidence record around your team, bring across your agreed Siteimprove exports and run the system for you. Keep a clear record of who fixed each issue and which evidence still applies.

Siteimprove does not show a standard price on the pricing route checked for this comparison. Use your quote to separate testing, support and the work you want to own.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Start with the renewal

Separate the testing service from the work record

Siteimprove combines testing, issue reporting and other website services. Compare the parts your team uses with an owned record for assignments, corrections and review evidence.

web

The pages in your package

Siteimprove publishes page-count allowances in its public-sector packages. Check the scope in your own agreement before comparing costs.

fact_check

Finding the barriers

Accessibility scanning is a distinct job. Agree how your sites will be tested and who will perform the manual assessment alongside your owned work record.

view_list

The list of issues

Siteimprove already shows issues across sites and lets you drill down to affected pages. Those exported records can become your own worklist.

person

Who made the correction

Siteimprove says its Accessibility module does not show who corrected specific issues. Your version records the person, the change reference and the later retest.

description

Reports for a review meeting

Siteimprove offers fixed-issue and progress reporting. Your version assembles a remediation plan, evidence record and exception register around your meeting.

support_agent

Support and wider services

Review the support package and any other website services in your agreement. Enterprise DNA scopes the records, connections and ongoing operation you actually need.

Your own operating record

A fix is only useful when you can trace what happened

Ownership

A named person behind the change

Connect the finding to the person who recorded its correction, then keep the evidence beside it.

  • check Record who made each fix
  • check Keep the change reference and notes
  • check Identify work with no owner
  • check See the history behind a review decision

Evidence

A pass that belongs to the current version

An old passing result stops counting when its finding, page or recorded fix changes.

  • check Tie each retest to the version reviewed
  • check Let a later failure supersede a pass
  • check Flag evidence made stale by a release
  • check Keep the supplied evaluator and test method

Review

A weekly meeting with the loose ends visible

Bring overdue work, critical journeys and unfinished assessment scope into the same review.

  • check Group overdue findings by owner
  • check Track barriers on important journeys
  • check Show sites without a completed manual audit
  • check Keep accepted risks separate from resolved findings

Paperwork

Documents carrying your business name

Prepare the records your team needs to explain what was assessed, what changed and what still needs work.

  • check Prepare a remediation plan for each site
  • check Produce an audit evidence pack
  • check Review risk decisions and expiry dates
  • check Draft statement notes for a human to finish

Make it yours

Design your own Siteimprove replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Siteimprove. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Siteimprove replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Siteimprove data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Actual output from the fictional records included with the free version. Names and evidence references are synthetic. No website was scanned to produce these examples.

forum

Accessibility Operations for Claude Code

Connected to your own database

Which accessibility fixes need attention this week?

code | site | title | owner | reason --------+---------+---------------------------------------------------+------------+------------------ A11Y-01 | SHOP | Payment step cannot be reached by keyboard | Mara Chen | critical_journey A11Y-03 | SERVICE | Required fields have no visible instructions | Owen Patel | critical_journey A11Y-06 | SERVICE | Third-party document viewer blocks keyboard users | Owen Patel | critical_journey A11Y-06 | SERVICE | Third-party document viewer blocks keyboard users | Owen Patel | expired_exception A11Y-02 | SHOP | Product images have no text alternative | | missing_owner A11Y-01 | SHOP | Payment step cannot be reached by keyboard | Mara Chen | overdue_fix A11Y-02 | SHOP | Product images have no text alternative | | overdue_fix A11Y-06 | SERVICE | Third-party document viewer blocks keyboard users | Owen Patel | overdue_fix A11Y-01 | SHOP | Payment step cannot be reached by keyboard | Mara Chen | stale_retest

Ask it anything

Questions your accessibility review should answer

These questions run against the working demo. They show your own review process, without claiming that Siteimprove lacks every one of these views.

chat_bubble Which critical journeys still have an open barrier and who owns the fix?
chat_bubble Which passing retests belong to an older page or finding revision?
chat_bubble Who recorded each fix, and what evidence did they attach?
chat_bubble Which owners have the most overdue accessibility work?
chat_bubble Which accepted risks have expired or been invalidated by a change?
chat_bubble Which sites have no recorded completed manual audit?
chat_bubble Which criteria recur across several pages and sites?
chat_bubble Which findings have no owner or agreed completion date?
chat_bubble Which sites need a review of why personal information is retained?
chat_bubble What changed in the record, who changed it, and what did it say before?

Switching

How to switch from Siteimprove

The move involves exporting your findings, mapping your fields, checking the import and running both systems side by side before you switch.

  1. 1

    Export your findings

    Use Siteimprove’s Cross Site Accessibility Issues widget to export page-level findings. Siteimprove documents CSV downloads. Aim for one row per page and issue, or use a per-issue export where the issue name appears once. Siteimprove offers several export views, so check the scope and fields available in your account before you start.

  2. 2

    Review the export

    Check that the export includes the page-level findings you want to bring across and note how its column names relate to your own fields. Decide which history you need before importing. The free import covers page-level findings and retains the original columns. Historic attachments and assessment records need separate migration scope.

  3. 3

    Test the import

    Load the export as a test run first, without saving changes. If the column names differ, map them to the fields in the new system. Check the test results before applying the import, and confirm that the export scope and the records you intend to bring across match. Ask Siteimprove about the available export fields if the layout is unclear.

  4. 4

    Check the import results

    Review the counts and any issues the test import reports, then compare the results with the export. Confirm that findings have the right pages and fields, and that the records you expect to bring across are present. A finding missing from a later export is not automatically closed by an import, so check omissions rather than treating them as resolved.

  5. 5

    Run both, then switch

    Keep Siteimprove running alongside the new record for a short period while your team checks that it can manage findings, owners, retests and review evidence. Once you have checked the records and agreed the operating process, switch off Siteimprove for that record-keeping work. Keep or commission the testing tools and human assessment your scope still requires.

construction

Where the real effort goes

Most of the work is mapping your own fields and review rules, then deciding which history to bring across. Page-level findings are supported by the import, while historic attachments and assessment records need separate migration scope. If you have Enterprise DNA run the system, they handle the agreed mapping and reconciliation as part of the customised setup.

Not ready for a call?

Get your Siteimprove switch plan by email

We will send you the step-by-step plan for moving your business off Siteimprove, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it built, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm ci, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Import a page-level Siteimprove CSV export after checking its headers
  4. 4 Ask for your review, then customise the fields and rules you need
Get it on GitHub

Built around your business

We customise it

A scoped setup fee

  • check We map your agreed Siteimprove exports
  • check We add your fields, review rules and documents
  • check We build a web front end when you need one
  • check We can use a different stack to fit your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check We install your system and bring the agreed records across
  • check We connect the testing and business systems in your scope
  • check We operate the records, reporting and agreed review workflows
  • check It runs inside Omni by Enterprise DNA with your wider business
Book a call with Sam

Questions

Instead of Siteimprove, answered

Does this replace the whole Siteimprove service? expand_more

The free version covers accessibility findings, fix ownership, retest evidence and review documents. Testing tools and expert assessment remain part of the scope we agree with you. Enterprise DNA can connect those services and build the screens your team needs in your custom version.

Can we bring our existing findings across? expand_more

Yes. Siteimprove documents CSV downloads from its cross-site issue widget. The free version imports page-level findings and retains the original columns. Check the export layout first. We handle the agreed mapping and reconciliation in a customised version; historic attachments and assessment records need their own migration scope.

Will a clean worklist prove our website is accessible? expand_more

No. A recorded passing retest applies to that finding and version. Website conformance depends on the assessment scope and human evaluation. The system keeps the evidence and unfinished work visible so your reviewer can make an informed assessment.

What happens when a release changes the page? expand_more

Record the page change and the old passing evidence stops counting. A reviewed fix and a new retest are needed for the current version. Time-limited risk decisions also stop applying when the underlying page or finding changes.

What do we pay Enterprise DNA? expand_more

The source is free. We agree a setup fee for your records, rules, documents and connections. Ongoing operation through Omni by Enterprise DNA is then a retainer. Bring your Siteimprove agreement so the comparison uses your actual scope and renewal.

Bring your Siteimprove renewal and one review pack

In 30 minutes with Sam, map the records you need to own, the testing you need to retain and the version Enterprise DNA can build and run for your team.

Book 30 minutes with Sam Get the free version

Accessibility Operations for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Siteimprove?

Get your version built