Skip to main content
PayslipIQUSA
EnglishEspanol (Beta)

Last reviewed: 2026

Accessibility Statement

PayslipIQ targets WCAG 2.1 Level AA. We design and test for users who rely on keyboard navigation, screen readers, voice control, and high-contrast modes.

Standards we target

  • Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard most US courts treat as the de-facto benchmark under Title III of the Americans with Disabilities Act (ADA).
  • Section 508 of the Rehabilitation Act, where applicable to federal procurement.
  • Keyboard-only navigation across every page.
  • Screen reader compatibility (tested with VoiceOver on macOS/iOS and NVDA on Windows).

What we have built in

  • Skip-to-main-content link on every page.
  • Semantic HTML (proper <header>, <nav>, <main>, <article>, <footer> landmarks).
  • Color contrast ratio of at least 4.5:1 for body text and 3:1 for large text.
  • Visible keyboard focus indicators.
  • Form fields with explicit labels and ARIA error messaging.
  • Responsive layout that reflows at 200% zoom without horizontal scrolling.
  • No automatically playing audio or video.
  • Alt text on all informative images. Decorative images marked aria-hidden.
  • Captions on any embedded video content.

Known limitations

We disclose what is not yet fully WCAG 2.1 AA compliant:

  • Some PDF source documents we link to (IRS publications, state DOR forms) are hosted on third-party government sites and may not meet AA themselves. We cannot remediate third-party content.
  • Complex interactive calculators have been tested with screen readers but may have edge cases. Report any issue and we will prioritize a fix.

Reporting an accessibility issue

If you encounter a barrier on PayslipIQ, please tell us. We aim to acknowledge accessibility reports within 2 business days and provide a fix or workaround within 10 business days for issues that block use.

Email: see the Contact page.

Please include: the URL, the device and assistive technology you were using, what you were trying to do, and what failed. Screenshots or screen recordings help.

Continuous testing

We run automated accessibility checks (axe-core) on every deploy. We do periodic manual reviews with screen readers and keyboard-only navigation. We treat accessibility regressions as production-blocking.

Feedback drives improvement

This statement is updated when we ship significant accessibility changes. The current version reflects the state of the site as of 2026.