Accessibility

Accessibility Statement

We are committed to making this website accessible to everyone, regardless of ability or assistive technology. This page documents our conformance posture, the measures we have taken, known limitations, and how to report barriers.

Conformance target: WCAG 2.2 Level AA

This site is tested against all applicable WCAG 2.2 Level A and Level AA success criteria. Statement last reviewed: .

What this statement covers

This accessibility statement covers the Mobile Application Testers website at https://www.mobileapplicationtesters.com. It does not cover external services linked from this site, third-party platforms (e.g. LinkedIn, GitHub), or the content within any embedded third-party iframes that are outside our editorial control.

Mobile Application Testers provides mobile app testing and quality assurance services, including specialised accessibility audit services for client applications. We hold ourselves to the same standard we recommend to our clients: WCAG 2.2 Level AA as the baseline, with Level AAA criteria applied where feasible.

This statement uses the format recommended by the W3C Web Accessibility Initiative (WAI) and the EU Web Accessibility Directive Model Accessibility Statement.

Specific conformance measures

Perceivable

  • All non-text content has text alternatives: images carry descriptive alt attributes; decorative images use aria-hidden="true"
  • All informational icons are accompanied by visible text labels, never icon-only
  • Colour is never the sole means of conveying information, status indicators combine colour, icon, and text
  • All foreground/background colour combinations meet WCAG 4.5:1 contrast ratio for normal text and 3:1 for large text (18pt+ or 14pt+ bold)
  • The accent red (#dc2626) is used over dark backgrounds where the contrast ratio meets or exceeds 4.5:1; it is not used as body text on white
  • Text can be resized to 200% without loss of content or function
  • Content does not require horizontal scrolling at 320px viewport width (1280px at 400% zoom)
  • Text spacing can be overridden to 1.5× line height, 2× letter spacing, and 0.16em word spacing without content loss (WCAG 1.4.12)
  • No content flashes more than three times per second

Operable

  • A skip navigation link is the first interactive element on every page, visible on keyboard focus, linked to #main-content
  • All interactive elements are keyboard accessible via Tab, Shift+Tab, Enter, Space, and arrow keys as appropriate
  • No keyboard traps exist on any page, keyboard focus can always move freely
  • The mobile navigation drawer uses role="dialog" with programmatic focus containment (focus trap) and Escape key dismissal
  • All pages have descriptive, unique <title> elements in the format 'Page Name, Mobile Application Testers'
  • Focus is never hidden behind the sticky header, scroll-padding-top: 80px is applied globally (WCAG 2.4.11)
  • Focus indicators are visible on all interactive elements: 3px solid box-shadow ring at 0.5rem border-radius with minimum 3:1 contrast against adjacent colours (WCAG 2.4.11)
  • No tabindex greater than 0 is used anywhere; DOM order matches visual reading order
  • The pricing table annual/monthly toggle announces its state via aria-pressed
  • The testimonial carousel includes a visible pause button meeting WCAG 2.2.2 (Pause, Stop, Hide)
  • All accordions use the Radix UI Accordion primitive with correct ARIA button roles and aria-expanded attributes
  • Links whose text is not self-explanatory have aria-label providing full context
  • The mega-menu uses Radix NavigationMenu with correct ARIA navigation role, arrow key navigation, and Escape dismissal

Understandable

  • <html lang="en"> is declared on every page
  • Every page has exactly one <h1> provided by the HeroSimple or Hero layout component
  • Heading hierarchy (h1 → h2 → h3) is maintained without skipping levels on all pages
  • Form labels are always explicit <label> elements associated via htmlFor, no placeholder-only labels
  • Form error messages are programmatically associated to their fields via aria-describedby
  • Form errors use role="alert" or aria-live="assertive" for immediate announcement to screen readers
  • Form success messages use aria-live="polite" to announce without interrupting ongoing screen reader activity
  • All form fields requiring specific format (phone, date) include format hints in the label or description
  • The site does not produce unexpected context changes on focus or input without user initiation

Robust

  • All HTML is well-formed and validates without critical errors
  • Landmark roles are explicit on all layout elements: role="banner" (header), role="main" (main), role="contentinfo" (footer), role="navigation" with aria-label on all nav elements
  • Interactive components use native semantic HTML where possible; custom widgets use ARIA roles, states, and properties per the ARIA Authoring Practices Guide
  • All custom components are tested with VoiceOver (macOS/iOS), NVDA (Windows), and TalkBack (Android)
  • All pages pass axe-core automated audit with zero violations
  • Animations and transitions are wrapped in a prefers-reduced-motion check, all motion is disabled when the user has requested reduced motion
  • Third-party scripts are loaded asynchronously and do not block main-thread rendering or assistive technology parsing

Testing methodology

Accessibility is tested at multiple layers: automated scanning at build time, manual screen reader verification on each page template, and keyboard-only navigation walks on every new interactive component. The following tools form our accessibility testing stack:

axe-core

Automated WCAG violation detection, run on every page at build time

Lighthouse

Accessibility audit scoring, target 100 on every route

VoiceOver

Screen reader testing on macOS and iOS Safari

NVDA

Screen reader testing on Windows Chrome and Firefox

TalkBack

Screen reader testing on Android Chrome

Keyboard-only

Full navigation verification, Tab, Shift+Tab, Enter, Space, arrow keys, Escape

WCAG Contrast Checker

Contrast ratio verification for all colour pairs in the design system

Deque WorldSpace

Manual WCAG 2.2 checklist review on all page templates

Known limitations

Despite our best efforts, some areas of this website may have accessibility limitations. The following known issues are being actively addressed or have documented workarounds:

Third-party form embed

The CompanyHub contact form is loaded from an external domain. We have verified it is keyboard operable and screen-reader compatible, but cannot fully control its internal accessibility implementation. Users who encounter barriers can use the phone number 857-567-2674 as an alternative.

Third-party map embed

Google Maps iframes on the Fort Worth page have accessibility limitations outside our control. A text address alternative is always provided alongside any map embed.

MDX content pages

Older glossary and blog entries may have heading hierarchy inconsistencies. These are remediated on a rolling basis as pages are reviewed. Priority remediation is given to high-traffic pages first.

Report an accessibility barrier

If you experience an accessibility barrier on this website, a broken keyboard flow, a missing alt text, a colour contrast failure, or any other issue, please tell us. We commit to:

  • →Acknowledging your report within 2 business days
  • →Providing a workaround or fix timeline within 5 business days
  • →Prioritising critical barriers (those preventing task completion) for immediate remediation
857-567-2674Contact form →

Formal complaints and escalation

If you are not satisfied with our response to an accessibility report, you may escalate through the following channels:

  • US Department of Justice, ADA complaints: ada.gov/filing-a-complaint
  • Section 508 (federal contractors): If you are accessing this site as part of a federally-funded procurement process, Section 508 complaint procedures apply via the relevant agency's Section 508 Coordinator.
  • UK Equality Act / WCAG for public sector: If accessing from the UK, the Equality and Human Rights Commission (EHRC) handles complaints under the Equality Act 2010.

Related policies and standards