Accessibility
Usable by everyone, checked every day.
Standard
WCAG 2.1 AA, with 2.2 where it goes further
This site (airtablebackup.com) and the console (app.airtablebackup.com) are built to conform to the Web Content Accessibility Guidelines 2.1 at level AA, the standard web accessibility is judged against under the Americans with Disabilities Act and similar laws. Where WCAG 2.2 adds a requirement at level AA, such as a minimum size for anything you click or tap, it is met as well.
In practice that means: every page works from the keyboard alone with a visible focus ring, every control and image has a name a screen reader can speak, text and controls keep at least the required contrast in both the light and the dark theme, pages reflow to a 320-pixel-wide screen without sideways scrolling, nothing flashes, and motion is removed when your system asks for less of it.
Testing
Before every release, and every morning
Before anything ships. Every page of the site and every page of the console, including the dialogs, is opened in a browser in both themes and checked against the WCAG 2.0, 2.1 and 2.2 A and AA rules of axe-core, an open-source accessibility engine, plus a stricter check of our own that every clickable target is at least 24 by 24 pixels. One failure stops the release, the same way one failing test does.
Every morning. The same rules run against the live site each day alongside the security scans, and the result is read by a person.
By hand. What automated rules cannot judge was checked by a person from the keyboard: that every dialog takes focus, keeps it, closes on Escape and returns focus where it came from; that the skip link, the current-page marker and the headings make sense in order; and that the two charts in the console have a text alternative that says the same thing.
Last reviewed 2026-10-27. The date moves when the testing or the standard changes, not on every release.
Limits
What is outside our hands
- Airtable’s sign-in and consent pages. You sign in to the console with Airtable, and a restore asks Airtable for permission in Airtable’s own window. Those pages are Airtable’s.
- Checkout. Payment is taken by Paddle, our merchant of record, in Paddle’s checkout. That page is Paddle’s.
- Your own data. The console shows the contents of your base as they are. Text, images and attachments in your records are yours, and the console cannot add what they lack, such as a description for an image.
No known accessibility problems are open on this site or in the console as of the review date above. If you find one, it is a bug, and it is handled as one.
Feedback
Tell a person
If any part of this site or the console is hard to use with the assistive technology or settings you rely on, email support@airtablebackup.com with “Accessibility” in the subject. Say which page, what you were trying to do, and what you use (for example a screen reader and its browser). A person replies within one business day, and you will hear what was done about it. If the problem keeps you from using your backup, say so and it goes to the front of the queue. More on how to reach us is on the support page.
Technical
How the pages are built
Both the site and the console are standard HTML, CSS and JavaScript with WAI-ARIA where HTML alone has no word for something, and work in the current versions of Chrome, Safari, Firefox and Edge on desktop and on phones. The site is readable with JavaScript off. The console needs JavaScript, as any application that changes what it shows as you work does.