We test everything against WCAG 2.2 at the AA standard.

GitHub has everything. Plus, it's reasonably easy to get information out of it. Need a way to move GitHub issues to a different platform like JIRA? We can help you do that. Want to create a report with a bunch of issues? GitHub makes it easy to get that information. We don't like vendor lock-in.

Rather than create a proprietary tool, we've opted to build on something your teams are already familiar using.

The annual cost of a specialized, dedicated accessibility expert easily exceeds $100,000, which doesn't account for benefits and other costs. Many companies and organizations simply can't justify that expense.

With a subscription:

• You know exactly what you're paying each month
• Have all the perks of a full-time employee without any of the overhead.
• There are no messy contracts to negotiate or billable hours to question
• You have a team of accessibility experts supporting you

On average, issues get a response in about 48 hours. Sometimes it's faster. Sometimes it's slower.

We're happy to tackle whatever you need, and you can submit anything you'd like in an issue. Obviously more complex questions and requests take longer. We might ask some questions, but that's one of the perks of GitHub comments.

Every issue follows the same template. You'll add information like:

• The question you're asking or a description of what you need done
• Environment access and credentials
• Any other relevant details

We strive to make this as asynchronous as possible, but sometimes there are questions or problems. We'll do our best to raise questions or blockers so we can keep crushing your backlog.

There are companies who specialize in accessibility testing services. We've worked for a few of them. What we've found is that large, bloated testing reports aren't useful for anyone.

We're not a "testing company". We're a group of accessibility subject matter experts who know that designers, developers, and product teams need a resource they can rely on. If that means validating a design, working through a developed component, or detailing functional requirements, we're happy to do it. And we'll do it in a way that makes reading, interpreting, and applying it easy.

We do not offer refunds at this time.

Absolutely. Enterprises, too!

We're a team of designers, developers, program managers, and digital strategists happy to help however we can, or get you connected with someone that can.

Schedule a call with us to let us know about your project.

This is one of the rare occasions where we'll want to setup a meeting.

Many times you don't need a VPAT, but if you do, we'll talk through what it entails, what we need, and how we'll approach it.

Book a call with us to start the conversation.

Yes! You can submit designs -- like images or Figma files -- for us to review.

This is particularly useful for organizations that are shifting left in an attempt to mitigate defects being found in development and production.

Design reviews generally take two forms:

Feedback:

Comments left on early-stage designs to help inform and create accessible experience, patterns, and flows.

Annotations:

Guidance intended to be used by development teams. This usually focuses on component markup, accessible names, roles, and behaviors across assistive technologies.