Accessibility Statement
YourStory: Your Romance
Last updated: [EFFECTIVE DATE]
StoryForge Consulting Ltd (“StoryForge”, “we”, “us”) is committed to making the “YourStory: Your Romance” mobile app for iOS and Android, the website at example.com and our share link pages (together, the “Service”) accessible to as many people as possible, including people with disabilities. Everyone should be able to enjoy a great story.
1. Our standard
We aim for the Service to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C), and to the relevant requirements of the European standard EN 301 549 (Accessibility requirements for ICT products and services). We take into account the requirements of the European Accessibility Act (Directive (EU) 2019/882) as implemented in the EU Member States.
2. Conformance status
The Service is partially conformant with WCAG 2.2 Level AA. “Partially conformant” means that some parts of the content do not yet fully conform to the standard. We are working to address the known limitations listed in Section 4.
3. What we do to support accessibility
Reading experience
- Adjustable font and font size in the reader, and support for your device’s system text size settings where technically possible.
- Multiple reading themes (including light and dark), designed to maintain readable contrast.
- Search within text, bookmarks and chapter navigation to make it easier to find your place.
- A portrait layout designed for one-handed use.
Interface
- Text and interface elements designed to meet WCAG colour contrast ratios.
- Tap targets sized to support users with limited dexterity.
- Labels for buttons and controls so they can be read by screen readers such as VoiceOver (iOS) and TalkBack (Android).
- Status of chapters (Ready, Generating, Locked, Unavailable) communicated in text, not by colour alone.
- Clear error messages and recovery options for offline and generation failure states.
- Support for your device’s reduce motion setting where technically possible.
Website
- Semantic HTML structure with headings and landmarks.
- Keyboard navigation and visible focus indicators.
- Text alternatives for meaningful images.
4. Known limitations
Despite our efforts, some content may not yet be fully accessible. We are aware of the following:
| Area | Limitation | What we are doing |
|---|---|---|
| AI-generated images (covers, chapter illustrations, share cards) | Images are created automatically, so text alternatives may be generic (for example, the book or chapter title) rather than describing the image in detail. | Exploring automatically generated image descriptions. The story text is always available in full and does not depend on images. |
| AI-generated video highlights | Generated videos may not have captions or audio description. | Videos are an optional extra; all story content is available as text. We are evaluating captions and descriptions. |
| QR codes on share cards | QR codes cannot be read by screen readers. | Every share also provides a text link that can be copied. |
| Third-party screens | App store purchase sheets, Sign in with Apple or Google, and web payment pages are provided by third parties and their accessibility is outside our control. | We use providers’ standard, accessibility-supported components wherever possible. |
| Onboarding sliders | Some questionnaire slider inputs may be difficult to operate precisely with assistive technology. | Improving accessible labels and step controls for sliders. |
| Very large text sizes | At the largest system text sizes, some screens may require scrolling or truncate text. | Reviewing layouts for large text support. |
5. Compatibility
The Service is designed to be compatible with:
- the latest two major versions of iOS with VoiceOver;
- recent supported versions of Android with TalkBack;
- the latest versions of Chrome, Safari, Firefox and Edge on desktop and mobile.
It may not work fully with older operating systems, browsers or assistive technologies.
6. How we assess accessibility
We assess the accessibility of the Service through self-evaluation by our team, including automated testing tools, manual testing with screen readers and keyboard navigation, and user feedback. We include accessibility checks when we design and release new features.
7. Feedback and alternative formats
We welcome your feedback. If you encounter an accessibility barrier, need information in an alternative format, or have suggestions for improvement, please contact us:
- Email: accessibility@example.com
- In the app: Settings > Help > Report an issue (choose “Accessibility”)
- Post: StoryForge Consulting Ltd, [REGISTERED OFFICE ADDRESS, CYPRUS]
Please tell us the page or screen, the device and assistive technology you use, and the problem you experienced. We aim to acknowledge your message within 5 business days and to respond fully within 15 business days.
8. Enforcement
If you are not satisfied with our response, you may contact the authority responsible for enforcing accessibility requirements in your EU Member State of residence.
9. Updates to this statement
We review this statement at least once a year and when we make significant changes to the Service. This statement was prepared on [EFFECTIVE DATE] based on a self-assessment.