An honest accessibility statement for Counsel.day.
We target WCAG 2.1 Level AA on every public page and every signed-in surface. This page lists what conforms today, the gaps we know about (with three of them named below in plain language), our process for fixing reported barriers, and how to reach a person if you have hit one. We treat accessibility reports as bug reports of the first order; you will not be sent to a queue.
WCAG 2.1 Level AA, on every surface.
Our target is WCAG 2.1 Level AA for every page on counsel.day and every surface inside the signed-in product. We have not yet commissioned a third-party audit; this statement is the result of our own assessment, reviewed by the founder. We will commission an external audit before the end of 2026, and we will publish its findings here.
Beyond the WCAG checklist, we hold ourselves to three plainer commitments. First: every interactive control reachable by keyboard alone. Second: every text element legible at 200% browser zoom on a 1280-pixel-wide viewport without horizontal scroll. Third: every action that has a visual confirmation also has a screen-reader-accessible confirmation. The third commitment is where most of our current gaps sit.
What is meeting the standard right now.
The marketing site, this page included, conforms to WCAG 2.1 Level AA across every audited criterion: contrast ratios meet 4.5:1 for body and 3:1 for large text; every link is keyboard-reachable; every heading uses correct semantic level; the skip-to-main-content link is present and visible on focus; the colour palette does not rely on colour alone to convey meaning; all form fields have programmatically associated labels.
The signed-in application conforms to the same standard on every static surface: the dashboard, the vote screens, the verdict view, the account and billing screens. Keyboard navigation through the evening-vote flow is tested on every release; focus order matches reading order; the focus indicator is visible against every background. Multi-factor authentication challenges work with assistive technology in our testing.
What does not yet conform.
The gaps below are real. We list them so you know what to expect, and so you can hold us to fixing them. Each gap names what is wrong, what the impact is, and when we plan to ship the fix.
- Gap 01 · Dynamic toast notifications Dynamic toast notifications on the in-product surface are not yet announced to screen readers. The visual toast appears, but the underlying region lacks an aria-live attribute. Affected actions include the "vote cast" confirmation and the "invite sent" confirmation. Planned fix in the next iteration; tracked as accessibility ticket A11Y-001.
- Gap 02 · Verdict chart The conviction-trajectory chart on the verdict page is not yet keyboard-navigable. A keyboard-only user can read the verdict text and the synthesis, but cannot interact with the chart to inspect a specific day. The chart's data is also available below the chart as a labelled list, but the chart itself is currently mouse-only. Planned fix as part of the verdict-view rebuild; tracked as A11Y-002.
- Gap 03 · Reduced-motion compliance One transition on the verdict-reveal moment ignores the prefers-reduced-motion media query. Users who have set their operating system to reduce motion will still see a single 400-millisecond fade on the verdict reveal. The rest of the application honours the preference. Planned fix in the next release; tracked as A11Y-003.
How to report a barrier.
If you have hit a barrier we have not listed above, write to a11y@counsel.day. Tell us what you were trying to do, what happened, the assistive technology you were using (if any), and the page or surface where the problem occurred. A screen-recording or screen-reader log is welcome but not required.
We acknowledge accessibility reports within one business day and treat them as priority bugs. We will tell you in plain language whether we can fix the issue, when we plan to ship the fix, and how to follow up.
How we fix what is reported.
Every report enters our public ticket sequence (A11Y-NNN). Critical issues, those that block a user from completing a core flow with assistive technology, are fixed within fourteen days. Major issues are fixed within thirty days. Minor issues are fixed within ninety days. We publish every fix in the changelog under an "accessibility" tag, with the ticket number, so reporters can confirm their issue has shipped.
If you reported the issue, we will write back to you when the fix ships. If we cannot fix it in the windows above, we will tell you why and what the workaround is in the meantime.