ADDA first pilot product

Pilot

Document Accessibility Assistant

An AI-powered tool that helps you identify and understand accessibility issues in your documents, without needing to be an accessibility expert first.

The Document Accessibility Assistant is ADDA's first AI-powered product. It is part of the broader ADDA platform, which also offers accessibility consulting, training, and course support. The assistant is currently available to a small group of pilot participants only. It is not yet publicly available.

The problem

Creating accessible documents is harder than it should be

[Placeholder: one sentence capturing the core frustration visitors already feel about document accessibility. Replace with final copy.]

Most documents are not accessible by default. PDFs with missing tags, Word files without proper heading structure, presentations with no alt text, and forms that screen readers cannot navigate are common problems across every industry. Finding them takes time. Fixing them takes knowledge most people do not have.

[Placeholder: one to two sentences about the risk or cost of leaving this unaddressed. For example: legal risk, reputational risk, or the people who cannot access your content. Replace with final copy.]

[X%]

[Placeholder: a relevant statistic about inaccessible documents or digital content. Replace with a verified source.]

[X]

[Placeholder: a second relevant fact or figure. Replace with a verified source.]

[X]

[Placeholder: a third fact or figure if available. Remove this card if not needed.]

What it does

Your document reviewed. Issues explained. Next steps clear.

[Placeholder: one sentence describing the core experience of using the assistant. Replace with final copy.]

[Placeholder: two to three sentences describing the end-to-end experience. What does the user do, what does the assistant do, what does the user receive? Replace with final copy when ready.]

[Placeholder: one sentence about what makes the assistant's output useful and practical, not just a technical report. Replace with final copy.]

What the assistant looks at

  • [Placeholder: accessibility check one, for example heading structure and reading order]
  • [Placeholder: accessibility check two, for example image alt text]
  • [Placeholder: accessibility check three, for example colour contrast]
  • [Placeholder: accessibility check four, for example table structure and form labels]
  • [Placeholder: accessibility check five if applicable]

Who this is for

The document accessibility assistant is designed for people who work with documents regularly and need a practical, accessible way to improve them.

  • Educators and course creators

    [Placeholder: one to two sentences about how educators use the assistant to check course materials, PDFs, and handouts. Replace with final copy.]

  • Professionals and content teams

    [Placeholder: one to two sentences about professionals who create reports, guides, or client documents. Replace with final copy.]

  • Organizations with large document libraries

    [Placeholder: one to two sentences about organizations that need to review existing document collections for accessibility compliance. Replace with final copy.]

What you get

Practical accessibility support without the guesswork

  • Clear findings, not just a technical report

    [Placeholder: one to two sentences describing this benefit in plain language. Replace with final copy.]

  • Actionable next steps you can act on straight away

    [Placeholder: one to two sentences describing this benefit. Replace with final copy.]

  • Your document stays private

    [Placeholder: one to two sentences about privacy and security. Replace with final copy.]

  • No accessibility expertise required

    [Placeholder: one to two sentences about how the assistant explains issues in plain language. Replace with final copy.]

Current status

Pilot

Currently available to pilot participants only

The Document Accessibility Assistant is not yet publicly available. It is currently being tested with a small group of pilot participants as part of ADDA's product development process.

[Placeholder: one to two sentences about what the pilot involves. For example: what participants get access to, how long the pilot runs, or what ADDA is looking for in pilot participants. Replace with final copy.]

If you are interested in joining the pilot or being notified when the product becomes more widely available, request access below or start a conversation with ADDA.

What pilot means

  • Limited access, by invitation or request only
  • Not available through public self-serve
  • Active development in progress
  • [Placeholder: any other relevant pilot condition]

What it is not

  • Not a publicly available product yet
  • Not available to purchase or subscribe to
  • Not a finished or final product

Interested in the pilot?

Request access or start a conversation. ADDA will be in touch to discuss whether the pilot is a good fit for your situation.