← Home
Published 26 July 2026

Accessibility Statement

This page sets out the accessibility standard Verbata targets for verbata.com, what the current coming-soon page actually does to meet it, and how to tell us if something doesn't work for you.

The short version. Verbata targets WCAG 2.2 Level AA across verbata.com. The current page uses semantic HTML, labelled form fields, live-region status messages, visible keyboard focus, and respects reduced-motion settings. One known gap is listed below. If you hit a barrier, email hello@verbata.com.

Conformance target

Verbata's accessibility target for verbata.com is Level AA of the Web Content Accessibility Guidelines (WCAG) 2.2, published by the W3C. This is a forward-looking commitment describing the standard every page on this site is built against, rather than a claim that a formal third-party audit has already certified full conformance. Verbata has not published an independent accessibility audit or conformance report for this site.

How the current page is built

This is a small, pre-launch site, so the honest way to describe accessibility here is to describe what the shipped markup actually does. On the current coming-soon page at verbata.com:

  • The page is built with semantic HTML5 — one <main> landmark, one <h1>, and a lang attribute on the <html> element so assistive technology applies the correct language rules.
  • The Verbata wordmark and its decorative line art are inline SVG marked aria-hidden; the logo container carries role="img" with a single aria-label="Verbata", so screen readers announce one clear name instead of raw path data.
  • The early-access email field has a real, programmatically associated <label> (visually hidden, not a placeholder standing in for one), and is linked to its status message via aria-describedby.
  • Form feedback uses ARIA live regions: validation errors are announced via aria-live="assertive", and the success confirmation via aria-live="polite" with role="status", so the outcome is announced without the visitor needing to find it visually.
  • The email field and submit button have a visible :focus-visible outline, distinct from the page background, for people navigating by keyboard.
  • The stylesheet includes a prefers-reduced-motion: reduce rule that turns off the logo-draw animation, the reveal transitions, and the pulsing launch-date indicator for visitors whose system requests reduced motion.
  • The viewport meta tag does not disable pinch-zoom, so visitors who need to magnify the page can.
  • A <noscript> message explains what to do if JavaScript is unavailable, rather than leaving the page blank.

Colour contrast check

The site's secondary text uses #625f59 against the #f1efe9 page background. The contrast ratio calculated from those stylesheet colours is 5.53 to 1, above WCAG 2.2 AA's 4.5 to 1 minimum for normal text. This calculation covers that colour pairing only; it is not a full accessibility audit or a claim of site-wide conformance. Verbata has not published an independent accessibility audit or conformance report for this site.

Report an accessibility barrier

If anything on verbata.com is hard to use with a screen reader, keyboard-only navigation, voice control, or magnification, or if something in this statement doesn't match what you actually experience, please tell us: hello@verbata.com. Include the page URL and, if you can, the browser or assistive technology you were using — it helps track the problem down. Verbata aims to acknowledge accessibility reports promptly and will work through genuine barriers as they're confirmed.

About this statement

Standard WCAG 2.2, Level AA (target)
Scope verbata.com — the public coming-soon site
Statement published 26 July 2026
Format This is a living statement — it will be revised as the site changes.