Skip to content
Even Entry home

Engage: every fix ready for your developer to publish

Have a developer or agency? This plan's for you. Your customers who use a keyboard or screen reader, or zoom in, meet fewer barriers all the way to checkout.

$795  a month.

No onboarding fee.

A free 30-minute video call. You'll leave with your price.

Make the cart table headings dark enough to read

assets/component-cart-items.css
.cart-items th {   text-align: left;   padding-bottom: 1.8rem;   opacity: 0.85;   font-weight: normal; }
  1. Our software drafts the fix, a person checks it
  2. Your developer previews it
  3. Your developer publishes it
  4. Live, and our next check confirms it

Less work for your developer

Our software checks your store and drafts each fix. A person looks over every fix and every test result before it reaches you.

  • Fixes in your theme's code, with a note on what changed and why.
  • Shoppers have nothing extra to load: no widget, app or script.
  • Once a fix is in, every later check makes sure it stays fixed.
  • A monthly report in plain words: what we fixed and what's next.
Our team is asked: Does the store look right with “Make the cart table headings dark enough to read” on its private copy? Someone looks first. One blue button keeps the fix. Then it waits for your yes.
Our review screen. This is where our team checks every fix before it reaches you. You never have to use it.

What you have by the end of month one

Month one starts the day you sign.

  • Canvas High's product page on a laptop: the shoe's large picture, then sizes 6 to 10 with 6 chosen and 9 and 10 struck through.

    Your baseline

    We check every page once, so every later check can show what's changed.

  • Even Entry Lab wants everyone to be able to use this store, including people with disabilities, and works to make it so.

    The standard we use

    The Web Content Accessibility Guidelines (WCAG) 2.2, at level AA.

    What we are doing

    A page of every kind was last checked on 2026-10-16.

    Your statement

    A page telling shoppers what you're doing about accessibility, and what's next. We keep it up to date.

  • Before

    The top of the cart page on a phone, October 10, 2026, before the fix. We've outlined the small headings Product and Total, which are pale.

    After

    After the fix, the headings "Product" and "Total" are darker, the same gray as the price and size under the shoe's name. There's no outline in this one.

    Your first fixes

    At least five. If the pages customers buy from have fewer problems, we fix them all.

If month one ends before we deliver your baseline, your statement and your first fixes, ready to publish, month two is free.

Also in month one

  • First, we test every page of your store by keyboard.
  • We list the apps you've installed, and what each one breaks.
  • For shoppers who can't see pictures, we draft descriptions. A person checks a sample.

You say yes, your developer publishes

Your live store changes only when you say so.

You

  1. Set up a theme password and a collaborator account for us in Shopify.
  2. Delete either one any time, and that access ends.
  3. Read the monthly report.
  4. Approve each picture description.
  5. Read the statement first, tell us how shoppers can reach you, and approve it.
  6. Approve each fix.
  7. App causing a problem? Send its maker our message.

Your developer

  1. Preview each fix on the unpublished copy.
  2. Publish it.
  3. Put your statement and the picture descriptions you've approved on your store.

Us

Everything else, from the daily checks to your statement and your dated record.

No developer? We recommend Resolve: we publish the fixes for you.

A fix goes live, then gets checked. Our test store's live theme. Below it, our unpublished copy of the theme, with the fix and a Preview button. Then it goes live, and the old theme greys out. At a phone's width, our check outlines the cart's pale headings. Our next check shows them darker, and the outline turns green. It ends with the fix live and the problem gone.
Our keyboard test, paused on our test store's home page. After 85 presses of Tab, you're on the button of a small "Don't miss out" popup at the bottom of the page. Nothing on the page shows where you are, and our test marks it in red.
You've tabbed to a button, but you can't see it. A keyboard shopper wouldn't know where they are.

Checks and tests

  • Every day, we check the pages your customers buy from.
  • Every week, and whenever a new theme or app shows up, we take a wider look at some pages of every kind.
  • We compare each check with the last: what's new, and what came back.
  • We check your store's own emails too: order, shipping, account and marketing.
  • At least every 30 days, we check every page in full, at three screen sizes.
  • We test every page by keyboard when you join, then every month, and again after each new theme.
  • We check against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

Fixes

  • We put each fix on an unpublished copy first, with a preview link.
  • A problem on many pages? You hear about it once, with pictures of where it happens.
  • We draft a description for new product pictures too.

Keeping you posted

  • New or returning problem? We tell you within 24 hours, once a person has looked at it.
  • Your status page shows where your store stands. We bring it up to date after every check.
  • We keep a dated record of every check and fix. It's yours, just ask.
  • Demand letter? Your evidence pack, your record put together for your lawyer, is ready within 10 business days.
  • Email us any time. A person replies within 1 business day, with a full answer within 3 business days.

What Engage costs

$795 a month.

The disabled access credit, on IRS Form 8826, is for small US businesses. A year of Engage could lower your income tax by up to $4,645. Your tax preparer decides whether your business can claim it, and whether website work counts. Each January, we send them what you paid and what it bought.

Read our guide to the Form 8826 tax credit

You hear your price before you sign anything. See what moves your price, and the terms

What Engage doesn't do

  • Publishing fixes: Your developer does it. On Resolve, we do, and you can move up in any month.
  • Messages to app makers: You send the one we write. On Resolve, we take it to them and follow it up.
  • Screen reader tests: Engage doesn't test with screen readers. Resolve tests every page with two each month, and Defend with three.

No service can promise a store won't be sued, and we don't.

We don't give legal advice.

See what's not in any plan

See what Engage would do for your store

Before the call, we look over your store's public pages. On the call, we show you what we found, with pictures. Then we walk through your first month, and your price.