Keystone Registry
MenuBook a demo

Legal

Accessibility statement (draft)

Our accessibility target for the website, the console, and the docs, what we test, the gaps we know of, and how to reach us.

Draft for Leadership review. This document is a working draft prepared . It has not been reviewed or approved by Leadership, is not in effect, and will change before it is published as final. Bracketed items are placeholders.

  1. Our target

    We design and build keystoneprotocol.io, the Keystone Registry console, and the documentation to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. [Leadership: confirm this commitment.]

    Status: partially meeting the target. The parts that fall short are listed below, with what we are doing about each.

  2. How we check

    Every website page is tested automatically with axe against the WCAG 2.0, 2.1, and 2.2 A and AA rules, in light and dark modes, on each change, and checked at 390 pixels wide with no sideways scrolling and with reduced motion; the home page's skip link is tested. The main console screens are tested with axe in light and dark modes, and an asset's overview and the console's error, not-found, sign-in, and organization pages also at 320 and 390 pixels wide with reduced motion; the other console screens are not tested at small widths yet.

    Controls are native links, buttons, and form fields with visible labels and status is never shown by color alone. Most controls are at least 44 by 44 pixels; compact buttons (sign out, table paging) are 32 pixels. The website ships no JavaScript. Keyboard use has been reviewed in the code, and the skip link and its focus are tested with the keyboard; full keyboard walk-throughs of each form are not automated yet. Automated checks find only some kinds of problem.

    This is our own evaluation, not an independent audit. An Accessibility Conformance Report (ACR) for the console, on the VPAT 2.5 template, is drafted. [Leadership: decide whether to publish the ACR or provide it on request.]

  3. Known gaps

    Console sessions end after 30 minutes without activity, for security, and no warning appears before that happens yet. A form left open that long has to be filled in again.

    When an action needs a recent sign-in, you sign in again and then repeat the action, re-entering what you had typed.

    Some error messages are not yet announced to screen readers as they appear.

    Wide data tables scroll sideways inside their own area on small screens rather than reflowing.

    Sign-in uses WorkOS AuthKit, a hosted service. We have not yet checked its pages against WCAG 2.2 success criterion 3.3.8 (accessible authentication); we will record the result here.

    The documentation site is hosted by Mintlify and has not been evaluated yet.

  4. Tell us about a problem

    If something on keystoneprotocol.io, in the console, or in the documentation is hard to use with your browser, assistive technology, or settings, write to accessibility@keystoneprotocol.io. Say which page and what happened. We will reply within [5 business days] and can provide the information in another format. [Leadership: confirm the mailbox and response time.]