Accessibility at Back

Last updated October 1, 2026

This statement covers Backburner (a task list), Backpack (files, documents and spreadsheets), Backdrop (a video editor) and back.dev (this site). It describes their accessibility, known limitations and how to request help or report a barrier.

This statement reflects our own testing and the limitations we have identified.

Accessibility standard

We work toward WCAG 2.2 level AA, the international guidelines for making web content accessible to people with disabilities. We do not fully meet this standard. Known limitations are listed below.

Back publishes this statement voluntarily. The UK regulations requiring an accessibility statement apply to public bodies, which Back is not, and the European Accessibility Act exempts very small businesses. We remain responsible for reasonable adjustments under the Equality Act 2010.

Current accessibility features

• Buttons, links and fields are reachable with a keyboard, with a visible outline around the focused element. We know of no hidden focus or keyboard traps. The timeline limitation is described below.
• Light and dark themes are supported and follow your system preference unless you choose one.
• Reduced motion preferences are respected. Fades, slides and animated reveals are disabled when your system requests reduced motion.
• No unsolicited interruptions. The products do not use pop-ups, interstitials, adverts or autoplay. There is no cookie banner because we do not use advertising or analytics cookies.
• Backdrop provides keyboard shortcuts for playback, stepping by frame or second, moving between cuts, splitting, trimming to the playhead, deleting, zooming and undoing. Press ? in Backdrop for the full list.
• Plain language. We use familiar words and explain technical terms where they are needed.

Known limitations

Our testing has identified the following issues.

• Moving clips in Backdrop's timeline requires a mouse. Most editing actions have keyboard shortcuts, but moving a clip to a different place on the timeline requires dragging. There is no keyboard or screen-reader alternative. Contact us if this prevents you from editing; we will help you make the edit.
• Backpack's documents and spreadsheets have not had accessibility work. They may present barriers. The file list and other parts of Backpack are more developed, but dialog boxes, including the confirmation for permanent file deletion, are not announced properly to screen readers.
• Screen-reader support is uneven. We have tested some screens but not all. Testing has been internal and has not included people who use a screen reader every day.
• Some outlines and secondary text do not meet contrast requirements. We are addressing these product by product, starting with text-field boundaries.
• The products have not had an independent accessibility audit. This statement is based on internal testing. There are likely to be issues we have not identified.

How we test

We test manually with the keyboard, at increased browser zoom, in both themes, and with the macOS screen reader on selected screens. Backpack also has targeted automated accessibility and dialog keyboard tests. These checks do not establish full conformance with WCAG, and no independent audit has been completed.

Request help or report a barrier

Write to legal@back.dev with a brief description of what you were trying to do and what prevented it. Technical terminology is not required. We will respond.

We aim to reply within five working days. If a prompt fix is possible, we will give you a timeframe. Otherwise, we will explain the limitation and find another way to help you complete the task, including doing it for you.

When this changes

We will update this page and its date when we resolve a listed issue or identify a new one.