Accessibility

Last reviewed October 14, 2026

Facing Pages is a reading app, and reading should be open to everyone. We want this website to work well for people who use screen readers, keyboards, switch controls, magnification or voice control, and for people who are sensitive to motion or need strong contrast.

This statement covers the website at facingpagesapp.com. It’s written by DM Solutions and Development LLC, which makes Facing Pages.

Our standard

We build this website to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and we meet the stricter Level AAA wherever we can. WCAG 2.2 Level AA is the benchmark commonly used for website accessibility under laws such as the Americans with Disabilities Act (ADA).

In our most recent testing, described below, we found no failures of any WCAG 2.2 Level A or AA success criterion. We haven’t had an independent audit, so we describe the site as designed to conform rather than certified.

What we’ve done

Reading and contrast

• All text meets the Level AAA contrast ratio: at least 7:1, or 4.5:1 for large text. That includes text laid over photographs, which we measure against the actual photo pixels behind every line.
• Nothing depends on color alone. Links are underlined or clearly set apart, and a selected sentence is highlighted and underlined.
• If your device asks for more contrast, the site increases it. Windows High Contrast and other forced color modes are supported.
• Text can be zoomed to 400% and the page reflows to a single column, with no sideways scrolling, down to a width of 320 pixels.
• You can increase line, letter, word and paragraph spacing (as WCAG 1.4.12 describes) without text being cut off.

Keyboard and focus

• Everything on the site works with a keyboard alone, in a logical order. A “Skip to content” link is the first thing you reach.
• The item with keyboard focus always shows a thick ring in a color that contrasts with what’s behind it, and the site’s header never covers it.
• Buttons and links are at least 44 by 44 pixels, so they’re easy to tap. The sentences in the reader are the text itself, at its normal line height.

Screen readers

• Pages use headings, landmarks and labeled controls, so you can move around by heading or region.
• Spanish and French text is marked with its language, so screen readers pronounce it correctly.
• In the “Try it” reader, picking a sentence or a word is announced, and its translation and meaning appear as real text you can read.
• The drawn iPhone Duo and iPhone are pictures. Screen readers hear a short description of each instead of the text drawn on them.

Motion

• If your device is set to reduce motion, the opening-book animation, the scroll effects and the moving shelf of covers all stay still.
• You can also turn motion off on this site with the “Reduce motion” button at the bottom of the homepage. The setting is remembered on that device.
• The moving shelf of covers has its own pause button. Nothing flashes, and no sound plays unless you ask for it.

Known limitations

• Read aloud. The “Listen” button in the “Try it” reader uses your browser’s built-in voices. Which voices you get, and whether Spanish and French voices are available, depends on your device and browser.
• The drawn devices. The iPhone Duo and iPhone illustrations show story text very small, as a real phone would at that size. That text is part of the picture. The “Try it” reader shows the same kind of page as real text, at a readable size.
• Pages on other websites. Links to the App Store, Google Play and Unsplash lead to pages we don’t control.
• Assistive technology testing. We test with automated tools, a keyboard, and by reviewing what each page tells screen readers. We haven’t yet tested with people who rely on assistive technology every day, and we’d value hearing from you.

This statement is about the website. If anything in the Facing Pages app for iPhone, iPad or Android gets in your way, please tell us too.

How we test

• Automated checks with axe-core, using its WCAG 2.0, 2.1 and 2.2 rules at Levels A, AA and AAA, on every page at desktop, phone and 320 pixel widths.
• A pixel-by-pixel contrast check of every line of text against what is actually behind it, in light and dark mode.
• Keyboard-only testing of every link and control, including focus visibility and whether anything covers the focused item.
• A review of the accessibility tree, which is what screen readers read: every control’s name and role, the headings and the landmarks.
• Checks at 400% zoom and with increased text spacing.

These checks run every time the site is updated, and an update that fails them isn’t published.

Technologies

The site relies on HTML, CSS, WAI-ARIA and JavaScript, and is built for current browsers. Without JavaScript the text is still there, but the drawn devices stay empty and the “Try it” reader doesn’t respond.

Tell us about a barrier

If something on this site is hard to use, or you need any of it in a different format, please email hello@facingpagesapp.com. Tell us the page, what you were trying to do, and the device or assistive technology you use, if you’re comfortable sharing it. We read every message.