Accessibility Statement

Document: Accessibility Statement · Last updated: 2026-07-31 · Effective: 2026-07-31

Accessibility Statement

Farouk Fusion believes the fun of EFURC, the worlds of EFER and EFEMM, and the help of JKPHermex should be available to everyone, including people who use assistive technologies. This statement describes our accessibility goals for farouks-fusion.com and the related Services, the standards we aim for, the assistive technologies we test, the limits we know about, and how to report problems to us.

1. Conformance target

Farouk Fusion aims to conform to WCAG 2.1 Level AA (Web Content Accessibility Guidelines, W3C Recommendation, June 2018) on farouks-fusion.com and on the web-based surfaces of all Services. For users in the European Union, our web targets also satisfy the harmonised European standard EN 301 549 (latest published version), which incorporates WCAG 2.1 AA by reference. Mobile app targets go beyond AA where practical; in particular we aim for a mobile AAA UX target for touch-target sizing (44pt+), contrast in dark-mode UI, and reduced-motion respect on animated effects.

2. What we do

• Semantic HTML. Pages use proper landmark roles (header, nav, main, footer) and skip links so screen-reader and keyboard users can navigate quickly.
• Keyboard operability. Every interactive element is reachable and operable with the keyboard alone. We surface a visible focus ring using :focus-visible with at least 3px of outline and 2px offset.
• Color contrast. Text colours meet at least 4.5:1 against their background (AA) and 3:1 for large text and UI components. Brand gold and cyan are used for accents, never as the only carrier of meaning.
• Resizable text. Layouts are responsive and remain usable at 200% zoom and at 320px viewport width.
• Alt text. Informative images carry meaningful alternative text; decorative images use alt="".
• Captions and transcripts. Cinematic EFER videos include captions and downloadable transcripts; EFEMM trailers include audio descriptions where the visual content is essential.
• Reduced motion. Animated hero banners, EFURC card flips, and JKPHermex loading indicators respect prefers-reduced-motion and present a static or simpler alternative.
• Form labels. All form fields are programmatically labelled; errors are announced to screen readers via aria-describedby or aria-live.
• Language. Pages declare lang="en"; passages in other languages use the lang attribute.

3. Assistive technologies we test with

For EFURC, EFER, and EFEMM on console / desktop, we additionally test with platform-native accessibility APIs (Xbox Narrator, PS5 Screen Reader, Windows UI Automation) where the platform exposes them.

4. Known limitations

We are honest about what is not yet perfect. The following items are tracked in our accessibility backlog:

• EFURC combat log in spectator mode is updated at high frequency and is not yet fully exposed to screen readers. A toggle for a simplified text log is on the roadmap.
• EFEMM 3D avatar viewer on lower-end devices occasionally reduces contrast for the avatar’s outline to maintain frame rate. A high-contrast outline mode is in beta.
• JKPHermex markdown rendering can produce nested lists where some screen readers do not announce levels correctly. We are tracking the upstream NVDA bug and apply a workaround where possible.
• Farouks-fusion.com PDF downloads (white-papers, lore PDFs) may not be fully tagged. We are migrating to tagged-PDF exports by Q4 2026.
• Older Android (10 and earlier) on JKPHermex may not expose all TalkBack gestures for the chat composer. We document the supported gestures in the in-app help.

If a feature you need is on this list, please contact us — we prioritise backlog by user impact.

5. EN 301 549 and EU compliance

For users in the European Union, our web targets and procurement practices are designed to satisfy the requirements of the European Accessibility Act (Directive (EU) 2019/882) as transposed by Member States, and the harmonised technical specification EN 301 549. Where Member-State rules require additional local-language support or higher standards (for example, the German BFSG or French RGAA), we work to meet them. JKPHermex on Android follows the WCAG 2.1 AA mobile target plus platform-specific accessibility APIs.

6. Mobile UX target (AAA-oriented)

Our mobile apps (EFURC, JKPHermex) target AAA-friendly mobile UX:

• Minimum 44pt logical touch targets (AAA mobile guidance).
• 7:1 contrast for primary action text in dark mode (AAA contrast).
• Reduced-motion mode for card flips, particle effects, and JKPHermex typing indicators.
• Voice Control / Switch Control compatible focus order.
• Haptic feedback is non-essential; never the sole channel of information.

7. Feedback and complaints

If you encounter an accessibility barrier on any of our Services, please let us know:

• Email: osei1sup@gmail.com.
• In-app: open the app, go to Settings → Help → Accessibility feedback.
• Phone / relay: see farouks-fusion.com/contact for relay service support.

We aim to acknowledge within 2 business days and to propose a fix or workaround timeline within 10 business days. You can also file a complaint with your national enforcement body (e.g., the U.S. Department of Justice for ADA Title III complaints, the UK Equality and Human Rights Commission, or the EU Member-State designated authority under the European Accessibility Act).

8. Compatibility with browsers and assistive tech

farouks-fusion.com is tested on the two most recent major versions of Chrome, Firefox, Safari, and Edge. We do not require Internet Explorer. If you use an older browser, some interactive features may not work; please email osei1sup@gmail.com if you need assistance.

9. Assessment approach

We combine three methods:

1. Automated audits using axe-core and Lighthouse on every release candidate.
2. Manual expert audits (keyboard-only navigation, screen-reader walkthroughs) before major releases.
3. User testing with assistive-technology users, recruited through community channels and compensated for their time.

10. Changes to this statement

We will update this page as we fix issues or add new Services. The “Last updated” date at the top records the most recent revision.

11. Specific commitments by product

11.1 EFURC (Unreal Engine 5)

• In-game UI scales 100%–200% without clipping.
• Combat log toggle provides a high-contrast, screen-reader-readable text feed.
• Card text uses high-contrast outlines so it remains legible on every background.
• Voice- and switch-control compatible menus on supported platforms.

11.2 JKPHermex (Android)

• Native TalkBack labelling throughout the chat composer and history.
• Voice-control compatible: “type,” “send,” “clear,” and “new chat” are exposed.
• Reduced-motion mode disables typing-indicator animation and message-bubble parallax.
• High-contrast dark theme with AAA contrast for primary action text.

11.3 EFER and EFEMM (lore and character sites)

• Lore pages are static HTML with proper heading hierarchy for screen-reader navigation.
• Embedded cinematic videos include captions and a downloadable transcript.
• EFEMM avatar viewer supports a high-contrast outline mode and an “alt text only” view that replaces 3D content with a static image and descriptive text.

11.4 farouks-fusion.com

• Skip link, landmark roles, and visible focus rings on every page.
• Forms support autofill, error announcements, and label associations.
• PDFs are being migrated to tagged-PDF exports (Q4 2026 target).

12. Acknowledgements and standards

We use the W3C WCAG 2.1 specification, the WAI-ARIA 1.2 Authoring Practices, and the European harmonised standard EN 301 549 as our working references. We also reference the W3C Mobile Accessibility Guidelines and the BBC Mobile Accessibility Guidelines when designing JKPHermex and EFURC.

13. Contact

Questions about this Accessibility Statement can be sent to osei1sup@gmail.com.

14. Specific success metrics

We track accessibility progress with concrete numbers, not just statements of intent:

• Lighthouse Accessibility score on farouks-fusion.com (target ≥95).
• axe-core violations per release candidate (target: 0 critical, ≤3 serious).
• Percentage of JKPHermex UI components labelled for TalkBack (target 100%).
• Number of accessibility-related user reports resolved within 30 days.
• Number of user-testing sessions with assistive-technology users per quarter (target ≥4).

15. Continuous improvement

Accessibility is treated as a release-blocking category: a regression that drops the Lighthouse Accessibility score below 90 or introduces a WCAG AA violation blocks the release until fixed. Our roadmap for the next 12 months includes:

• Shipping a tagged-PDF export pipeline for all PDFs on farouks-fusion.com.
• Adding audio descriptions to EFER cinematic trailers.
• Launching a simplified-text-log mode in EFURC spectator view.
• Conducting an external WCAG 2.2 audit of the EFURC and JKPHermex flagship flows.

Farouk Fusion is committed to keeping EFURC, EFER, EFEMM, JKPHermex, and farouks-fusion.com accessible. Public accessibility and legal requests currently route to osei1sup@gmail.com.