Declaração de acessibilidade

1. Introduction

This Accessibility Statement applies to the Lastribe mobile application (iOS and Android) and the website www.lastribe.eu, operated by EnableUnion SASU, a company registered in France.

Lastribe is committed to ensuring digital accessibility for all users, including people with disabilities. We continually work to improve the user experience for everyone and to comply with applicable accessibility standards and legislation, including the European Accessibility Act (Directive (EU) 2019/882) and its French transposition.

2. Compliance Status

Lastribe is partially conformant with EN 301 549 V3.2.1 (2021-03), the European Harmonized Standard for ICT accessibility, which incorporates the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

"Partially conformant" means that some parts of the content do not yet fully conform to the accessibility standard. This status results from a self-assessment, not from a third-party audit (Section 7).

The application is in active development, and we are working toward full compliance. Our accessibility targets are:

• WCAG 2.1 Level AA for all content across the mobile application and website.
• WCAG 2.1 Level AAA for safety-critical content, including emergency alerts, civil protection warnings, and evacuation information, where the highest level of accessibility is essential for user safety.

3. Non-Accessible Content

The following content is not yet fully accessible. We are actively working to resolve these limitations:

3.1 Data Visualizations

Some complex data visualizations, including PrepScore radar charts, barometer pressure charts, and risk index gauges, may not be fully accessible to screen reader users. Text-based alternatives summarizing the data are provided alongside these visualizations.

3.2 Map Features

Map-based features, including the unified map, extraction route visualization, offline map downloads, and shelter/AED location markers, have limited screen reader support due to the inherent complexity of interactive map interfaces. List-based alternatives are available for all map content, allowing users to browse locations, routes, and points of interest without relying on the map interface.

3.3 Third-Party Content

Some third-party content integrated into the application, such as embedded news articles from RSS feeds and external alert provider data, may not meet WCAG 2.1 AA standards. We do not control the accessibility of this external content but apply formatting and structure where possible.

3.4 PDF Exports

PDF documents generated by the application (such as GDPR data exports) may have limited accessibility. We are working to ensure all generated documents conform to PDF/UA (ISO 14289-1) standards.

3.5 Disproportionate Burden

No claims of disproportionate burden are made at this time.

3.6 Remediation Timeline

All identified accessibility issues are tracked in our development roadmap. We aim to address critical accessibility barriers within each release cycle and to achieve full WCAG 2.1 AA conformance before public launch.

4. Feedback Mechanism

We welcome feedback on the accessibility of Lastribe. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

• E-mail: support@lastribe.eu (subject line: Accessibility)
• Post: EnableUnion SASU, 7A rue Neuve, 57270 Uckange, France
• Response time: We respond to accessibility feedback within 15 business days.

We take all accessibility feedback seriously and will work to address reported issues promptly.

5. Enforcement Authority

France

If you are not satisfied with our response to your accessibility feedback, you may file a complaint with the:

Défenseur des droits Libre réponse 71120 75342 Paris CEDEX 07 France

• Website: www.defenseurdesdroits.fr
• Phone: 09 69 39 00 00

Emergency reminder. Lastribe is not an emergency channel. In France, if you are deaf, hard of hearing or cannot speak, the emergency services can be reached by SMS or video through the 114 number; the voice number for the whole European Union is 112.

Other EU Member States

Users in other EU member states may contact their national enforcement body designated under the European Accessibility Act (Directive (EU) 2019/882). A list of national enforcement authorities is maintained by the European Commission.

6. Technical Specifications

Lastribe relies on the following technologies and accessibility features:

Platform Accessibility Services

• iOS: VoiceOver screen reader, Dynamic Type (system font scaling), Switch Control, Reduce Motion, Increase Contrast, Smart Invert
• Android: TalkBack screen reader, system font scaling, Switch Access, Remove Animations, High Contrast Text, Color Inversion

Application Technologies

• Mobile application: React Native (Expo), with native accessibility APIs (AccessibilityInfo, accessibilityLabel, accessibilityRole, accessibilityState)
• Website: Next.js, HTML5, CSS3, WAI-ARIA landmarks and attributes
• Styling: Supports system dark mode, respects reduced motion preferences, responsive layout for all screen sizes

Accessibility Features Implemented

• Semantic heading structure and landmark regions
• Meaningful alternative text for images and icons
• Touch target sizes of at least 44x44 points (iOS) / 48x48 dp (Android)
• Color contrast ratios meeting WCAG 2.1 AA (minimum 4.5:1 for normal text, 3:1 for large text)
• Focus management for modal dialogs and navigation
• Keyboard and switch control navigation support
• No content that flashes more than three times per second
• Text resizing support up to 200% without loss of content or functionality

7. Assessment Method

The accessibility of Lastribe has been evaluated through:

• Self-assessment against the criteria of EN 301 549 V3.2.1 and WCAG 2.1 Level AA.
• Automated testing using accessibility linting tools integrated into the development pipeline.
• Manual testing with VoiceOver (iOS) and TalkBack (Android) screen readers on physical devices.
• Reduced motion and font scaling testing to verify the app adapts to user accessibility preferences.

An independent third-party accessibility audit is planned before public launch to validate conformance and identify any remaining barriers.

8. Date

• Statement prepared: April 6, 2026
• Last conformance audit (substantive accessibility review): April 6, 2026
• Editorial review (no audit performed): May 14, 2026 — cadence alignment with the broader Lastribe legal corpus and reintroduction of French diacritics. No re-verification of WCAG/EN 301 549 conformance was performed on this date.
• Spot-check + remediation: May 15, 2026 — V5 web brand-identity rollout (PRs #123, #125, #127–#131) shipped new color tokens for the landing surface. Spot-checked contrast of all new color pairs; identified that the hero / closer waitlist submit buttons rendered with color: #fff on Ember #e76f2d background (3.13:1, fails WCAG AA). Remediated by switching the button label to color: var(--ink) (dark Ink #0c100e on Ember = 6.12:1, AA). All other token pairs (Ink on Sand 15.91:1 AAA, Ink-muted on Sand 4.87:1 AA, Ember-Dim #b8561f on Sand 5.0:1 AA for text accents) verified compliant. No full third-party audit performed.
• Editorial review (no audit performed): October 14, 2026 — feedback channel corrected (the application has no dedicated accessibility form; feedback goes by e-mail or post), 114 emergency reminder added for France, header aligned with the legal corpus. No re-verification of WCAG/EN 301 549 conformance was performed on this date.
• Next planned conformance audit: April 6, 2027 (yearly cadence). An independent third-party audit is targeted before the public launch of the Service.

9. Version History

Version	Date	Summary of changes
1.0	April 6, 2026	Initial statement (internal preparation, no third-party audit). Partial conformance with EN 301 549 V3.2.1 / WCAG 2.1 AA targeted; WCAG 2.1 AAA for safety-critical content.
1.1	May 14, 2026	Editorial review only — Date section clarified to distinguish "last conformance audit" (April 6, 2026) from "last editorial review" (May 14, 2026, no audit). French diacritics reinstated. Yearly audit cadence confirmed (next audit: April 6, 2027). No WCAG/EN 301 549 re-verification.
1.2	May 15, 2026	Spot-check + remediation following the V5 web brand-identity rollout (PRs #123, #125, #127–#131). Waitlist submit button label color corrected (#fff → var(--ink)) to pass WCAG 1.4.3 AA (6.12:1 contrast on Ember instead of 3.13:1). All other token pairs verified compliant. No full third-party audit.
1.3	October 14, 2026	Plan 176 wave F (EU legal audit). Feedback mechanism corrected: the "Settings › Accessibility › Report a problem" path did not exist in the application; feedback is by e-mail or post. 114 emergency reminder for France added. Header lines aligned with the legal corpus; version history moved into both language halves. No audit.