ToolJovia
Accessibility

Reviewed HTML Accessibility Annotations

Inspect eligible static attributes and apply a hash-guarded, author-approved alt, form-name or language change list.

✓ Browser-local processing
Processed in this tab. Up to 100,000 characters unless this tool states a smaller limit.

Loading tool…

How to use Reviewed HTML Accessibility Annotations

Carry reviewed accessibility text into a separate HTML source copy while preserving all other source bytes. The inspect manifest identifies explicit source nodes and current values; apply mode refuses stale input, unsupported attributes and accidental overwrites before creating an inert text download.

  1. Paste a static source excerpt and run inspect to obtain its source hash, node IDs and existing values.
  2. Decide the appropriate text in context, then create edits with nodeId, attribute, expected (string or null), and value under the exact sourceSha256.
  3. Run apply-approved, review the separate text download, and test the resulting site with real users and assistive technology.

Good to know

  • 100,000 source characters, 20,000 nodes, 60 levels, 1,000 eligible explicit elements, 200 approved edits, 1,000 characters per new value and a 300,000-character output preflight. Duplicate attributes are refused.
  • Only HTML img alt, non-hidden input/select/textarea aria-label, and explicit html lang are editable. Templates, SVG/MathML, implied nodes, arbitrary attributes, scripts and styles are excluded. Language checking is a limited syntax profile, not a registered-language lookup.
  • User source remains inert text; existing scripts, URLs and unsafe markup are preserved as source bytes, so the output is not sanitized. The tool does not infer an image meaning, visible label, accessible name, live state or WCAG conformance.
  • Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.

Common questions

Can this replace a real visible label or accessibility review?

No. A visible associated label is usually preferable for form controls, and alternative text depends on context. This tool only applies the text you explicitly approve; it does not decide that the resulting experience is accessible.

Is this input sent to a server?

No. The application processes this input inside your browser tab and does not save it to persistent storage.

Keep going with related tools

All accessibility →