Accessibility statement · updated July 2026

Accessibility

FactNot is working toward an inclusive product that people can use with different devices, input methods, and assistive technologies.

01

Our commitment and standard

We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as a design and testing target. FactNot is still in beta and does not currently claim full WCAG conformance or accessibility certification.

  • Core actions should remain available by keyboard, not only by pointer or hover.
  • Controls should expose meaningful names, roles, states, and focus indicators.
  • Layouts should support text resizing, reduced motion preferences, and readable contrast.
02

What we test today

Our automated LiveView tests check selected labels, roles, dialog states, and keyboard interaction contracts. We also use browser checks for selected focus and responsive behaviors, but we have not yet completed an independent accessibility audit or a full page review with assistive-technology users.

  • Selected dialogs, menus, search controls, and navigation states have semantic regression tests.
  • Selected flows receive keyboard, focus-return, responsive, and reduced-motion browser checks.
  • Passing these checks does not establish that an entire page or the full product conforms to WCAG.
03

Known limitations

Accessibility work is ongoing. Some complex workspace and mobile interactions need broader keyboard, screen-reader, text-zoom, and low-vision testing.

  • Generic mobile panels may not yet provide complete focus trapping and focus restoration.
  • Not every route has received an end-to-end keyboard or screen-reader pass.
  • Dense toolbars and advanced editing controls may be difficult to use at narrow widths or high zoom.
04

Report a barrier or request help

If an accessibility barrier prevents you from using FactNot, use the contact link on this page. We welcome requests for an alternative way to access information or complete a task.

  • Include the page or route, what you were trying to do, and what blocked you.
  • If you are comfortable doing so, include your browser, device, and assistive technology.
  • Do not include passwords, access tokens, or other sensitive account information.