Accessibility statement
Website last assessed: August 8, 2026. App last assessed: August 26, 2026.
This statement covers the website at rewordme.ai and the Reword Me iOS app. It says what we have actually tested, what we have not tested yet, and what we know is still wrong. We would rather tell you the gaps than claim a level of conformance we have not earned.
Conformance status
We are working towards WCAG 2.2 Level AA for the website. The current status is partially conformant, which means most of the standard is met but some parts have not been verified yet.
We are not claiming full conformance, and we do not use an accessibility overlay widget. Overlays do not achieve conformance and frequently make screen reader use worse, so there is no such script on this site and there will not be one.
The Reword Me app: what we have verified
The Reword Me app is a Messages extension for iPhone and iPad. We only declare support for an accessibility feature on the App Store if we have verified it in the app itself, not just read the code and assumed it works.
- VoiceOver. Every button and label has a name that describes what it does. The daily rewrite count is read aloud correctly, including after it changes. A failed rewrite is announced instead of leaving VoiceOver users guessing why nothing happened.
- Voice Control. The app uses standard iOS controls throughout, and where a button's on screen text did not match its spoken name we added the on screen phrase as an alternate voice command.
- Larger Text. Every screen was tested at the largest accessibility text size on a real device simulator, in addition to the default size. Text wraps and grows instead of clipping or overlapping.
- Dark interface. The app uses the system's light and dark color settings throughout, verified directly in dark mode.
- Differentiate without color alone. Success and error messages use an icon and text, not color alone.
- Sufficient contrast. Every color pair in the app was checked against WCAG contrast ratios and passes.
- Reduced motion. Animations are skipped in favor of an instant change when Reduce Motion is turned on.
The Reword Me app: what we have not tested yet
- Live VoiceOver and Voice Control use. We verified the underlying labels, traits, and standard controls, but we have not yet driven the app end to end with VoiceOver speaking or with spoken Voice Control commands.
- Switch Control. The app uses standard controls that should work with Switch Control, but this has not been directly tested.
- Testing with disabled users. Nothing substitutes for this and we have not done it yet.
If VoiceOver, Voice Control, or any other assistive technology does not work the way you expect inside Reword Me, please tell us. The same contact below applies to the app.
The website: what we have tested
- Automated scanning of every page template with axe-core and with pa11y against the WCAG 2.1 AA rule set, in both the light and dark themes. Both currently report zero violations.
- Keyboard only operation of the navigation, including the mobile menu, verified by walking the focus order in a real browser.
- Operation with JavaScript disabled. The site remains readable and navigable.
- Layout at 375, 768, and 1280 pixels wide, and with text lengths inflated by roughly 40 percent to simulate translation.
- Right to left layout.
An important caveat. Automated tools detect roughly 30 to 40 percent of real accessibility problems. During our own audit the single most serious issue on the site, a mobile menu that no keyboard user could reach, was missed by all three automated tools we ran. Zero automated violations is a floor, not a result.
The website: what we have not tested yet
These are genuine gaps, not formalities.
- Screen readers. We have not yet completed testing with NVDA, VoiceOver, or TalkBack. Target: October 31, 2026.
- Zoom to 400 percent and reflow at 320 pixels. Not yet formally verified. Target: October 31, 2026.
- Text spacing overrides. Not yet verified. Target: October 31, 2026.
- Windows High Contrast Mode. Not yet verified. Target: December 31, 2026.
- Testing with disabled users. Nothing substitutes for this and we have not done it. No date yet, because committing to one we cannot keep would be worse than saying so.
Known limitations
- The contact form confirmation page. After you submit the contact form, the confirmation is served by Formspree, a third party. We do not control that page and cannot vouch for its accessibility. If it causes you a problem, email us directly at the address below instead of using the form.
- App screenshots. The screenshots of the app contain text inside images. They have alternative text describing what they show, but the text inside them cannot be resized or selected.
- English only. The site is currently available in English only, which is a barrier for anyone who reads another language more comfortably.
Tell us about a problem
If something on this site is difficult or impossible for you to use, please tell us. You do not need to know why it is broken or what the standard says. Describing what happened is enough.
Email james@njligames.com. We aim to reply within 5 business days. If a problem blocks you from something you need, say so in the subject line and we will prioritise it.
If we cannot fix an issue quickly, we will tell you what the workaround is and when we expect a real fix.
Technical information
Accessibility here relies on HTML, CSS, and a small amount of JavaScript. The site is built to work without JavaScript, with reduced motion preferences honoured, and with the browser and operating system font size settings respected.
Standard used: Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.
This statement was created on August 8, 2026 and reflects testing performed on that date. It is reviewed whenever the site changes materially, and at least every six months.