Accessibility

Accessibility statement

Apparently is committed to making the regulatory licensing platform usable for everyone, regardless of ability, assistive technology, or environment.

Conformance level

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We test against this standard during development and verify with both automated and manual checks.

  • Semantic landmarks (header, nav, main, footer) on every page.
  • Skip-to-content links for keyboard users.
  • Visible focus indicators on all interactive elements.
  • Form fields associated with labels and inline error messages announced via ARIA live regions.
  • Status changes (uploads, extractions, save events) announced to screen readers.
  • Color contrast meeting or exceeding 4.5:1 for normal text and 3:1 for large text.
  • Reduced-motion preference honored — decorative animations stop when prefers-reduced-motion: reduce is set.
  • Responsive layouts that reflow at 320px wide without horizontal scrolling.

Tested with

  • NVDA (Windows), JAWS (Windows), VoiceOver (macOS & iOS), TalkBack (Android).
  • Keyboard-only navigation on Chrome, Safari, Firefox, and Edge.
  • 200% browser zoom and 320px minimum viewport width.
  • axe DevTools and Lighthouse automated audits on every release.

Known limitations

We are transparent about areas where our conformance is in progress:

  • PDF deliverables — Some generated PDFs (legal opinions, engagement letters) are tagged for accessibility, but a small number of legacy templates are still being remediated. Email accessibility@apparently.com for an accessible alternative.
  • Embedded jurisdictional maps — Interactive map visualizations have keyboard-accessible equivalents via the list view, but the map itself is decorative for screen-reader users.
  • Some data tables — Wide CRM/ops tables use horizontal scroll wrappers; we are progressively migrating to responsive card layouts for full mobile-screen-reader support.
  • Third-party content — Some embeds (e.g. live regulator updates) are sourced from external systems that may not meet our standards. We surface accessible summaries where possible.

Contact us about accessibility

If you find a barrier on Apparently, please tell us. We treat accessibility reports as priority bugs and aim to respond within two business days.

  • Email: accessibility@apparently.com
  • Subject line should describe the page and the assistive technology you were using.
  • We'll acknowledge receipt and follow up with a fix timeline or workaround.

Last updated: May 11, 2026.

This statement is reviewed quarterly and after every major release.