# Accessibility HTML + AIO - RipAI

- Route: `/accessibility-html`
- URL: https://rippdf.com/accessibility-html
- Source file: `src/pages/v2/AccessibilityHtmlV2.jsx`

## Page Summary
Publish Accessibility HTML companions for large PDF estates - reconstructed headings, reading order, tables, visible document context, and review signals.

## Key Headings
- H1: Publish Accessibility HTML companions for large PDF estates
- H2: Keep the official PDF Publish a web access layer
- H3: Accessibility depends on fragile tag quality
- H3: Accessibility starts from web-native semantics
- H3: Critical context stays hidden
- H3: Document meaning becomes visible
- H3: Every workflow needs a separate cleanup path
- H3: One structured companion supports multiple outcomes
- H2: Specialized Accessibility HTML, not a print-to-web dump
- H3: Accessibility HTML bundle
- H3: Structure a screen reader can navigate
- H3: Meaning exposed as page content
- H3: Signals for faster remediation
- H3: Provenance and handoff evidence
- H2: From PDF estate to reviewed HTML companion
- H3: Stage the estate
- H3: Reconstruct meaning
- H3: Package the companion

## Canonical References
- https://rippdf.com/ai/product.md
- https://rippdf.com/ai/use-cases.md