archimedes
write

EverythingAccessible Public Systems

Accessible documents

PDFs and public packets that a screen reader can actually use, batched after inventory.

  • Section 508
  • WCAG 2.1 AA
  • Tagged PDFs
  • Named batches
  • Scoped after inventory

A public packet that cannot be read is not a public packet. Batches are sized after we see the library, not guessed from a page count on a call.

Named document consulting, not a page-count SKU. I inventory the set, map what a screen reader cannot use, improve that batch, and hand over before-and-after evidence plus a short maintain guide.

I tag, structure, and evidence the named set, and leave you a way to keep the next batch from rotting the same way.

Same method as the rest of the practice: diagnose the operating system, map the risk or workflow, improve the procedure or digital tool, produce evidence and a usable handoff.

What you get

  • A named document batch
  • Before and after evidence
  • A short maintain guide
  • A straight answer on what will not fit

How accessible public systems runsSee the method

  1. 01Understand the operating system
  2. 02Map the risk or workflow
  3. 03Improve the procedure or digital tool
  4. 04Produce evidence and a usable handoff
  • Section 508
  • ADA Title II
  • WCAG 2.1 AA
  • Named scope only
  • No overlay product

Ask about thisStraight answer, no deck.

More on accessible public systems