Accessibility

Last reviewed: May 2026

The short version

–We aim for WCAG 2.1 Level AA conformance across the site.

–Every interactive element supports keyboard navigation and screen readers.

–If something doesn’t work for you, email us and we’ll fix it.

Our commitment

RollsRewards is committed to making credit-card information accessible to everyone, including people who use assistive technologies like screen readers, voice navigation, switch devices, or keyboard-only input. We design and build the site with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our target conformance standard.

What that means in practice

–Every interactive element (buttons, links, sliders, inputs) is reachable via keyboard alone, with a visible focus indicator.

–Form fields and tools have associated labels announced by screen readers.

–Color is never the only way information is conveyed — labels, icons, and text accompany every color cue.

–Slider values, calculator outputs, and numeric figures are announced as plain words to assistive tech (e.g., “six hundred fifty dollars per month”, not “dollar sign 6 5 0”).

–Decorative typography (Roman numerals, em-dashes, ornamental flourishes) is hidden from screen readers so they announce only the meaningful content.

–Animations respect the prefers-reduced-motion setting at the operating-system level.

Known limitations

Accessibility is a continuous effort, not a finished state. We test new features against keyboard navigation and screen-reader announcement before shipping, but we're a small team and may miss things. Known areas we're actively improving:

Third-party content (card images sourced from issuers) may have inconsistent alt text.
The statement-analyzer tool relies on AI categorization that doesn't yet announce per-row categorization confidence to screen readers.

Report an accessibility issue

If you encounter content that's difficult or impossible to use with assistive technology, email hello@rollsrewards.com with the subject “Accessibility issue” and as much detail as you can share (the page URL, the browser and assistive technology you're using, and what you were trying to do). We aim to acknowledge within 3 business days and resolve within 30 days, depending on complexity.

Standards and methods

Our development practice includes semantic HTML, ARIA where appropriate (and only where appropriate), automated linting against accessibility rules, and manual keyboard + screen-reader spot-checks before each release. We don't claim third-party certification, but we welcome reports from any audit you run against the site.