Accessibility support
Compounding Momentum should stay readable, keyboard-friendly, and recoverable if a page, download, or buying route is hard to use. Use this page to find the fastest alternative route or report a barrier with enough detail to fix it.
Fastest next route
Choose by what you need right now
If access friction shows up, pick the route that keeps momentum without forcing a checkout, private details, or a fixed file format.
Current baseline
Readable routes first
The site is static, keeps a skip link, visible focus states, descriptive route links, and mobile-sized actions. If a surface fails for you, the recovery path should be clear without requiring checkout or private account details.
- Keyboard
- Use the skip link, primary navigation, and route cards to move through each public page.
- Downloads
- Free reader resources are available as HTML routes and PDFs where practical.
- Support
- Report the exact page, device, assistive setup, and what blocked the next step.
Reading support
Choose the format that is easiest to use now
Start with the route that matches your setup. The HTML reader is the safest fallback for zoom, keyboard navigation, and browser-level accessibility tools.
Access decision
Pick the fastest fallback before reporting
Most access problems have a useful next route while the barrier is being fixed. Use this split to keep reading, switch formats, or check whether a buying path is site-owned or retailer-owned.
Accessible recovery routes
If one path is awkward, use the nearest alternative below. The free sample route is the best fallback when a purchase, policy, or download route is not ready.
Policy and support recovery map
When the access problem is not about reading the page itself, jump straight to the route that owns the next decision. Each link is a full tap target and keeps sensitive payment or account details out of email.
Barrier reports
Send details that make the issue fixable
Do not send passwords, payment card details, private account screenshots, or API keys. A focused report with the page and blocked action is enough for a local-safe site fix.
- Page and actionInclude the URL and the button, link, form, download, or text that was hard to use.
- SetupName the device, browser, zoom level, keyboard use, screen reader, or other assistive tool if relevant.
- Expected resultSay what you were trying to do next: read, download, buy, ask support, or review a policy.
What happens next
Site-level accessibility issues can be fixed in the static pages. Retailer checkout, Kindle delivery, and store account accessibility remain owned by the store that handles that order.