Accessibility Statement
Last reviewed: September 28, 2026
The Short Version
- We want everyone to be able to use STRUC-ID, including people with disabilities and older individuals.
- Our objective is full compliance with international WCAG 2.2 Level AA standards.
- The website is currently partly accessible. Known gaps and mitigation efforts are detailed below.
- If you encounter an accessibility barrier, contact us for immediate alternative assistance.
Contents
1. Our commitment
- Structural safety concerns everyone who resides in or manages a building; therefore, our platform must be accessible to all users.
- We follow the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and European standard EN 301 549.
- We support the objectives of the German Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG). As a university spin-off micro-enterprise, STRUC-ID voluntarily commits to meeting these digital accessibility standards.
2. How accessible the website is
This website is partly compliant with WCAG 2.2 level AA. While the core user journeys are accessible, certain components currently fall short of full compliance. A breakdown of active remedial work is detailed in Section 4.
3. What already works
4. Known problems
We are actively rectifying the following items with a target completion date of September 28, 2027:
| Known Barrier | Impacted Audience | Planned Remediation |
|---|---|---|
| Mobile navigation dynamic menu button missing on small screens. | Mobile users, severe page zoom users. | Implementing accessible screen-reader verified ARIA toggle overlay. |
| Diagrams and building figures missing concise text descriptions. | Screen reader users. | Adding descriptive alternative text and aria-hidden tags on decorative SVGs. |
| Low contrast ratio on minor footer elements and secondary captions. | Low-vision users. | Adjusting color tokens to meet minimum 4.5:1 ratio. |
| Interactive dynamic report buttons lack live-region screen reader alerts. | Screen reader users. | Integrating aria-live status regions for live updates. |
| Exported assessment PDF reports are not fully tagged. | Screen reader users. | Generating tagged accessible PDFs along with direct HTML web report views. |
| Card hover animations do not strictly adhere to motion preferences. | Users sensitive to motion. | Enforcing system prefers-reduced-motion CSS directives globally. |
5. Other ways to get help
If an online feature presents an barrier, we provide alternative service channels at no additional charge:
- Submit building addresses via email to receive manual safety evaluation reports.
- Request structural reports in alternative formats (large print, plain text, accessible digital documents).
- Schedule a phone or video consultation with our engineering team for verbal report explanation.
6. Tell us about a problem
We welcome feedback regarding accessibility issues. Please contact our team with details of the difficulty encountered:
We acknowledge accessibility inquiries within 5 working days and aim to resolve reported barriers within 4 weeks.
7. Dispute & enforcement authorities
If our response to your accessibility concern is unsatisfactory, you may escalate to official German market monitoring and accessibility bodies:
Marktüberwachungsstelle der Länder (MLBF)
Competent authority monitoring digital accessibility of products and services in Germany.
www.mlbf-barrierefrei.deBundesfachstelle Barrierefreiheit
Federal body offering guidance and advice regarding accessibility rights and implementation.
www.bundesfachstelle-barrierefreiheit.de8. About this statement
- This statement was prepared and finalized on September 28, 2026.
- It is derived from self-assessment evaluations conducted against WCAG 2.2 Level AA guidelines.
- This policy undergoes mandatory annual review and immediate re-assessment following major platform release cycles.