Skip to main content
Kill The Body

and the head will die

Accessibility

Tested November 11, 2026

We want every fan to be able to use Kill The Body, including people who use a screen reader, a keyboard, voice control or zoom. The site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Today it partially conforms: some parts don’t meet the standard yet, and they’re listed below.

Report a problem


If something on the site doesn’t work for you, email contact@killthebody.com with the page address and what went wrong. We’ll reply within 5 business days with what we’ll do and when.

What we tested


On November 11, 2026 we checked these pages:

  • the home page, a fighter page, an event page and a news article
  • the rankings, the fighter list, search, and the privacy policy

How we checked them:

  • An automated scan with Pa11y 10 and axe, using the WCAG 2.2 AA rules plus the touch-target size rule.
  • A keyboard pass: the skip link, visible focus, tab order, menus, and whether focus gets stuck anywhere.
  • A colour-contrast check of every text and background colour in the site’s themes.

We haven’t yet tested with a screen reader such as VoiceOver or NVDA, or at 200% and 400% zoom. An automated scan finds only part of the problems people actually hit.

Known problems


These are the problems we found on November 11, 2026. We’re working through them.

  • Rankings tables. Screen readers can’t move through the rankings tables row by row, because the tables are missing parts of their structure.
  • Event pages. Event pages have no main heading, so screen-reader users can’t jump to the event title.
  • Fight history on fighter pages. The links to each opponent have no name for screen readers, so they’re announced only as “link”.
  • Rank numbers. The large rank numbers are slightly too faint against the background for some low-vision readers.
  • Small tap targets. Some links in the rankings grid and the dots under the home page carousel are smaller than 24 by 24 pixels, so they’re hard to hit on a touch screen.
  • Fighter records and flags. Screen readers read some records as raw numbers and some country flags as emoji instead of the label we wrote.
  • Theme menu. The theme picker is announced as a menu, but the arrow keys don’t move through it. Tab still works.

What already works


  • A “Skip to main content” link is the first thing you reach with Tab.
  • Every link and button shows a visible outline when it has keyboard focus.
  • A high-contrast theme is available in the theme picker at the bottom of every page.
  • The fighter-page timeline animation and the header stay still if your device is set to reduce motion.

We don’t use an accessibility overlay widget. We fix problems in the site itself.

About this statement


We wrote this statement on November 11, 2026 from our own testing. We’ll update it when we fix the problems above or test again. See also our Privacy Policy and Terms of Use.