Accessibility Statement

Our Commitment to Accessibility

PaceBrain is committed to ensuring digital accessibility for people of all abilities. We believe that everyone should have equal access to information and functionality on our platform, regardless of any disabilities they may have.

We are continually improving the user experience for everyone and applying the relevant accessibility standards to ensure we provide equal access to all users.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

PaceBrain is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

What We Have Implemented

• Keyboard Navigation: All interactive elements can be accessed and operated using a keyboard alone.
• Focus Indicators: Clear, visible focus indicators are provided for all interactive elements.
• Skip Navigation: Skip links allow users to bypass repetitive navigation and jump directly to main content.
• Semantic HTML: We use proper heading hierarchy and semantic landmarks (header, nav, main, footer) for easy navigation.
• Alternative Text: Images and icons include alternative text descriptions for screen reader users.
• Color Contrast: Text and interactive elements maintain a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text.
• Reduced Motion: Animations respect the user's "prefers-reduced-motion" system setting.
• Form Labels: All form inputs have associated labels that are programmatically linked.
• Error Identification: Form errors are clearly identified and described to users.
• Resize Support: Content can be resized up to 200% without loss of functionality.

Known Limitations

Despite our best efforts to ensure accessibility, there may be some limitations. Below is a description of known limitations and potential solutions:

Charts and Data Visualizations

Our analytics charts use visual representations that may not be fully accessible to screen reader users. We are working on providing alternative text descriptions and data tables for all charts. In the meantime, data can be exported for analysis in alternative formats.

Map Components

Interactive maps displaying routes may present challenges for users relying on assistive technologies. We provide alternative route information in text format where available.

Third-Party Content

Some content provided by third-party integrations (such as Strava or Garmin widgets) may not meet our accessibility standards. We are working with our partners to improve the accessibility of integrated content.

Compatibility with Assistive Technologies

PaceBrain is designed to be compatible with the following assistive technologies:

• Screen readers (including NVDA, JAWS, and VoiceOver)
• Screen magnification software
• Speech recognition software
• Keyboard-only navigation

PaceBrain is designed to be compatible with the following browsers:

• Google Chrome (latest two versions)
• Mozilla Firefox (latest two versions)
• Apple Safari (latest two versions)
• Microsoft Edge (latest two versions)

Technical Specifications

Accessibility of PaceBrain relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• WAI-ARIA
• CSS
• JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Assessment Methods

PaceBrain assesses the accessibility of our platform through the following methods:

• Self-evaluation: Regular internal audits using automated testing tools such as axe, WAVE, and Lighthouse.
• Manual testing: Testing with keyboard-only navigation and screen readers.
• User feedback: Incorporating feedback from users with disabilities to identify and address issues.
• Custom audit tooling: We have developed internal accessibility audit utilities that validate WCAG 2.1 AA compliance including color contrast checks, ARIA validation, focus management, and keyboard navigation testing.

Built-in Accessibility Features

PaceBrain includes comprehensive accessibility features built directly into our component library:

Modal Dialogs

• Focus is automatically trapped within dialogs when open
• Escape key closes dialogs
• Focus returns to the triggering element on close
• Proper ARIA roles and labels (role="dialog", aria-modal, aria-labelledby)
• Background scroll is prevented when dialogs are open

Tab Interfaces

• Arrow key navigation between tabs
• Home and End keys to jump to first or last tab
• Proper ARIA tab pattern implementation
• Support for both automatic and manual activation modes

Dropdown Menus

• Arrow key navigation within menus
• Type-ahead character search to quickly find options
• Home and End keys support
• Escape key to close
• Proper ARIA menu pattern implementation

Screen Reader Announcements

• Dynamic content changes are announced via ARIA live regions
• Status messages use appropriate politeness levels
• Form validation errors are announced automatically
• Loading states are communicated to assistive technology

Color Contrast

• All text meets WCAG 2.1 AA contrast requirements (4.5:1 for normal text)
• Large text meets 3:1 contrast ratio minimum
• Interactive elements have sufficient contrast in all states
• Focus indicators are clearly visible

Feedback and Contact Information

We welcome your feedback on the accessibility of PaceBrain. Please let us know if you encounter accessibility barriers:

When contacting us about an accessibility issue, please include:

• A description of the accessibility problem you encountered
• The URL (web address) of the page where you encountered the issue
• Your browser and assistive technology, if applicable
• Any other details that might help us understand and reproduce the issue

Enforcement Procedure

If you are not satisfied with our response to your accessibility concern, you may escalate the issue. In many jurisdictions, there are governmental bodies responsible for enforcing accessibility requirements. Contact information for relevant authorities may vary by location.

Additional Resources

For more information about web accessibility, please visit:

• W3C Web Accessibility Initiative (WAI)
• Web Content Accessibility Guidelines (WCAG) 2.1
• The A11Y Project