Accessibility Statement
Last updated: 11 May 2026
Our Commitment
easy.bi GmbH is committed to making www.easy.bi usable by as many people as possible, regardless of ability or assistive technology. We treat accessibility as a quality of engineering, not an afterthought.
Conformance Target
We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the technical standard referenced by the European Accessibility Act (EAA / Directive (EU) 2019/882) and the German Barrierefreiheitsstärkungsgesetz (BFSG). Conformance has not yet been independently audited; this statement reflects our internal review and ongoing work.
What We've Done
- Semantic HTML throughout (one
h1per page, logical heading hierarchy) - Visible keyboard focus indicators on every interactive element
- Sufficient colour contrast on body text and primary CTAs (verified against WCAG AA thresholds)
- Descriptive
alttext on meaningful images; decorative images marked with empty alt - Captions / transcripts for video content where available
- Forms with associated labels, error messages, and required-field indicators
- Skip-to-content link on every page
- Responsive layout that adapts down to 320 px width and zooms to 400 % without horizontal scroll loss
- Content language declared in HTML (
lang="en"/lang="de")
Ongoing Work
We continuously review the site and welcome feedback on any barriers you encounter.
Feedback and Contact
If you experience an accessibility issue or need information in a different format (e.g. plain text, large print), contact us:
Email: info.de@easy.bi
Phone: +49 40 228599 600
Post: easy.bi GmbH, Hongkongstrasse 1, 20457 Hamburg, Germany
We aim to respond to accessibility enquiries within 5 business days.
Enforcement
If you're not satisfied with our response, you may contact the relevant enforcement body. In Germany, the central authority for accessibility complaints is the Bundesfachstelle Barrierefreiheit (bundesfachstelle-barrierefreiheit.de).
How We Test
We use a mix of automated tooling (Lighthouse, axe-core), manual keyboard navigation, screen-reader testing (VoiceOver on macOS, NVDA on Windows), and code reviews against WCAG success criteria. Accessibility is part of our pre-launch checklist; we welcome external audit feedback to improve.