Accessibility Statement
Last Updated: January 2025
Last Reviewed: January 2025
Our Commitment to Accessibility
OnePage Builder is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards.
This accessibility statement applies to the OnePage Builder platform available at onepagebuilder.com and all websites created using our platform.
Conformance Status
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
✓ OnePage Builder is partially conformant with WCAG 2.1 Level AA
"Partially conformant" means that some parts of the content do not fully conform to the accessibility standard.
Standards and Legislation
OnePage Builder aims to comply with the following standards and legislation:
- Swedish Law: Lag (2018:1937) om tillgänglighet till digital offentlig service (Law on accessibility to digital public services)
- EU Directive: Directive (EU) 2016/2102 on the accessibility of websites and mobile applications
- EN 301 549: European Standard for ICT Accessibility
- WCAG 2.1 Level AA: Web Content Accessibility Guidelines
Accessibility Features
OnePage Builder includes the following accessibility features:
♿ WCAG AA Compliance Tools
Built-in contrast checker ensures all text meets the 4.5:1 minimum ratio. The system prevents saving designs that don't meet accessibility standards.
⌨️ Keyboard Navigation
Full keyboard support with Tab navigation, Enter/Space activation, and Escape to close modals. Visible focus indicators on all interactive elements.
📢 Screen Reader Support
Semantic HTML, ARIA labels, proper heading hierarchy, and descriptive link text ensure compatibility with assistive technologies.
🎨 Visual Accessibility
High contrast UI, readable fonts (minimum 16px), clear focus indicators, and no reliance on color alone to convey information.
🌐 Language Support
Proper lang attributes, consistent terminology, and clear, simple language throughout the interface.
⏸️ User Control
No auto-playing content, no time limits on interactions, and respect for prefers-reduced-motion preferences.
Known Limitations and Issues
Despite our best efforts to ensure accessibility, there may be some limitations. Below is a description of known issues:
Color Picker Interface
Issue: The visual color picker may be difficult to use with keyboard only.
Workaround: Users can enter hex color codes directly using the text input field.
Status: Planned for improvement in future update.
Preview Iframe
Issue: The live preview iframe has limited keyboard navigation within the preview.
Workaround: All editing functionality is available in the main interface. The preview is for visual reference only.
Status: Under review.
Third-Party Services
Issue: Some third-party integrations (Stripe, GitHub) may have their own accessibility limitations.
Workaround: We work with providers who prioritize accessibility and provide alternative methods when possible.
Status: Ongoing monitoring.
Technical Specifications
Accessibility of OnePage Builder relies on the following technologies:
- HTML5 - Semantic markup
- CSS3 - Visual presentation
- JavaScript - Interactive functionality
- ARIA - Enhanced accessibility attributes
- Vue.js 3 - Framework with accessibility features
These technologies are relied upon for conformance with the accessibility standards used.
Assessment Approach
OnePage Builder assessed the accessibility of this website by the following approaches:
- Self-evaluation: Internal testing with accessibility tools and screen readers
- Automated testing: Using tools like WAVE, axe DevTools, and Lighthouse
- Manual testing: Keyboard-only navigation and screen reader testing
- User testing: Feedback from users with disabilities
Feedback and Contact Information
We welcome your feedback on the accessibility of OnePage Builder. Please let us know if you encounter accessibility barriers:
💬 GitHub Issues
Public issue tracker for transparency and community input.
When reporting accessibility issues, please include:
- The page or feature where you encountered the issue
- A description of the problem
- Your operating system and browser
- Any assistive technologies you use
- Steps to reproduce the issue
Enforcement Procedure
Under Swedish law (Lag 2018:1937), if you are not satisfied with how we respond to your accessibility feedback, you can report it to:
DIGG is the Swedish Agency for Digital Government responsible for monitoring compliance with accessibility legislation.
Websites Created With Our Platform
All websites created using OnePage Builder benefit from our accessibility features:
- Automatic WCAG AA contrast validation during design
- Semantic HTML structure in exported code
- Proper heading hierarchy
- Accessible forms with proper labels
- Keyboard-navigable elements
- Screen reader-friendly markup
Note: Content creators are responsible for:
- Providing meaningful alt text for images
- Writing clear, understandable content
- Using descriptive link text
- Maintaining logical content structure
- Testing their own websites for accessibility
Continuous Improvement
We are committed to continuous improvement of accessibility. Our roadmap includes:
- Q1 2025: Enhanced keyboard navigation in color picker
- Q2 2025: Comprehensive accessibility audit by external experts
- Q3 2025: User testing with people with disabilities
- Ongoing: Regular automated accessibility testing in CI/CD pipeline
- Ongoing: Staff training on accessibility best practices
Formal Complaints
If you wish to make a formal complaint about accessibility, please contact us at accessibility@onepageai.builder with:
- Your name and contact information
- Description of the accessibility issue
- The page or feature affected
- Date and time you encountered the issue
- Impact on your ability to use the service
We will investigate all formal complaints and provide a written response within 3 weeks.
Additional Resources
Learn more about web accessibility:
Help Us Improve
Your feedback is essential to improving accessibility. If you encounter any barriers, please let us know.
Report Accessibility IssueStatement Approval
This accessibility statement was created on January 2025 and last reviewed on January 2025.
This statement will be reviewed and updated at least annually and whenever significant changes are made to the website.