Eco Heroes International SL is committed to making the Eco Heroes Academy accessible to the widest possible audience, including people with disabilities. This statement describes the current accessibility status of the Platform, known limitations, and how to report problems.
1. Scope
This Accessibility Statement applies to the Eco Heroes Academy website and Platform at learn.eco-heroes.org, including all its public pages, the Learner registration and login flow, legal pages, and the learning experience itself once launched.
This statement does not cover:
- Third-party services linked from the Platform (for example, the payment processor's checkout page, or external references in course content). Those services are covered by their own accessibility statements.
- User-generated content, if and when such functionality is added in the future.
- PDF documents generated by the Platform (such as Diplomas) — see Section 4 below.
2. Conformance target
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the reference standard under:
- EU Directive 2016/2102 on the accessibility of public sector websites and mobile applications.
- EU Directive 2019/882 on accessibility requirements for products and services (the European Accessibility Act, applicable from 28 June 2025).
- Spanish Royal Decree 1112/2018, which transposes the 2016 Directive.
- The EN 301 549 European standard on accessibility requirements for ICT products and services.
WCAG 2.2 AA is the standard against which we self-assess below. We have not yet obtained a third-party audit or certification against this standard.
3. Current status
Based on internal review of the Platform as of the effective date of this statement, we assess our conformance as follows, broken down by the four WCAG principles:
3.1 Perceivable
- All non-decorative images have descriptive alt text. Decorative elements (such as the SDG rainbow bar) are marked
aria-hiddenso screen readers skip them. - Text-on-background colour contrast meets or exceeds the 4.5:1 ratio required for body text at WCAG AA (dark green
#1E5631on cream#FAF8F3gives 10.4:1; dark body text#1A2318on cream gives 15.7:1). - Layout scales cleanly to at least 400% zoom in desktop browsers without loss of content or functionality.
- The Platform respects the operating system's
prefers-reduced-motionsetting: when enabled, the logo spin animation and any scroll transitions are disabled. - Text sizing is controlled with relative units (
rem), which respects browser font-size preferences. We have not yet formally tested at all browser zoom levels on mobile.
3.2 Operable
- All interactive elements (links, buttons, form fields) are reachable and usable with the keyboard alone, in a logical tab order.
- A "Skip to main content" link is provided for screen reader and keyboard users, visible when focused (see top-left of this page when you press Tab).
- Form fields have visible focus indicators.
- No feature of the Platform requires a gesture, time limit, or mouse-specific interaction to complete.
- Some pages in the learner-facing authentication flow (login.php, register.php) inherit focus styles from the design system but have not been individually tested for focus visibility on every interactive element. We will audit and fill any gaps by Q3 2026.
3.3 Understandable
- The document language is declared on every page via the
langattribute on the<html>element. - Form fields have explicit
<label>elements associated byfor/id. - Error messages on authentication forms are clear and describe both what went wrong and, where safe to disclose, how to correct it.
- The Platform is currently published in English only. Content translations into Spanish, Catalan, Italian and further EU languages are planned; translated versions will carry the correct
langattribute at publication.
3.4 Robust
- Pages use semantic HTML5 landmarks (
<header>,<main>,<footer>,<article>,<aside>). - HTML validates with no major errors. We use ARIA attributes only where they add meaning beyond what the HTML element already communicates, following the first rule of ARIA: don't use ARIA when a native HTML element will do.
- We have not yet performed end-to-end screen reader testing with NVDA, JAWS, VoiceOver, or TalkBack. This is scheduled before the Platform's full public launch.
4. Known limitations
The following items are known gaps at the time of this statement. Each has a tracked resolution path:
- Skip-to-content link on legacy pages. This Accessibility Statement has a skip-to-content link. The Terms of Service, Privacy Policy, Legal Notice, and Cookie Policy pages currently do not. We will add them in the next legal-pages update pass (target: before Learner production launch).
- PDF Diplomas. The Diploma generated on course completion will be delivered as a PDF. We plan to use tagged PDFs with a logical reading order, but this has not yet been implemented — the feature itself is not yet live. Accessibility of the Diploma PDF will be addressed as part of its initial release.
- Video content. Course content will include video material. All videos at launch will include closed captions in the language of the video; audio descriptions and full transcripts will be phased in over the first year after launch. Sign language interpretation is not planned for the initial content set.
- Quiz interaction model. The quiz component is not yet built. When designed, it will be fully keyboard-operable, will not rely on time limits by default, and will surface feedback in a way readable by assistive technology.
- Formal third-party audit. We have not yet commissioned an independent accessibility audit. We commit to obtaining one within twelve (12) months of public launch and to publishing its findings (including any adverse findings) in an updated version of this statement.
If you encounter a barrier not listed here, please report it (see Section 7).
5. How we built for accessibility
The Academy is built on a small number of deliberate design decisions that reduce the accessibility-tax of every new page:
- Semantic HTML first. The Platform avoids
<div>soup. Headings are real heading elements, form labels are real<label>s, landmarks are real landmark elements. - Minimal JavaScript for core flows. Registration, login, email verification, and reading legal documents all work without any JavaScript. If the script fails to load, the Platform still functions.
- No modals, overlays, or pop-ups that trap keyboard focus.
- No autoplaying media.
- No CAPTCHA on the registration flow in the current release; security is provided by server-side rate limiting (see Privacy Policy §7). If we introduce a CAPTCHA in the future, it will offer an accessible alternative.
- Respect for system preferences — we honour
prefers-reduced-motion,prefers-color-scheme(planned for next iteration), and browser font-size settings. - Colour is never the only signal — status indicators use both colour and text labels (for example, the status markers on this page show ✓ / ◐ / ? icons and the words "Pass", "Partial", "Not audited").
6. Assistive technology compatibility
The Platform has been built to be compatible with recent versions of common assistive technologies, including:
- Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS), TalkBack (Android).
- Screen magnifiers: built-in OS magnifiers, ZoomText.
- Voice control: Dragon NaturallySpeaking, Voice Control (macOS), Voice Access (Android).
- Keyboard-only navigation without assistive software.
Compatibility has been designed-for but not yet end-to-end tested with each of these tools. See Section 4.
7. Report a problem
If you find an accessibility barrier on the Eco Heroes Academy, please let us know. We take every report seriously and aim to respond within ten (10) working days.
Eco Heroes International SL
Email: info@eco-heroes.org (please put "Accessibility" in the subject line)
Postal: Girona, Spain (available on request)
In your report, if you can, please include:
- The URL of the page where you encountered the problem.
- A description of the barrier — what you were trying to do, and what stopped you.
- The assistive technology or browser configuration you were using, if relevant.
We will acknowledge your report, investigate, and tell you what we can fix and when. If we cannot fix something reasonably, we will tell you why and propose an alternative.
8. Enforcement
If you are not satisfied with our response to an accessibility report, you can lodge a complaint with the competent Spanish authority:
Unidad Responsable de Accesibilidad
Ministerio de Asuntos Económicos y Transformación Digital
via the electronic registry at administracion.gob.es
or the Oficina de Atención a la Discapacidad (OADIS).
These channels apply under Spanish Royal Decree 1112/2018. Note that the 2018 Royal Decree is addressed primarily at public sector bodies; as a private-sector commercial platform we are not strictly within its scope, but we choose to offer the same redress mechanism because it is the most visible route familiar to Spanish users.
9. Review and updates
This Accessibility Statement is reviewed at least annually and whenever significant changes are made to the Platform. The "Next review" date at the top of this page is the latest date by which this statement will be re-assessed.
Previous versions are retained internally so that regulators and users can verify the timeline of changes.
Revision log
- 22 April 2026 — v1.0 — initial publication. Self-assessment only, no third-party audit yet.
This Accessibility Statement was last updated on 22 April 2026 (version 1.0). The most current version is always available at learn.eco-heroes.org/legal/accessibility.html.