Who it's for

Made for the people who do the work

Axcess was commissioned for an accessibility lead at a large university and designed around the people that lead hands work to. Find yourself below to see what you would actually get.

The accessibility lead

In-house professional responsible for dozens of sites, triaging hundreds of findings in a sitting, often while screen-sharing with an editor who has never seen the tool.

"Find every barrier across this site before the next report cycle, hand a prioritised list to the content team, and verify the fixes."

What you get

  • A prioritised, grouped issue table the moment a scan finishes, scoped to that scan only.
  • A defensible verdict for every finding: the rule, the confidence, the affected users, and the evidence side by side.
  • One-keystroke decisions with a required rationale, so the record shows who decided what and when.
  • A manual review matrix for the criteria no tool can decide, with the procedure for each.
  • Rescan comparison so you spend your time on what changed.

Designed for you, specifically

The interface is held to WCAG 2.2 AAA, works fully by keyboard, reflows to a phone width, and never conveys severity by colour alone. If you use a screen reader, magnification, or keyboard only, the tool was built with you in the room.

The editor or developer receiving the work

You never open Axcess. You open a Jira ticket, a spreadsheet row, or a report and need to know what to change.

"Take the finding, fix the page, mark it done, move on."

What you get

  • Plain-language remediation hints written for you, not for the auditor: what to change and why it helps.
  • The exact page, the exact element, and a snippet, so there is no hunting.
  • A "done when" acceptance note so you know when the fix is complete.
  • Jira import that uses Jira's own column names, and Excel with clickable links.
  • Repeated problems grouped by cause, so one template fix can close hundreds of occurrences.

Leadership and compliance owners

You need to know how exposed a site is, what to fund first, and whether last quarter's work made a difference.

"How thoroughly was this evaluated, what should we fix first, and is it getting better?"

What you get

  • A stakeholder report that states scope, methods, and limitations before it states results.
  • Issues ranked by impact on people, not by a single score that hides the reasoning.
  • A "Who's Affected" view that shows which abilities each issue blocks.
  • Honest coverage: which criteria were checked by a tool, which by a person, and which are still untested.
  • Trend evidence across rescans instead of a fresh, incomparable number each time.

What you will not get

A certificate. Axcess never generates a conformance claim or an Accessibility Conformance Report automatically. A qualified person completes those, using Axcess evidence as input.

IT and security reviewers

You have to approve a tool that crawls institutional websites, some of them behind a login.

"Where does the data go, what does it connect to, and what happens with credentials?"

What you get

  • No cloud service, no account, no telemetry. Evidence lives in a local database in the operating system's application-data folder.
  • Outbound connections only to the site being scanned, plus an optional local AI service on the same machine.
  • Credentials never enter Axcess. The auditor signs in inside a visible browser window; login pages are not stored as evidence.
  • A sandboxed desktop app with a documented security boundary, and open source you can read.
  • A stricter managed mode for sensitive institutional targets, with identity-aware access, encryption, redaction, and short retention. Disabled by default.

Read the full privacy and trust page.

Not designed for

Where Axcess is the wrong tool

Public scanning services

Axcess is a local tool for one operator at a time. It is not a web service anyone can point at any site, and it should never be exposed to the open internet.

Nightly bulk monitoring

The command line can be scheduled, but the interface is built for careful one-at-a-time review, not fleet-wide dashboards.

Automatic certification

No scan proves a site conforms. Testing with people who use assistive technology remains essential.