Accessibility Statement

At FlexiRoam, we are committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We strive to align with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA and continually improve our digital properties.

Commitment

FlexiRoam's accessibility policy is based on the Web Content Accessibility Guidelines (WCAG) 2.2 – Level AA and EN 301 549 v3.2.1 and adheres to global best practices for web accessibility as mandated by the European Accessibility Act (EAA). Our goal is to provide a seamless and inclusive digital experience across all devices and platforms, ensuring everyone can access our services with ease.

 

Compliance Status

The current accessibility status of www.flexiroam.com is partially compliant with EN 301 549 / WCAG 2.2 Level AA. This means some parts of the content may not fully conform to the accessibility standard, but we are actively addressing these issues in accordance with EAA requirements.

1. Scope and Application

This accessibility statement applies to:
▪️Primary website: https://www.flexiroam.com
▪️Core user journeys: Plan selection, checkout, account management
▪️Mobile responsive versions
▪️Customer support interfaces

This statement covers content and functionality under FlexiRoam's direct control and does not extend to third-party integrations or external payment processors unless specifically noted.

2. Compliance Status
▪️Standard: EN 301 549 v3.2.1 (Web Content Accessibility Guidelines 2.2 Level AA)
▪️Conformance Level: Partially Compliant

Accessibility Audit Results

A comprehensive accessibility audit was conducted combining automated tools with mandatory manual testing as required by EN 301 549
▪️Accessibility Score: 81/100 (Google Lighthouse v11)
▪️Date of Audit: 13 June 2025
▪️Pages Tested: Homepage, Plans, Checkout, Dashboard Login, Contact Us

FlexiRoam website partially conforms with EN 301 549 / WCAG 2.2 Level AA standards. Some content areas require remediation as detailed in the "Non-Accessible Content" section below.

3. Testing Methodology & Tools

Manual Testing Conducted (EN 301 549 Requirement):
✅ Screen Reader Testing
▪️NVDA (Windows screen reader) - Version 2024.1
▪️JAWS (Windows) - Version 2024
▪️VoiceOver (macOS/iOS) - Latest version
▪️TalkBack (Android) - Latest version
✅ Keyboard Navigation Testing
▪️Tab order verification across all interactive elements
▪️Focus indicators visibility and management
▪️Keyboard shortcuts functionality
▪️Bypass mechanisms (skip links)
✅ Assistive Technology Testing
▪️Voice recognition software (Dragon NaturallySpeaking)
▪️Magnification software (ZoomText)
▪️Switch navigation devices
▪️Eye-tracking systems
✅ Real User Testing
▪️Testing with 5 users with disabilities
▪️Vision impairments (2 users)
▪️Motor disabilities (2 users)
▪️Cognitive disabilities (1 user)

Tools & Methodology

Our audit included the use of:

• Google Lighthouse v11 - Automated accessibility scanning
• axe DevTools (Chrome) - Comprehensive accessibility testing
• NVDA (Windows screen reader) - Manual screen reader testing
• VoiceOver (macOS/iOS) - Mobile and desktop screen reader testing

Browser Compatibility Testing:

Tests were run in:

• Chrome (Windows/macOS) - Primary testing environment
• Safari (macOS/iOS) - Mobile and desktop compatibility
• Mozilla Firefox (Windows/macOS)
• Microsoft Edge (Windows)

Pages Tested:

• Homepage (/)
• Plan selection (/plans)
• Checkout flow (/checkout)
• Account dashboard (/dashboard)
• Support center (/support)
• Accessibility statement (/accessibility)

4. Technical Specifications

The accessibility of FlexiRoam website relies on the following technologies:

• HTML5
• CSS3
• JavaScript ES6+
• WAI-ARIA 1.2
• Progressive Web App (PWA) technology
• RESTful API services

5. Summary of Findings

Strengths Identified

• Sufficient color contrast for most text/background combinations
• Meaningful link and button names in most sections
• ARIA roles and landmarks used appropriately on primary layouts
• Headings are in logical order and support screen reader navigation
• Keyboard navigation works effectively in core areas (e.g., navigation, buttons)
• Semantic HTML Structure: Proper heading hierarchy (H1-H6)
• Responsive Design: Functional across all device sizes
• Skip Links: Bypass navigation mechanisms implemented

6. Areas for Improvement & Non-Accessible Content

6.1 Non-Compliance Issues Identified (Being Addressed)

• Names & Labels
• • Issue: Some elements (e.g., SVG icons, buttons) are missing accessible names, making them invisible to assistive technologies
  • WCAG Criterion: 4.1.2 (Name, Role, Value)
  • Impact: Screen reader users cannot identify icon functions
  • Timeline: Fix by Q4 2025
• Color Contrast
• • Issue: While mostly compliant, a few interactive elements (e.g., light gray on white) fall short of minimum contrast ratio
  • WCAG Criterion: 1.4.3 (Contrast Minimum)
  • Impact: Users with low vision may have difficulty reading text
• ARIA Attributes
• • Issue: Certain aria-* attributes are not correctly applied (e.g., aria-expanded missing on accordions)
  • WCAG Criterion: 4.1.2 (Name, Role, Value)
  • Impact: Screen reader users may not understand component states
• Form Elements
• • Issue: Inputs lack associated elements or placeholder text in a few forms, impacting usability for screen reader users
  • WCAG Criterion: 3.3.2 (Labels or Instructions), 1.3.1 (Info and Relationships)
  • Impact: Users with disabilities may struggle with form completion
• Language Attribute
• • Issue: The HTML root element is missing a valid lang attribute, which is critical for screen readers
  • WCAG Criterion: 3.1.1 (Language of Page)
  • Impact: Screen readers may not pronounce content correctly
• Image Alt Text
• • Issue: Some decorative icons and images either lack alt text or have inappropriate descriptions
  • WCAG Criterion: 1.1.1 (Non-text Content)
  • Impact: Screen reader users may miss important information or be confused by inappropriate descriptions

6.2 Disproportionate Burden

• Legacy PDF Documents
• • Issue: Historical promotional materials (pre-2023) lack accessibility features
  • WCAG Criterion: Multiple criteria affected
  • Justification: Retrofitting legacy PDFs would require disproportionate resources
  • Mitigation: New PDFs follow accessibility guidelines; alternative formats available on request
• Third-Party Integrations
• • Issue: Some payment processing interfaces controlled by external providers
  • WCAG Criterion: Various
  • Justification: Limited control over third-party accessibility implementation
  • Mitigation: Working with vendors to improve accessibility; alternative payment methods available

7. Ongoing Accessibility Improvements

We take these findings seriously and are taking action. Our current and planned improvements include:

• Immediate Actions (Q4 2025):
• • Adding descriptive aria-labels and accessible names to all interactive icons
  • Ensuring color contrast meets WCAG thresholds throughout the site
  • Correcting form labels and providing clear validation messages
  • Applying the correct lang="en" declaration in HTML
  • Enhancing mobile accessibility by increasing tap target sizes
  • Removing incorrect alt text from decorative images
• Phase 1: Critical Issues (October 2025)
• • Fix SVG icon accessibility and ARIA attributes
  • Implement proper language declarations
  • Resolve form validation and labeling issues
• Phase 2: Important Issues (December 2025)
• • Address remaining color contrast issues
  • Improve image alternative text consistency
  • Enhance keyboard navigation patterns
• Phase 3: Enhancement (Q4 2025)
• • Implement advanced ARIA patterns
  • Add audio descriptions for video content
  • Improve mobile accessibility beyond minimum requirements

8. Feedback and Support

We welcome your feedback on the accessibility of www.flexiroam.com. If you encounter accessibility barriers, please let us know:

• Primary Contact:
• • Email: support@flexiroam.com
  • Subject Line: "Website Accessibility Issue"
  • Response Time: 3-5 business days

When reporting accessibility issues, please include:

• URL of the affected page
• Description of the issue
• Assistive technology being used
• Browser and operating system information

Last Updated

This statement was last reviewed and updated on 27 July 2025.