Onepage is constantly working to improve digital accessibility. Our goal is to enable small and medium-sized enterprises (SMEs) to create Onepage websites that comply with current digital accessibility standards.
Our technical development is guided by the international Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, as well as the requirements of the German Act on Strengthening Accessibility (BFSG) and the underlying EU Directive (2019/882).
Scope
This statement applies to two areas:
The Onepage platform (onepage.io), for which we, as the provider, are responsible.
The customer websites created with Onepage, whose accessibility results from the interaction between our builder and the content you provide. We provide the technical foundation; the final level of accessibility also depends on how you use content, colors, text, and media.
What we have already implemented
As part of our accessibility release in April 2026, we rolled out extensive improvements to websites published using Onepage.
These improvements take effect automatically as soon as you republish your website. You don’t need to make any changes to your content.
Semantic page structure: Published pages now use correct HTML landmarks (Header, Main, Footer) so that assistive technologies like screen readers can navigate the page effectively.
Keyboard accessibility: All interactive elements, such as menus, buttons, forms, and modals, are now accessible and operable via the keyboard. A "Skip to main content" link helps users go directly to the page content.
Visible focus indicators: Keyboard users can now clearly see where they are on all interactive elements, including buttons, links, form fields, date pickers, sliders, and modals.
Screen reader support: Icon buttons now have meaningful labels, decorative graphics are correctly hidden, alt text for background images and video previews has been added, and the currently selected page is announced in the navigation.
Accessible forms: Forms are a particularly sensitive area. Field labels are now programmatically linked to their input fields, required fields and error messages are correctly announced to screen readers, and multi-step forms reliably guide keyboard users through all steps.
Interactive widgets: Our selection elements, date pickers, sliders, rating elements, file uploads, and checkbox lists have been redesigned and are now operable with a keyboard and screen reader.
Modals and cookie banners: Modal dialogs maintain focus within the window, can be closed with the Escape key, and are announced to screen readers as dialogs. This also applies to the cookie banner, which is often the first interaction many visitors have with a website.
Respect for user preferences: Published websites now respect the "Reduce motion" system setting and allow zooming via pinch gestures on mobile devices, which is important for users with vestibular disorders or visual impairments.
Accessible Templates: Our design team has added a dedicated category of accessibility-optimized templates to the template gallery, featuring verified color contrasts, a logical heading structure, proper alt text, and a preconfigured page structure. The templates are available for the German and English markets and are ready to use right away.
Our Roadmap
For us, accessibility is not a one-time project, but an ongoing process. Here’s where we stand and where we’re headed:
July 2025 - Initial improvements: The first accessibility measures were released, including initial improvements to HTML structure, ARIA attributes, and the usability of key elements.
April 2026 - Comprehensive accessibility release: Systematic overhaul of the entire platform: semantic page structure, full keyboard accessibility, visible focus indicators, accessible forms and widgets, modals, cookie banners, and the release of accessible templates. Approximately 56 individual improvements were implemented.
Q3 2026 - Further improvements: Plans include an automatic contrast check in the builder, validation of the heading hierarchy, and expanded support for video captions and transcripts.
Q4 2026 - Expected completion of core adjustments: With this milestone, we aim to have fully covered the essential core areas of WCAG 2.1 Level AA from a technical standpoint, without any legal guarantee of full compliance. At the same time, we are evaluating an update to WCAG 2.2.
Known limitations
We’re open about what we haven’t achieved yet. The following areas are not yet fully covered and are on our roadmap:
An automatic contrast check in the Builder that alerts you during the design process if text and background colors do not meet WCAG requirements.
Validation of the heading hierarchy (e.g., warnings for skipped levels or multiple H1 elements per page).
Comprehensive subtitle and transcript support for video content.
An update to WCAG 2.2, which introduces additional criteria such as minimum touch area sizes and behavior for sticky headers.
If you encounter any of these or other limitations that hinder your work with Onepage, we’d love to hear from you, see the contact information below.
Recommendation for SMEs: Your own Accessibility Statement
If your business is subject to the BFSG, we recommend publishing your own accessibility statement on your website.
Such a statement is not only good practice, but can also help to:
Reduce legal risks during the transition phase
Demonstrate transparency to regulatory bodies
Clearly communicate your company's commitment to inclusion
Even if your site is not yet fully accessible, a public accessibility statement signals that you take the topic seriously and are actively working toward compliance.
Helpful tools:
📌 Please note: This recommendation does not constitute legal advice. Please consult your legal counsel or regulatory authority for guidance.
Tools for self-assessing your website
The following external tools can help you check the accessibility of your published website:
Instructions:
Contact and Feedback
We continuously strive to improve. If you have questions, feedback, or have discovered a barrier, please contact us at:
Accessibility is not a final state, but an ongoing process. Thank you for joining us on this journey.
💡Do you have any feedback about this article? Please let us know through our live chat or at support@onepage.io, so we may keep it up to date. Thank you! 🙂