Doors just opened. It's still the warm-up in here. Grab your spot and check back as the floor fills up.

B2B Beta

Accessibility

Accessibility

We want every DJ to be able to use DJ back 2 back. This page says what we have checked on this site, what we know is wrong, and how to tell us about a problem.

What we checked

On 6 October 2026 we checked the pages of this site you can see without logging in. We used the engines behind Chrome and Safari, on a laptop-sized and a phone-sized screen, with automated tests and keyboard tests. On 7 October 2026, after the site's new look, we checked the headings, form labels, keyboard order and Menu again, in Chrome's engine. We have not yet tested with screen readers or with disabled users. We have not checked the apps.

On 18 October 2026 we checked the code of the pages behind log-in (your account page, Sessions and Mixes) for two things: where keyboard focus goes after you press a button, and whether buttons that say the same on every row are marked with that row's name. We haven't checked anything else on them, apart from text contrast (below).

What works today

Headings: every page has one main heading, and the headings under it go in order.

Images: the one photo, on the home page, is decoration and is marked so screen readers skip it.

Keyboard: you can reach every link, button and form field with the Tab key. "Skip to the content" comes first. On a phone-sized screen the Menu opens with Enter or Space, and Escape closes it. In Safari, links and buttons need Option+Tab, unless "Press Tab to highlight each item" is turned on in Safari's settings.

Focus: links, buttons, form fields and the Menu show an outline when you reach them with the keyboard: lime in dark mode, deep plum in light mode. Buttons, form fields, the Menu and "Skip to the content" also have a band of the page's own colour around the outline, in both modes, except in Safari on drop-down lists, checkboxes and radio buttons, which show the outline without the band. On all of these, the outline is at least 3 to 1 against what's behind it. On links in running text, a few of its pixels fall below that where it crosses text.

After a button: on your account page, Sessions, Friends and Mixes, when you press Block, Mute, Unmute, Unblock, Like, Delete, a friend request's Accept or Decline, a friend's Remove, or Add friend, keyboard focus comes back to that button. If the button has gone, focus moves to its section's heading, or to its list where the section has none, never to another button. Block and Remove ask first: focus goes to the question, so it's read before you Tab on to answer it or Cancel.

Buttons in a list: on those pages, a button that says the same on every row, like Unblock, Invite or Like, is marked for screen readers with its row's DJ name or set title, and each Log out under Logins with its device's name.

Text contrast: on 16 October 2026 we measured every page, logged out and logged in, on a laptop-sized (1280 pixels wide) and a phone-sized (390 pixels wide) screen, in light and dark mode, in Chrome's and Safari's engines, with the moving lights at five points and stopped. Everywhere we measured, the text meets WCAG 2.2 AA's contrast minimum (1.4.3): 4.5 to 1 for normal text and 3 to 1 for large text. The lowest values, all over the stage lights or the photo at the top of a page, were 4.88 to 1 for normal text and 3.23 to 1 for large text in light mode, and 5.00 and 3.14 to 1 in dark mode. Away from the lights and photo, normal text is at least 5.32 to 1 in light mode and 6.00 to 1 in dark mode. The outlined numbers and the ticker's words, measured by their outlines, are at least 3.45 to 1 in light mode and 16.37 to 1 in dark mode. We haven't measured hover states, the error box, the apps or our emails.

Reduced motion: if your device asks for reduced motion, the moving light effects stop. Pause motion, in the footer under Light mode on every page, stops them too, and your browser remembers it.

Like all DJ gear, the app flashes to show that something needs attention, or as a warning: the red border while you're live, and the headphone warning before a set. Every flash is once a second (half a second on, half off), a third of the 3-a-second limit in the accessibility guidelines (WCAG 2.3.1). The live border and the headphone warning keep flashing even with reduced motion on, because they're warnings; the other flashing lights stop.

Forms: every form field has a visible label.

Errors: if you leave a required field empty, your browser shows its own message and puts you in that field. Other errors appear under the form, in a status area that screen readers read out. An error we didn't expect opens a box that says what happened, with an error code. Escape or Cancel closes it.

Known problems

An error message isn't linked to the field it's about, and fields aren't marked as wrong for screen readers.

Not checked yet: the rest of the pages behind log-in (we've checked text contrast, focus after a button and the names on row buttons), the Mac and Windows apps, and screen readers.

The standard we're working towards

WCAG 2.2, level AA. We don't claim to meet it yet.

Tell us about a barrier

Email support@djback2back.com. Tell us the page, what you were trying to do, and what you use (your browser, and any screen reader or other tool).

Last updated: