Use the arrow keys to navigate between menu items.

What you can expect from my accessibility subscription

How we'll likely work together when you subscribe and a weekly breakdown of results and KPIs.

A monthly subscription allows us to work together based on the level of support your team needs. I believe this is the most effective way to quickly make progress. By eliminating the friction of changing priorities, debating scope and exchanging proposals, contracts and statements of work, I can help you consistently ship an accessible product.

What's in it for you

You get friction-less access to me, without worrying about the clock, proposals or invoices through a monthly subscription that you can pause or cancel at any time, without long-term contracts or penalty clauses.

I'll be responsible for:

  • eliminating critical accessibility issues in production,
  • reducing the number of critical accessibility issues in key user flows,
  • decreasing the time it takes your team to resolve known accessibility issues,
  • reducing the time an accessibility issue sits in your backlog,
  • reducing the number of new accessibility issues a product release introduces,
  • reducing the number of development hours your team spends on fixing known accessibility issues at the expense of building new features.

With my help, your team will ship accessible products without blocking ongoing work.

How we'll do it

I'm going to unpack a process for shipping an accessible website without blocking ongoing work. Of course, I'll work together with your team to apply it to your product. And it'll take trial and error before we get it right. Here's how we'll likely work together to help you ship an accessible product without blocking ongoing work.

Week 1

I'll spend the first week getting to know you, how your team works and what the current state of accessibility in your team and product is. We'll do a workshop and put together the pages and components that are part of your key user flows.

By the end of the first week, you should have:

  • a list of key user flows we can come back to again and again,
  • an accessibility statement on your website, and
  • a proper process implemented on how we'll deal with accessibility issues together.

We will continually update the accessibility statement.

Weeks 2 - 4

Over the next few weeks, we'll work on eliminating the critical accessibility issues already in production. I'll start work behind the scenes on an accessibility audit using both automated and manual testing processes on a few different devices, operating systems, browsers and assistive technologies.

By the end of the first month, you should have:

  • an accessibility audit started,
  • a reviewed backlog and a prioritised list of accessibility issues to work on,
  • recognised and identified any gaps in your team's knowledge and accessibility practice.

Weeks 5 - 8

During the next month, we'll focus on establishing healthy communication habits while working together to fix critical accessibility issues in your key user flows.

By the end of the second month, you should have:

  • reduced the number of critical accessibility issues in production,
  • an accessibility audit completed,
  • a downloadable Accessibility Conformance Report (ACR) on your website,
  • a design and code review process to reduce the number of new accessibility issues, and
  • a realistic roadmap with milestones for clearing your backlog of accessibility issues.

Going forward

After the initial two months, you should already be in a much better position. Your team should be following best practices. As a result, far fewer accessibility issues should end up in production. Going forward, you'll want a way to review accessibility issues in QA and in customer-reported feedback.

I can't predict what these issues will be, but here are some things we're likely to work on together:

  • run prototyping/research/discovery workshops for accessibility
  • help build your roadmap to include accessibility
  • create an accessibility strategy and roadmap, set goals and monitor progress
  • help recruit and onboard my eventual full-time replacement
  • write accessibility policies and guidelines, accessibility statements and inclusive language guides, informed by internal research
  • suggest an accessible colour palette and a type scale that will scale across your system components
  • review design work, troubleshoot accessibility problems and suggest improvements
  • annotate designs for accessibility: semantic structure, content, tab order, ARIA tags, colour use, state design and screen reader notes
  • embedding accessibility acceptance criteria into the development process
  • setting up a consistent process to triage and prioritise accessibility issues that result from customer feedback
  • setting up guard rails, such as automated accessibility tests, to avoiding introducing new accessibility issues into releases
  • keeping the ACR up to date
  • lead the planning and execution for bringing digital assets up to current and future standards as they emerge
  • coordinate with 3rd parties and product teams to assist with remediation
  • identify gaps in business and technology workflows and implement process improvements
  • getting out of the break/fix cycle that drives up costs

The fine print

I'm not a fan of surprises, so I want to make sure we're on the same page. Here are some things you should know before you apply.

  • You can pause or cancel your subscription at any time, for any reason, no questions asked.
  • We'll communicate mostly asynchronously, via our private Slack channel or email. I'll always reply to any message within 24 hours.
  • If we need to talk face to face, we can schedule a mutually convenient time.
  • I have a hard limit of five clients at a time. This way I can guarantee a timely response and a turnaround time for all your requests.
  • The ideal team is made up of no less than 3 and no more than 7 people, including 1-2 designers and 2-4 developers. If you don't yet have these roles on your team, you won't benefit fully from what I offer.
  • I don't work with or advertise a specific web framework or technology.
  • I won't create high-fidelity designs or write production-ready code. Your team has the technical chops and the domain knowledge that likely outmatches my technical abilities in their framework of choice. Plus, doing the work beats having someone else do it for them.
  • I don't just write code, I help design the overall solution and make sure it's implemented in the correct way.
  • My role is to support your team and answer the inevitable questions and challenges that arise from working day to day.
  • Payment is due 100% at the beginning of each month.
  • If you're unhappy with how work is progressing in the first 7 days, you can ask for your money back. I'll refund your payment in full, no hard feelings.
  • Before we start work together, you'll need to agree to my complete terms of service.

Ready to work with me?

If everything I've described above sounds like what you've been looking for, that's great! Get started with an intro call by selecting an appropriate level of support and filling in the form.

Get started

Still have questions?

Each heading expands to show more information, one block at a time.

Is a subscription better than other engagements?

Yes. Here's how it compares to other engagements.

Now is the time

Have I answered all your questions? Great! Then apply now to start the process!

Get started

Not ready to work with me yet?

If you love all this, but still need some time to decide, that's ok! I want you to be 100% confident we're a good fit. Until you feel that way, here are some risk-free ways to see what I bring to the table.

6 Days to an Accessible Website

Enroll in a free 6-day email course that teaches you how get the upper-hand on 1 million websites by fixing the most common accessibility issues on yours.

Enroll now
Effective Accessibility Checklists

Download free PDF checklists for agile teams to nudge you towards a more accessible outcome by weaving accessibility into your SDLC.

Download now