Skip to content
SELARA

Accessibility

Designed to be used by everyone.

Last updated on June 23, 2026.

Accessibility is something we build into our work from the start. It shapes how we design pages, write markup, and review what we ship, because we want everyone to be able to use what we build. That includes people who rely on screen readers, keyboard navigation, magnification, or other assistive technology. This statement covers the standards we hold ourselves to, how we check our work against them, where we know we still fall short, and how to let us know when something gets in your way.

Our commitment and conformance target

We build to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA and the Section 508 standards as our target. They are the bar we design against and test against. We treat them as the goal we engineer toward, not a finished certification. This statement is not a formal conformance claim, a per-criterion audit, or a published Accessibility Conformance Report (ACR/VPAT). It is an honest account of how we work toward those standards.

How we test

We build accessibility checks into our engineering process, so problems get caught before they ship instead of after. Every change has to clear our automated test suite first.

  • A zero-exclusion axe sweep across every public page. We run the full accessibility ruleset with no rules switched off. When a check flags something, we fix the page or the underlying component rather than scope the check away.
  • Keyboard and screen-reader operability checks (our Playwright page sweeps) that verify the skip link moves focus to the main content, the navigation menu opens and closes with the keyboard alone, and focus is managed correctly as you move between pages.
  • Component-level accessibility checks on our design-system building blocks, so each one is exercised in isolation as well as on the assembled page.

These checks run continuously in our build, so a regression that breaks accessibility stops the change from shipping.

Known limitations

There are still gaps, and we would rather name them than gloss over them. As of the date above, here is what we have not done yet.

  • We have not yet commissioned an independent, third-party accessibility audit of the site.
  • We have not published a formal Accessibility Conformance Report (ACR/VPAT) or a per-criterion conformance statement.
  • Automated testing catches a lot, but it is not a substitute for a full manual review. Some WCAG criteria come down to human judgment, and we have not yet walked through every one of them end to end.

We expect to narrow this list over time, and we will update this statement as we do.

Tell us about a barrier

If something we have built is hard to use or read with assistive technology, we want to hear about it. A report from you is often how we find out about a problem. Email us at hello@selara.us or reach us through our contact page. Please tell us the page and what went wrong, and we will respond and work to remediate the issue.

Ready to illuminate
the mission ahead?

Tell us about the program. We’ll respond with a clear path forward.

Start the conversation