Accessibility statement

Our target standard

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, and we use that standard as the yardstick for the US Americans with Disabilities Act (ADA) and the EU/EN 301 549 expectations. Accessibility is treated as an ongoing commitment, not a one-time checkbox.

What the site supports

The site is built to be operated by keyboard alone: a "Skip to content" link is the first thing you reach, every interactive control shows a visible focus ring, and the navigation exposes its state to assistive tech (current page, expanded/collapsed menus). Pages use proper landmarks (header, navigation, main, footer) and a single, ordered heading structure.

Content is written to work with screen readers: images carry descriptive alternative text (or are marked decorative), forms have associated labels, and status messages are announced politely. The site works in both light and dark themes, respects your operating-system color-scheme preference, and honors "reduce motion" so animations are turned off when you ask for less movement.

How we test

Every change is checked in continuous integration against an automated accessibility budget (a Lighthouse accessibility score gate), alongside end-to-end tests that exercise keyboard navigation, skip links, and ARIA state. Automated testing cannot catch everything, so we also rely on manual review and your feedback.

Known limitations

We are actively tracking a few items: some accent-colored text and buttons sit close to the minimum contrast ratio and are being tuned to comfortably clear WCAG AA, and the mobile navigation menu closes on Escape but does not yet trap focus while open. Documentation pages rendered from Markdown are held to the same standard but receive less frequent manual review. If you hit a barrier not listed here, please tell us.

Report a problem

If any part of this site is difficult to use with assistive technology, we want to fix it. Email [email protected] or open an issue on https://github.com/dj-pearson/MCPFold describing the page, what you were trying to do, and the assistive technology or browser you were using. We aim to acknowledge accessibility reports within a few business days.