Accessibility Statement
Last Updated: January 2025
1. Introduction
SSL Fruity AI GmbH & Co KG is committed to making its website accessibility-check.net accessible in accordance with the provisions of the European Accessibility Act (EAA) and Web Accessibility Directive (EU) 2016/2102.
This statement applies to the website: https://accessibility-check.net
Compliance Status: This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
2. Implemented Accessibility Measures
2.1 Semantic HTML
We use semantic HTML5 elements for better structuring:
<header>,<nav>,<main>,<section>,<footer>for logical document structure- Correct heading hierarchy (h1, h2, h3) without skipping levels
- Labeled form elements with
<label>tags
2.2 Keyboard Accessibility
The entire website is fully operable via keyboard:
- All interactive elements are reachable with the Tab key
- Visible focus indicators for all focusable elements
- Logical tab order through the page
- Enter and Space key support for buttons and links
2.3 Visual Design
We have ensured sufficient contrasts and readable font sizes:
- Color contrasts meet WCAG 2.1 AA standards (minimum 4.5:1 for normal text)
- Primary color: #2563eb (Blue) with sufficient contrast to white background
- Relative font sizes for scalability
- No information conveyed solely through color
2.4 Images and Media
All images are provided with alternative text:
- Descriptive
altattributes for informative images - Empty
altattributes for decorative images - SVG icons with descriptive labels or aria-labels
- Lucide Icons library for consistent, scalable icons
2.5 ARIA Support
Where necessary, we use ARIA attributes:
aria-labelfor button descriptionsaria-labelledbyandaria-describedbyfor form associations- Semantic HTML elements take precedence over ARIA roles
2.6 Responsive Design
The website is fully responsive and works on all devices:
- Mobile-first approach with adaptive layout
- Support for various screen sizes and resolutions
- Touch and mouse-friendly interaction elements
- Minimum touch target size of 44x44 pixels
2.7 Forms
All forms are designed to be accessible:
- Labeled input fields with
<label>tags - Clear error messages for validation errors
- Placeholder text as additional help (not as a replacement for labels)
- Logical tab order through forms
2.8 Navigation
The website navigation is clearly structured:
- Consistent navigation on all pages
- Multiple ways to access content (navigation, search, sitemap)
- Breadcrumb navigation where applicable
- Skip links to main content (planned)
3. Known Limitations
Despite our efforts, there are some areas where full accessibility has not yet been achieved:
3.1 Automated Tests
- Limitation: Our automated accessibility tests can only check approximately 30-40% of all WCAG criteria
- Impact: Some barriers may not be automatically detected
- Planned Action: Regular manual testing by accessibility experts
3.2 Third-Party Content
- Limitation: External libraries (e.g., Lucide Icons) may have their own accessibility issues
- Impact: Limited control over third-party component accessibility
- Action: Selection of accessible libraries and regular review
3.3 Dynamic Content
- Limitation: JavaScript-generated content may be difficult for screen readers to access
- Impact: Some dynamic updates may not be announced
- Planned Action: Implementation of ARIA live regions for dynamic updates
3.4 PDF Reports
- Limitation: Generated PDF reports may not be fully accessible
- Impact: Screen readers may have difficulty reading PDFs
- Planned Action: Offer HTML alternative for reports
4. Compatibility with Assistive Technologies
This website has been tested with the following technologies:
4.1 Screen Readers
- NVDA (Windows) - Basic compatibility
- JAWS (Windows) - In development
- VoiceOver (macOS/iOS) - Basic compatibility
4.2 Browsers
- Google Chrome (current version)
- Mozilla Firefox (current version)
- Microsoft Edge (current version)
- Safari (current version)
4.3 Operating Systems
- Windows 10/11
- macOS (current versions)
- iOS (current versions)
- Android (current versions)
5. Assessment Methodology
The accessibility assessment of this website was conducted through:
5.1 Self-Assessment
- Use of our own automated tools
- Manual testing with various browsers and devices
- Keyboard navigation testing
- Review of semantic HTML structure
5.2 Automated Testing
- axe-core for automated WCAG testing
- Lighthouse Accessibility Audit
- WAVE (Web Accessibility Evaluation Tool)
5.3 Planned External Audits
We plan to conduct regular external accessibility audits by certified experts.
6. Feedback and Contact
We are committed to continuously improving the accessibility of our website. If you encounter barriers or have suggestions for improvement, please contact us:
6.1 Feedback Channels
Email: info@fruitly.net
Phone: +43 650 37 50 530 (Austria) or +49 160 155 0555 (Germany)
Please describe the problem in as much detail as possible:
- Which page or feature is affected
- Which assistive technology you are using
- What exact problem you are experiencing
- Screenshots or screen recordings (if possible)
6.2 Response Time
We strive to respond to accessibility feedback within 5 business days and address reported issues as quickly as possible.
7. Enforcement Procedure
If you believe we have not adequately addressed your accessibility feedback, you can contact the following authorities:
7.1 Austrian Ombudsman
Austrian Ombudsman for Accessible Web Design
Bundessozialamt
Babenbergerstraße 5
1010 Vienna
Austria
Phone: +43 1 71100-0
Email: barrierefreiheit@bundessozialamt.gv.at
Website: https://www.bundessozialamt.gv.at/
7.2 EU Complaint Procedure
You also have the right to contact the competent national enforcement authority in your EU Member State.
8. Technical Specifications
8.1 Technologies Used
The accessibility of this website is based on the following technologies:
- HTML5 (semantic markup)
- CSS3 (responsive design, focus styles)
- JavaScript (progressive enhancement)
- EJS (server-side rendering)
- Lucide Icons (SVG icons)
8.2 Standards
This website follows these standards:
- Web Content Accessibility Guidelines (WCAG) 2.1 Level AA
- EN 301 549 v3.2.1 (2021-03) - European Accessibility Standard
- Section 508 (US Federal Standard)
9. Ongoing Improvements
9.1 Planned Measures
We continuously work on improving accessibility. Planned measures include:
- Q1 2025: Implementation of skip links
- Q1 2025: Improvement of ARIA live regions for dynamic content
- Q2 2025: External accessibility audit
- Q2 2025: HTML alternatives for PDF reports
- Q3 2025: Comprehensive screen reader testing
- Ongoing: Regular automated testing with every update
9.2 Training
Our development team regularly participates in accessibility training to ensure that new features are developed accessibly from the start.
10. Date of Creation and Review
Created: January 2025
Last Review: January 2025
Next Planned Review: July 2025
This statement is reviewed at least annually and updated when significant changes are made to the website.
11. Contact Information
SSL Fruity AI GmbH & Co KG
Inkustraße 1–7/Stiege 2/Haus C/1. OG/Top 2109
3400 Klosterneuburg
Austria
Management: Ferdinand Ledermüller
Company Registration Number: 661608d
Contact:
Germany: +49 160 155 0555
Austria: +43 650 37 50 530
Email: info@fruitly.net