RepForge
Legal

Accessibility Statement

Version 2026-09-01 · Effective [PUBLICATION DATE] · Next review [DATE + 6 MONTHS]

Draft — not in force. This document is still being prepared and has not been reviewed. It does not govern anything. The version and date above are provisional.

We want RepForge to be usable by everyone who trains, including people who use VoiceOver, larger text, or other assistive technology. This statement sets out what we are aiming for, where we currently fall short, and what we are doing about it. We would rather tell you the truth about where we are than claim a standard we have not yet met.

1 · Our commitment

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, as applied to native mobile applications, and we follow Apple's Human Interface Guidelines for accessibility on iOS.

2 · Current conformance status

RepForge is currently partially conformant with WCAG 2.2 Level AA. "Partially conformant" means some parts of the app do not yet fully meet the standard. The known gaps are listed in Section 4.

This assessment is a self-evaluation carried out by reviewing the app's source code and its use of iOS accessibility APIs. It has not yet been verified by an independent third-party audit. We have commissioned one — see Section 5.

3 · What already works

  • Reduce Motion is respected in the animated parts of the app, so transitions and celebratory animations are suppressed when you have that setting on.
  • Dark and light appearance are both fully supported, along with a choice of accent colours, and the app follows your system setting by default.
  • VoiceOver labelling is in place on a number of screens, including several of the more complex ones, where custom controls have been given explicit labels and decorative elements have been hidden from the screen reader.
  • Standard iOS controls are used throughout much of the app, and those inherit Apple's built-in accessibility behaviour.
  • No time limits. Nothing in RepForge expires or forces you to complete an action within a fixed time, apart from rest timers you start yourself, which can be skipped or extended.

4 · Known limitations

We know about the following, and we are working on them. This list is not a disclaimer — it is a work list.

Text size. RepForge does not yet adapt fully to the largest Dynamic Type settings. At the accessibility text sizes some screens will clip, truncate, or overlap. This is the most significant gap and it is first in the queue.

Custom controls and VoiceOver. Roughly three-quarters of our reusable interface components do not yet expose labels, values, or roles to VoiceOver. In practice this means several progress meters, day-grid squares, effort swatches, progress rings, statistic tiles, and some settings rows are either announced without meaning or skipped entirely.

Information conveyed by colour alone. Several views use colour as the only way of communicating a value or a status — including recovery and readiness trends, muscle-group coverage bars, the day grid, and effort ratings. There is currently no support for the Differentiate Without Colour setting, and no secondary shape or text cue in these places.

Charts and progress graphs. The charts on the Progress, Prep and Plan screens do not currently provide an accessible text alternative or audio graph, so their content is not available to VoiceOver users.

Hints and values. Very few controls provide accessibility hints or spoken values, so it is not always clear what a control will do or what state it is in.

Contrast. Some muted secondary text and some accent-on-surface combinations may fall below the 4.5:1 contrast ratio required at Level AA, particularly in light appearance. This has not yet been measured systematically.

Not yet tested. We have not yet completed structured testing with Switch Control, Voice Control, or Braille displays, and we have not yet tested the Apple Watch app or the home-screen widget for accessibility.

5 · What we are doing about it

  • A full internal pass with Xcode's Accessibility Inspector, VoiceOver, the largest Dynamic Type sizes, Increase Contrast, and greyscale — target [DATE].
  • Dynamic Type support across the design system, so every screen holds its layout at accessibility text sizes — target [DATE].
  • Accessibility labels, values, roles and hints on every custom control — target [DATE].
  • A non-colour cue everywhere meaning is currently carried by colour alone, and support for Differentiate Without Colour — target [DATE].
  • A systematic contrast audit against WCAG 2.2 AA — target [DATE].
  • An independent third-party accessibility audit, after which we will publish an updated statement and a conformance report — target [DATE].

We will update this statement as each item lands, rather than waiting until everything is done.

6 · Tell us where we have got it wrong

If you hit a barrier in RepForge, please tell us. Reports from people actually using assistive technology are more useful to us than any audit.

Email [ACCESSIBILITY EMAIL], and tell us what you were trying to do, which screen you were on, and what assistive technology and iOS version you were using.

We aim to acknowledge every report within 2 business days and to tell you what we are going to do about it within 10 business days. If something we have built is stopping you from using the app, say so plainly and we will treat it as urgent.

If you are not satisfied with our response, you can escalate to [COMPANY NAME] at [ADDRESS].

7 · Helpful iOS settings

RepForge inherits these system-wide iOS features, which you may find useful: VoiceOver, Zoom, Larger Text, Bold Text, Increase Contrast, Reduce Motion, Reduce Transparency, Colour Filters, Speak Screen, Voice Control, and Switch Control. They live in Settings ▸ Accessibility on your iPhone.

8 · Scope, standards and formal details

This statement applies to the RepForge iOS app, its Apple Watch companion, and its home-screen widget.

Standards referenced. WCAG 2.2 Level AA; Apple Human Interface Guidelines (Accessibility); Section 508 of the Rehabilitation Act, as a reference standard.

Preparation. This statement was prepared on [DATE] using a self-evaluation of the app's source code and its use of iOS accessibility APIs. It was last reviewed on [DATE] and will be reviewed again by [DATE + 6 MONTHS], or sooner if a significant change ships.

Feedback and enforcement. [COUNSEL TO REVIEW: whether to reference the ADA and a US enforcement route here, and whether a Section 508 VPAT / Accessibility Conformance Report should be produced and linked once the third-party audit is complete.]