A new A11yRoo tool · Early access

The PDF is tagged.
Make the edit that matters.

Give an existing tagged PDF a plain-language instruction. This early-access release finds supported spoken-text changes, shows you each match, and creates a review copy while preserving existing tags. Specialist submission is planned; have a specialist review your downloaded copy before final delivery.

Your instruction stays in view. So do the edits it produces.

YOUR INSTRUCTION

“Announce uppercase medication names followed by an asterisk with (brand) before the asterisk.”

PROPOSED ACCESSIBLE TEXTPAGE 6
CurrentTREMFYA *
ProposedTREMFYA (brand) *
Visible page unchanged Existing tag order retained
PRECISE INSTRUCTIONSREVIEWABLE CHANGESEXISTING TAGS RESPECTED

01 / PURPOSE

Keep the good work.
Change only what needs changing.

A PDF may already have sound headings, lists, reading order, and tags, yet still need a targeted accessibility fix. PDF Edit is designed for that moment: work from the tagged copy you have, inspect what an instruction would change, and leave unrelated structure alone.

A deliberate workflow

From instruction to a reviewable PDF.

See the matches, approve the changes, and download a copy for accessibility specialist review.

  1. 01

    Bring your tagged PDF

    Start with a PDF that has already been tagged, whether it came from A11yRoo or another tool.

  2. 02

    Describe the change

    Write what should happen in plain language. The app identifies the relevant content and proposes specific edits.

  3. 03

    Review every match

    Check the affected pages, the before-and-after result, and anything the app could not resolve safely.

  4. 04

    Create a revised copy

    Apply approved changes and run automated checks while preserving the original PDF.

  5. 05

    Specialist review

    Planned: submit the revised PDF to an accessibility specialist. For now, arrange review of your downloaded copy.

A real kind of request

A small change.
A meaningful difference.

A medication list contains uppercase brand names followed by an asterisk. The name should be announced with “(brand),” while the asterisk remains a separate reference.

The proposed edit changes the accessible text for matching names. It does not add “(brand)” to the printed page or move the asterisk out of its reference tag.

This is an illustration of the planned workflow, not a processed PDF.

EXAMPLE PREVIEW01 / 01 MATCH
If an uppercase medication name is followed by *
announce the name with “(brand)” before *
ON THE PAGE

TREMFYA*

Printed content is preserved
PROPOSED ANNOUNCEMENT

TREMFYA (brand) *

The asterisk keeps its own reference

One editor, focused tools

What PDF Edit is being built to handle.

The first tool focuses on accessible text. Other editing tools can follow, each with its own preview and checks.

AVAILABLE NOW

Accessible text

Adjust what assistive technology receives for specific tagged content, such as expanding a label or clarifying how a name is announced.

PLANNED

Images

Review figures and edit their text descriptions.

PLANNED

Links

Review link text and how it connects to its tag.

PLANNED

Tables and structure

Make supported changes to headers, tag types, and relationships.

Built with the A11yRoo approach

The app proposes.
You decide.

PDF accessibility can involve judgment. An instruction may be ambiguous, or a PDF may not provide enough evidence for a safe edit. In those cases, PDF Edit should show what needs review instead of silently changing the file or claiming the instruction was applied. Specialist review should follow before the revised result is delivered.

  • Original PDF remains available
  • Every proposed change is visible
  • Unsupported instructions are called out
  • Specialist submission planned