Accessibility statement

Last reviewed November 9, 2026.

We want everyone to be able to use spillwaycms.com, its documentation and its registry, whatever device, browser or assistive technology they use. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

What we do

• Pages are built from semantic HTML: real headings, lists, tables with captions and header cells, labeled form fields and buttons, and landmarks for the header, navigation, main content and footer.
• Text and interactive elements meet the WCAG AA contrast ratio of 4.5:1, and the colors are checked whenever the brand changes.
• Everything works with a keyboard, with a visible focus outline. Wide tables and code samples that scroll sideways can be reached with the keyboard.
• Images have alternative text. Our publishing checks flag an image without it, and headings that skip a level, before a page goes live.
• Pages reflow on small screens without sideways scrolling, and text can be zoomed to 200%.
• We test every page type with automated checks (axe-core against WCAG 2.2 AA, and design checks for contrast, text size and layout) at desktop and phone sizes, and by hand with a keyboard.

Known limitations

• Content from other sites, such as embedded videos, depends on that site's accessibility.
• Registry package pages show READMEs written by each package's publisher, which may not meet every guideline.
• The admin, used by editors and registry publishers, follows the same standard, but we are still testing it with screen readers.

Tell us about a barrier

If something on this site is hard or impossible for you to use, please tell us at hello@spillwaycms.com. Say which page and what happened, and what you use to browse if you are comfortable sharing it. We reply within 5 business days and, if we cannot fix the problem quickly, we will get you the information another way.

Spillway is open source, so you can also report accessibility issues in the software itself on GitHub.