AAI PUBLIC ACCESSIBILITY TEST SITE

This website is supposed to fail.

Aditus is a deliberately imperfect website operated by the Accessibility Assurance Institute (AAI). We built it so developers, accessibility professionals, students and testing tools have a real public website to test against.

The public introduction you're reading is intentionally usable. The fun starts when you enter the test areas.

If you would like to learn how to make sure your site is accessibility compliant, contact us directly at contact@aaiaccess.org or visit us at aaiaccess.org.

WHY WE BUILT IT

Accessibility testing needs something predictable to test.

Real websites contain problems across structure, styling, interaction and application behaviour. Aditus gives the accessibility community a stable target containing known, deliberate faults.

01

Test automated scanners

Scan Aditus with your preferred accessibility testing tool and compare what it discovers with our published test manifest.

02

Practise manual testing

Explore keyboard operation, focus behaviour, forms, semantics, zoom, reflow and other issues that require human judgement.

03

Train developers

See how apparently small coding decisions create barriers for real users — and practise identifying the actual root cause.

04

Demonstrate remediation

AAI uses Aditus to demonstrate the complete journey from evidence to developer task, source-code remediation, validation and retesting.

THE ACCESSIBILITY TEST LAB

One lovely website.
An unreasonable number of accessibility problems.

The laboratory contains deliberately broken images, headings, links, forms, keyboard behaviour, ARIA, tables, dialogs, dynamic content, focus states, responsive layouts and more.

We deliberately exclude dangerous demonstrations such as flashing content and inescapable keyboard traps.

MEET THE DEMONSTRATION COMPANY

Aditus looks real because it needs to behave like a real website.

Aditus is our fictional demonstration organisation. Its pages work, its navigation works, its forms work and its source is split across PHP, CSS, JavaScript and SVG files. The accessibility problems are deliberate.

COMMUNITY. ACCESS. POSSIBILITY.

Practical services that help people participate fully.

Aditus works with communities, organisations and individuals to make everyday services simpler, clearer and more useful.

What Aditus does

Community support

Practical guidance and local support for people and families.

Learn more

Training

Straightforward training for teams delivering public services.

Learn more

Digital help

Simple digital services designed around real-life needs.

Learn more

Latest community update

Saturday drop-in sessions are now available.

This repeated ID is deliberate.

Show this week's update

Quick enquiry

AUTHENTICATED TESTING

Need a login-protected accessibility target?

Aditus also includes a deliberately public demonstration account. Use it to test authenticated crawling, protected-page scanning, login workflows and accessibility behind authentication.

Public demonstration credentials

Email
demo@aditus.ie
Password
AditusDemo2026!

These credentials are intentionally public and provide access only to fictional demonstration content. They are not connected to AAI user accounts or any production system.

Open demo login

After signing in, explore the protected demonstration area and test authenticated accessibility workflows.

HOW AAI USES ADITUS

Find it. Fix it. Prove it.

  1. 1
    Find

    Automated and manual testing identifies accessibility barriers and captures evidence.

  2. 2
    Fix

    Developer Studio connects the evidence to the relevant source and remediation work.

  3. 3
    Prove

    Validation and retesting provide evidence that the remediation actually resolved the problem.

ACCESSIBILITY ASSURANCE INSTITUTE

Finding accessibility problems is only the beginning.

AAI brings scanning, manual testing, developer remediation, evidence and verification together in one accessibility assurance platform.

Explore AAI

A note about this website

Parts of Aditus intentionally contain accessibility barriers. These examples exist for testing, education and product demonstration and must not be treated as examples of recommended development practice.