Capture
The free mini-scan requests only the public home page. Client-authorized assessments crawl the agreed scope.
Methodology / Checklist ssc-1.2
Uditus assesses a website against a published technical checklist. We show what was tested, when it was tested, what failed, and where software-assisted checks stopped. The result is an assessment on a date, not a certification or legal conclusion.
The five-part scan
The free mini-scan requests only the public home page. Client-authorized assessments crawl the agreed scope.
axe-core, Lighthouse, and focused custom checks create structured candidates across four categories.
A keyboard-and-focus harness walks the interface, opens interactive states, and preserves visual evidence.
An expert reviewer removes false positives and judges meaning, hierarchy, context, and usability.
Every finding gets a standard, severity, screenshot or element reference, plain-English impact, and a fix path.
The evidence path
Checks create a consistent starting point. An expert reviewer then reproduces the issue, evaluates its real impact, and turns it into a clear fix.
Capture the page, state, and affected element.
Reproduce the issue and remove false positives.
Connect the evidence to user impact and a practical fix.
What we test
Software-assisted checks cover contrast, alternative text, labels, landmarks, heading structure, language attributes, ARIA misuse, and other detectable patterns. Keyboard and focus testing then examines the path a person actually takes. An expert reviewer decides whether alternative text is meaningful, the content hierarchy makes sense, and color is carrying information on its own.
The public pass observes HTTPS, transport configuration, security headers, and visible technology signals. Deeper checks happen only inside a signed scope. We do not enumerate private paths or probe a third party's server during an unsolicited mini-scan.
We review broken links, mixed content, basic privacy and consent surfaces, insecure form endpoints, maintainability signals, and other small failures that quietly erode trust.
Published scoring model
Checklist ssc-1.2 weights accessibility at 76 because usability is what we are actually assessing. It scores three categories, not four: performance was removed in ssc-1.2 because nothing in the scan measured it, and a category that cannot fail scores every site 100. Every full report includes the item-level calculation, and every scan records the checklist version that produced it — scores from different versions are not comparable.
WCAG-based checks plus expert review of keyboard access, focus, structure, and content.
Transport security, headers, exposed technology risk, and authorized deep checks.
Broken links, mixed content, privacy basics, forms, and maintainability signals.
Responsible scanning policy
Unsolicited mini-scans request a public home page once. No path enumeration.
We honor robots.txt, X-Robots-Tag, explicit opt-outs, and permanent suppression.
Per-domain ceilings and approximately 30-day caching prevent repeated load.
Multi-page and interactive audits begin only after the site owner signs the scope.
Where software stops
Repeatable checks preserve consistent evidence across every assessment.
Focus order, traps, modals, and keyboard paths expose failures static code misses.
Context, useful text, real hierarchy, and false positives require expert review.
Findings are written for any competent developer, not only for Uditus.