Designed to be used by everyone.
Class2Class is committed to making our platform usable for everyone, including people with disabilities. We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA — and we're honest about where we already meet that standard, where we don't yet, and how to tell us when something is broken for you.
Designed for everyone
Accessibility is part of every feature, not remediation work that comes later. We design with assistive technology users in mind from the start.
Honest about gaps
We publish what works, what doesn't, and our remediation timeline. No "fully conformant" claim until an external audit confirms it.
Fast feedback
Acknowledge within 5 working days. Outcome — fix, alternative, or honest "not yet" — within 30 calendar days, matching GDPR Art. 12(3).
Built on certified infrastructure
Bubble (SOC 2 Type II, ISO 27001) and Xano (SOC 2, ISO 27001 family) provide the design defaults that underpin our accessibility posture.
Seven sections — short, direct, and honest.
Click any section to jump to it in the document below.
Class2Class Accessibility Statement.
Last updated 28 April 2026 · Next review by 28 April 2027.
Plain-language summary
Class2Class is committed to making our platform usable for everyone, including people with disabilities. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, as required by the European Accessibility Act (Directive (EU) 2019/882) and the Danish law that implements it. This statement is honest about where we already meet that standard, where we don't yet, and how to tell us when something is broken for you.
Commitment to accessibility
Class2Class.org is a global classroom collaboration platform. We connect classrooms across more than 160 countries, including students who use assistive technology to participate in their education, teachers using accessibility features to do their work, and parents who interact with the platform on their child's behalf. Accessibility is not a separate concern from our mission — it is our mission, applied to the people on the platform.
We commit to:
- Designing and building Class2Class in line with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as a best-practice target, drawing on the harmonised European standard EN 301 549 v3.2.1
- Treating accessibility as part of every feature, not as remediation work that comes later
- Listening to feedback from users with disabilities, prioritising it in our roadmap, and being transparent about progress
- Reviewing this statement at least annually, and sooner whenever a material change to the platform warrants it
This commitment applies to the platform itself, the Teacher Resources area (including the AI Literacy and Responsible Use guide), our published documentation, and our customer-support channels.
Regulatory framework and conformance status
2.1 Why this statement is voluntary — EAA microenterprise exemption
Class2Class ApS qualifies as a microenterprise within the meaning of EAA Article 4(5) and Commission Recommendation 2003/361/EC. EAA Article 4(5) provides that:
"Microenterprises providing services shall be exempt from complying with the accessibility requirements referred to in paragraph 3 of this Article and any obligations relating to the compliance with those requirements."
Class2Class is therefore not legally required by the EAA to publish this statement, conduct a WCAG 2.1 AA audit, or implement EAA service-provider obligations. We publish this statement voluntarily because accessibility serves our users and our mission, and because our partner schools (some of which are subject to their own EAA obligations) increasingly value transparent accessibility commitments from suppliers.
If our company size or turnover ever exceeds the microenterprise thresholds, the EAA's service-provider obligations will apply, and we will update this statement and our timelines accordingly.
2.2 Conformance status
| Aspect | Current status |
|---|---|
| Regulatory status | Microenterprise exempt under EAA Article 4(5); this statement is voluntary best-practice |
| Best-practice target standard | WCAG 2.1 Level AA, drawing on EN 301 549 v3.2.1 |
| Current alignment | Partially aligned — the platform meets many of the WCAG 2.1 AA success criteria via the design defaults of our infrastructure providers, but no formal audit has been conducted; some criteria are known not to be met (see §3) |
| Audit status | We may commission an external WCAG 2.1 AA audit in 2026–2027 as a best-practice exercise; this is not a regulatory requirement for our company size |
Known limitations and remediation timeline
Honesty matters here. Below are the accessibility limitations we are aware of as of the statement date, with the remediation we have planned. If you encounter a barrier that is not on this list, please tell us (see §4) — we will add it.
| Area | Known limitation | Planned remediation | Target |
|---|---|---|---|
| Audit coverage | No external WCAG 2.1 AA audit has been conducted; this statement is based on internal review and our infrastructure providers' certified accessibility postures | External WCAG 2.1 AA audit may be commissioned in 2026–2027 as a best-practice exercise | Best-practice goal |
| Alternative text for images (WCAG 1.1.1) | Some user-uploaded project images do not yet have alt text; some platform-side decorative images are not yet marked decorative | Add alt-text capture flow for new uploads; backfill platform-side images in priority order | Q3–4 2026 |
| Keyboard navigation (WCAG 2.1.1) | Full keyboard navigation has not been comprehensively tested; some interactive components may not be reachable without a pointing device | External audit will identify specific blockers; prioritised fixes follow | 2027 |
| Screen reader compatibility (WCAG 4.1.2) | Compatibility with NVDA, JAWS, and VoiceOver has not been comprehensively tested | Test pass against the three major screen readers; address findings | 2027 |
| Video captions (WCAG 1.2.2) | Some teacher-facing training videos and recorded sessions are not yet captioned | Caption all platform-published video; teacher-uploaded video carries a clear caption guideline and supports auto-captioning | Q3 2026 + ongoing |
| Colour contrast (WCAG 1.4.3) | Contrast ratios across the brand palette have not been formally verified at the 4.5:1 standard for body text and 3:1 for large text | Brand-palette accessibility review; design-system update where ratios fall short | Q3 2026 |
| ARIA live regions (WCAG 4.1.3) | Dynamic content updates (notifications, in-platform alerts) may not announce reliably to screen readers | Implement ARIA live regions on dynamic surfaces | Q3 2026 |
| Multilingual statement | This statement is currently published in English only | Translate to Spanish and Danish to match the languages supported across the platform | Q2 2026 |
Feedback and contact
If you encounter an accessibility barrier on Class2Class — a feature you cannot use, content you cannot read, an alert that doesn't reach your assistive technology — please tell us. Accessibility feedback is treated as a priority.
| You can | Use this contact |
|---|---|
| Report an accessibility barrier on the platform | [email protected] — please use the subject line "Accessibility" so it routes correctly |
| Request alternative formats (large print, plain-text, alternative language) | [email protected] |
| Ask a more detailed accessibility question, or escalate a feedback item that wasn't resolved | [email protected] |
| Lodge a complaint about Class2Class accessibility | See §6 below |
Our service-level commitments. We aim to acknowledge accessibility feedback within 5 working days and provide an outcome — fix, alternative, or honest "not yet" — within 30 calendar days, which matches the GDPR Article 12(3) DSAR timeline.
Where a fix is not feasible immediately, we will explain why and offer a reasonable alternative.
Technical specifications
The platform is built on:
- Bubble (frontend; SOC 2 Type II, ISO 27001) — accessibility settings configured per Class2Class's accessibility design tokens
- Xano (backend, EU data residency; SOC 2 Type II, ISO 27001 family)
- Class2Class custom code for project structure, AI features, and platform-specific UI
Accessibility is supported through:
- Semantic HTML (where Bubble surfaces it) and progressive enhancement
- Keyboard-navigable forms, dialogs, and primary navigation
- Captioning and transcript support for video where authored by Class2Class
- Compatibility tested with current versions of major browsers (Chrome, Edge, Firefox, Safari) and the three major screen readers (NVDA, JAWS, VoiceOver) — pending external audit confirmation
Where to escalate
Class2Class is a microenterprise and is exempt from EAA service-provider obligations under Article 4(5), so the EAA enforcement procedure for service providers does not apply. Even so, if you contact us about an accessibility barrier and you are not satisfied with our response, you have several routes:
| Route | Contact |
|---|---|
| Internal escalation | Email [email protected] (Data Protection Officer — Giancarlo Mena). The DPO may also escalate via the Independent Reviewer channel where the matter involves a Class2Class management member |
| GDPR-related accessibility (e.g., a data-rights request you cannot fulfil because we have not made the form accessible) | Datatilsynet (Danish Data Protection Authority) — [email protected], or your own national supervisory authority. GDPR Article 12 transparency includes accessibility for the data subject regardless of company size. |
| General consumer complaint | The competent consumer protection authority in your country |
| Personal data dimension (e.g. accessibility complaint involving a data-rights request) | Datatilsynet — [email protected] |
The enforcement procedure is independent of Class2Class. You may use it without first using our internal feedback process, although we always prefer the chance to fix the problem ourselves.
Related documents
This statement sits alongside:
- Privacy & Accessibility statement — the platform Privacy Policy
- Terms & Conditions v.2.0 — §10 (Accessibility) cross-references this statement
- Ethical Guidelines v.2026-04-24 — §9 (Inclusive participation)
- AI Literacy and Ethical Conduct Training Programme v.1.0 — modules are designed and delivered to WCAG 2.1 AA standards (Programme §5 Delivery format — Accessibility row)
If any of these documents conflicts with this statement on a matter of substance, this statement governs for accessibility, and we will reconcile the conflict at the next document review.
Quick answers about accessibility on Class2Class.
Why is this statement voluntary?
Class2Class ApS qualifies as a microenterprise under EAA Article 4(5) — fewer than 10 employees and an annual turnover/balance sheet well below €2 million. Microenterprises providing services are exempt from EAA service-provider obligations.
We publish this statement anyway because accessibility serves our users and our mission, and because partner schools value transparent accessibility commitments from suppliers. If we ever exceed the microenterprise thresholds, EAA service-provider obligations will apply and we will update accordingly.
What standard do you target?
WCAG 2.1 Level AA, drawing on the harmonised European standard EN 301 549 v3.2.1. We're partially aligned today — the platform meets many AA success criteria via the design defaults of our infrastructure providers — but no formal audit has been conducted yet. Section 3 lists the limitations we know about with target remediation dates.
What if I find an accessibility barrier?
Email [email protected] with the subject line "Accessibility" so it routes correctly. Tell us what you tried to do, what assistive technology you were using (if any), and what happened.
We acknowledge within 5 working days and give you an outcome — a fix, an alternative, or an honest "not yet" with an explanation — within 30 calendar days. Section 4 has the detail.
Can I request an alternative format for a document?
Yes — large print, plain-text, or an alternative language. Email [email protected] with subject "Accessibility — alternative format". Include the document or page you need and the format you'd like. We'll provide it within the 30-day SLA where reasonably possible.
What if I'm not satisfied with your response?
You have several escalation routes (Section 6 has the full table):
Internal: email the DPO at [email protected]. Where the matter involves a Class2Class management member, the DPO may escalate via the Independent Reviewer channel.
External: if the accessibility issue concerns a data-rights request you can't fulfil because the form isn't accessible, you can lodge a complaint with Datatilsynet (the Danish Data Protection Authority) at [email protected] or your national authority. GDPR Article 12 transparency includes accessibility regardless of company size.
What infrastructure does Class2Class run on?
The platform is built on Bubble (frontend; SOC 2 Type II, ISO 27001) and Xano (backend, EU data residency; SOC 2 Type II, ISO 27001 family), with Class2Class custom code on top. Both providers maintain certified accessibility postures that we benefit from by default. Section 5 has the technical detail.
When will the platform be fully WCAG 2.1 AA conformant?
We don't have a guaranteed date. Most known issues are scheduled for Q3 2026; some larger items (comprehensive keyboard navigation, screen reader testing) are 2027 work. We don't claim "fully conformant" until an external audit confirms it — and we'll update this statement with the audit summary if and when one is commissioned.
Will this statement be available in other languages?
Yes. Class2Class supports English, Spanish, and Danish across the platform. This Accessibility Statement is currently in English only; Spanish and Danish translations are scheduled for Q2 2026 (Section 3, last row).
Found something that doesn't work for you?
Accessibility feedback is treated as a priority. Tell us what you tried to do, what assistive technology you were using if any, and what happened — we'll get back to you within 5 working days.
- Report a barrier[email protected] (subject "Accessibility")
- Alternative format request[email protected]
- Detailed question or escalationGiancarlo Mena (DPO) — [email protected]
- GDPR-related accessibilityDatatilsynet — [email protected]
- Concern about the CEOIndependent Reviewer — [email protected]
Have an accessibility question we didn't answer?
We update this statement at least annually, and sooner whenever a material change to the platform warrants it. If you can help us make it better — or you found a barrier that isn't on our list — write to us at [email protected].
Email support