Listed

Accessibility statement

Listed aims to meet WCAG 2.2 level AA. This statement says how we test, where we fall short, and how to tell us about a barrier.

Version 2026-10-17Updated Oct 17, 2026

Draft. This document is awaiting review by counsel and may change. If it does, the new version will be dated and we will say what changed.

Contents, 5 sections
  1. Our target
  2. How the site is built for it
  3. What we test
  4. Known limitations
  5. Tell us about a barrier

Listed is a service operated by Valor Security.

Effective Oct 17, 2026. Version 2026-10-17.

Our target

Listed aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on every page, in both the light and the dark theme, on desktop and on a phone.

How the site is built for it

  • Every figure is text, not an image, set in a table with row and column headers where it sits in a table.
  • Charts are drawn as SVG on the server. The numbers they show are always in a table or a row beside them, so a chart adds shape and never carries data on its own.
  • Colour never carries meaning alone. An increase has ▲ and a decrease ▼ with the signed change, a reported purchase says "Purchase" and a sale says "Sale", and a voided league metric says "Void".
  • Every interactive element can be reached and used with a keyboard, and shows a visible focus outline. The command field opens with /, and a figure's source note is one key (n) away, with Esc back.
  • Text can be resized to 200% and the layout reflows to a 320-pixel-wide screen without horizontal scrolling, apart from inside wide data tables.
  • Motion is limited to short colour changes, and is switched off when your system asks for reduced motion.
  • Content pages are rendered on the server and can be read with JavaScript off. Each is also available as plain Markdown at the same path with .md added.

What we test

  • Keyboard: every page type and every form is walked with a keyboard alone before release.
  • Contrast: every colour pairing in the design system is checked against WCAG 2.2 AA in both themes, and re-checked when one is added.
  • Screen readers: the main flows (reading a company page, signing up and in, entering a forecast, approving an agent) are tested with VoiceOver on macOS and iOS and with NVDA on Windows.
  • Automated checks: page types are checked with automated accessibility tools on each release. These catch some problems, not all.

Known limitations

  • Filing text. Sections we extract from 10-K and 10-Q filings keep the structure of the company's own document. Some companies build tables and headings in ways that are hard to navigate with a screen reader. The original filing on sec.gov is outside our control.
  • Member uploads. PDFs and images that members attach to their notes may not have text alternatives.
  • Share cards. Share images contain text drawn into an image. The page each card links to carries the same information as text.
  • Stripe pages. Checkout and the billing portal are run by Stripe, on Stripe's pages.
  • Passkeys. Adding and using a passkey relies on your browser and operating system, whose dialogs we do not control.

We are working on these, and will update this statement as they change.

Tell us about a barrier

If something on Listed is hard or impossible for you to use, tell us through the contact form or at legal@listed.markets. Say which page, what you were trying to do, and what assistive technology you use, if any. We reply within 5 working days. If you need information from a page in another format, ask, and we will provide it.

Other documents