KILLCRITICby X1OTHINK

Accessibility

Last reviewed October 5, 2026

Our commitment

KILLCRITIC is made by Repair Tune LLC, which does business as KILLCRITIC by X1OTHINK. We want everyone to be able to use our website and app. That includes people who use screen readers, screen magnifiers, voice control, switch devices or only a keyboard, and people who turn off animations or make text bigger.

The standard we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. WCAG is published by the World Wide Web Consortium (W3C) and is the most widely used technical standard for accessible websites.

Where we are today

We consider KILLCRITIC partially conformant with WCAG 2.2 Level AA. Most of it follows the standard, but some parts do not yet. The known gaps are listed below. We fix problems as we find them.

This statement covers killcriticseo.com: the public website, the sign-up, log-in and plan pages, the KILLCRITIC app, the blog code we give our customers to put on their websites, and the emails we send.

Known limitations

  • Parts of the logged-in app. We have recently fixed labels, spoken messages, focus and text contrast across the app, but we haven't yet checked every screen by hand with a screen reader, so some results may still not be read out. Workaround: email us and we will do the task with you, or for you.
  • Map position grid. This shows your Google Maps position at 25 spots as a 5-by-5 table. Screen readers read the position and the top three businesses at each spot, but a grid is slow to explore by ear. Workaround: the line above the grid gives the totals, and we can email you the results as a plain list.
  • Picture descriptions. Pictures made in Content Studio get a short description automatically, from what the business owner typed. It may be generic until the owner edits it. Pictures made before we added descriptions in October 2026 have a basic one ("Picture for" and the business name).
  • Content written with AI. Articles, Google posts and review replies are drafted by AI and checked by our customers before they publish them. We ask for clear headings and plain lists, and our code fixes heading levels, but a draft can still be organized in a confusing way. If you find one, tell us.
  • Printable review card. The QR code on the "Get reviews" card is a picture meant for printing. The same review link appears on the page as text, with a Copy button.
  • Our blog on other businesses' websites. The blog section we provide uses the fonts, colours and layout of the website it is placed on. How easy it is to read partly depends on that website's design.
  • Emails we sent before our October 2026 update may have light grey text that is hard to read. Newer emails do not.

How we test

  • In October 2026 we went through the code of our website, app, blog code and emails against WCAG 2.2 Level AA and fixed what we found.
  • Automated checks (axe-core, in a real browser) on our public pages, the sign-up and log-in pages, our blog code and the app's screens, at desktop size and at the narrow width of a small mobile screen. We run them before major releases.
  • Code checks, run before we deploy, catch known problems such as missing labels, missing picture descriptions, hidden focus outlines and low-contrast text.

We test ourselves. We have not had an outside audit. Hands-on testing with screen readers is still to come, and we will list the screen readers and devices here once we have tested with them.

Compatibility

KILLCRITIC is built to work with current versions of Chrome, Edge, Firefox and Safari, and with the screen readers and accessibility settings built into Windows, macOS, iOS and Android. It uses HTML, CSS, JavaScript and WAI-ARIA. The app, and the blog section we provide for our customers' websites, need JavaScript turned on.

Read-aloud button

Some long pages, like this one, have a Listen button that reads the page using your browser's built-in voice. It's there for people who like to listen. It never starts on its own, and it doesn't replace your screen reader or change how the page works with it. Our Privacy Policy explains which voice it uses.

We have chosen not to add an "accessibility overlay" or toolbar plugin. These tools can get in the way of the screen readers and settings people already use. Instead, we fix the pages themselves.

Tell us about a barrier

Email legal@killcriticseo.com with "Accessibility" in the subject line. It helps to include the page address, what you were trying to do and what happened, and if you know them, your device, browser and any assistive technology. You don't need to tell us about a disability.

We aim to reply within 2 business days. Where we can, we aim to fix the problem or give you a workaround within 10 business days. Some fixes take longer. If yours does, we'll tell you what we're doing and when to expect it.

Get help another way

If something on our site gets in your way, we will help you get the task done, at no extra cost. For example, we can:

  • set up your account and business profile with you by email;
  • change your plan, cancel, or handle a refund under our normal terms without you using the billing portal;
  • send your audit, reports or drafts to you as plain text in an email;
  • export your data or delete your account (see our Privacy Policy).

Services we don't control

Some steps happen on other companies' websites: Google sign-in and Google Business Profile, Stripe Checkout and the Stripe billing portal, and WordPress. The accessibility of those pages is up to those companies. If one of them stops you from finishing something in KILLCRITIC, tell us and we'll help you do it another way. For example, we can change your billing for you.

Our customers' websites belong to them. If you have trouble with a business's website, please contact that business. If the problem is in the blog section we provide, you can also tell us and we'll check whether our code is the cause.

About this statement

We review this statement at least once a year and whenever we make large changes. It was last reviewed on October 5, 2026, based on our own testing. To read our legal terms on accessibility, see Section 19 of our Terms of Service.