Accessibility Statement

Effective 2026-05-19 · Version 1.0 · Conformance target: WCAG 2.2 Level AA.

Short version: Event Trekker — the mobile app, the web app, and this marketing site — is being built to work toward the Web Content Accessibility Guidelines 2.2 Level AA. We run automated checks (axe + Pa11y) on every pull request, and we hand-test with screen readers (VoiceOver on iOS and macOS, TalkBack on Android, NVDA on Windows) at every release. If something does not work for you, please write to support@neuralnestsolutions.com; we aim to triage accessibility reports with high priority.

1. What this statement covers

• This marketing site at et.nnssys.com and its sub-pages.
• The Event Trekker web app at web.et.nnssys.com and the corresponding iOS / Android builds in the App Store and Play Store.

2. Conformance status

WCAG 2.2 Level AA — we are working toward this target and consider the Service partially conformant at this time. "Partially conformant" means some parts of the content do not yet fully meet the standard, either because of known issues (§4) or because they are awaiting external review. We aim to reach full Level AA conformance and, where practical, to arrange an independent review; any resulting report will be published here.

3. How we build for accessibility

• Semantic HTML & ARIA: all interactive widgets have explicit roles, names, and states.
• Keyboard support: every interactive element is reachable and operable with a keyboard only. Visible focus rings honour :focus-visible.
• Colour contrast: body text ≥ 4.5:1, large text ≥ 3:1, UI components ≥ 3:1 against their backgrounds — verified by automated check on every PR.
• Reduced motion: all CSS animations honour the user's prefers-reduced-motion setting.
• Screen reader support: every screen has a logical reading order; every icon has a text alternative; live regions are used sparingly and announced politely.
• Text resizing: all UI scales to 200% without horizontal scroll on mobile and without content reflow loss.
• Touch targets: minimum 44 × 44 CSS pixels per WCAG 2.5.5 / 2.5.8.
• Language: every page declares lang="en" on the root <html>. Localised content carries its own lang.

4. Known issues

The list below is honest. We track each item in our backlog and aim to resolve them before Phase 7 release-readiness.

• Inline SVG screenshots on the marketing site — currently load as <img> with an alt-text summary of the scene. We have not yet authored full screen-reader scripts for each chart and timeline detail. Workaround: read the FAQ + Pricing + About sections for full feature coverage.
• QR-code attachments in the mobile app — VoiceOver / TalkBack reads "QR code attached" rather than the encoded content. By design (QR contents are machine-readable and would not be useful read aloud).
• Map embeds in v1.4+ (not in MVP) — when we add map embeds for venues, we will publish a paired text-list alternative; this is on the backlog as BR-NFR-T26-MAP-A11Y.

5. Compatible assistive technologies

• VoiceOver on iOS 16+ and macOS 13+ (Safari).
• TalkBack on Android 11+ (Chrome / built-in browser).
• NVDA latest on Windows 10/11 (Firefox, Chrome, Edge).
• JAWS latest on Windows 10/11 (Chrome) — community feedback welcome.
• Switch Control (iOS), Voice Control (iOS / macOS), Dragon NaturallySpeaking — best-effort.

6. Legal alignment

NeuralNest Solutions (NNS) is an India-based company. We aim to align with the following, on a best-effort basis, for the geographies our users are in:

• Rights of Persons with Disabilities (RPwD) Act, 2016 (India) — as an India-based provider, we aim to make Event Trekker accessible to our Indian users; this is tracked as part of our WCAG 2.2 AA program.
• European Accessibility Act (EAA) — where Event Trekker is offered to EU consumers, we aim to align our in-scope offerings with EAA expectations.
• EN 301 549 v3.2.1 — the European harmonised standard that maps to WCAG 2.1 AA + extras; we are validating against the WCAG 2.2 AA superset.
• Section 508 of the US Rehabilitation Act — best-effort alignment for US users.

7. Report an accessibility problem

If you encounter a barrier, please write to support@neuralnestsolutions.com. Include:

• The page or screen you were on (URL or in-app screen name);
• What you were trying to do and what went wrong;
• Your assistive technology + version, if you use one;
• How urgent it is for you.

We aim to acknowledge accessibility reports within 2 business days and to respond with a fix or a plan within 10 business days. We do not require you to demonstrate disability or proof of any kind; the report is the trigger.

8. Escalation

If you are not satisfied with our response, you can lodge a complaint with the relevant accessibility authority in your jurisdiction (for example, in India the Office of the Chief Commissioner for Persons with Disabilities). Our internal escalation path is:

1. Initial: support@neuralnestsolutions.com
2. Escalation: support@neuralnestsolutions.com with subject "ESCALATION: accessibility"

9. Testing methodology

• Automated: axe-core + Pa11y on every pull request via GitLab CI; failure on any AA violation blocks merge.
• Hand-testing: release candidates are walked through with VoiceOver (iOS), TalkBack (Android), and NVDA (Windows) by our accessibility reviewer.
• Independent review: where practical, we aim to arrange a review with a third-party agency; any resulting report will be linked here.
• Real-user feedback: the accessibility inbox above is monitored, and reports are logged and tracked to resolution.

10. Contact

Accessibility reports: support@neuralnestsolutions.com
General support: support@neuralnestsolutions.com

Changelog

• 2026-05-19 · v1.0 · Initial publication.

← Back to Event Trekker