Skip to main content

Accessibility Roadmap for coapp

This roadmap provides a transparent overview of the current accessibility status of the coapp platform and the measures planned for further improvement.

Updated this week

This roadmap provides a transparent overview of the current accessibility status of the coapp platform and the measures planned for further improvement.

It is intended to support customers in their own accessibility documentation and compliance processes (e.g. under the German Accessibility Strengthening Act – BFSG). This document does not constitute a certification or confirmation of legal compliance. It outlines the current implementation status and the direction of ongoing development.

For the official accessibility statement, please refer to:

Current Accessibility Status

coapp is continuously working toward alignment with the Web Content Accessibility Guidelines (WCAG) 2.1, conformance level AA.

Many central features of the platform are already accessible. However, accessibility is not yet fully implemented across all areas.

Known limitations currently include:

  • Partially insufficient visual representation of keyboard focus

  • Color contrasts that are not consistently compliant for individual elements (e.g. icons, badges)

  • Ongoing optimization of semantic labeling and ARIA roles

Semantic structuring and ARIA roles have largely been implemented but are being continuously refined.

We regularly perform automated assessments using Google Lighthouse for orientation purposes. Tested page areas currently achieve an accessibility score between approximately 65% and 75%. These values reflect an intermediate level of implementation and are gradually being improved.

Accessibility is an ongoing development process. Full WCAG 2.1 AA compliance cannot currently be confirmed.

How You Can Improve Accessibility Today

Customers can implement additional accessibility improvements within their own coapp instance.

coapp provides:

Through Custom JavaScript, operators may integrate tools such as accessibility overlays or additional assistive scripts.

Planned Enhancements (Next 12 Months)

Within the next 12 months, the following improvements are planned, subject to prioritization and product development capacity:

  • Improved and more consistent keyboard focus indicators

  • Expanded design customization options

    • Ability to define and adjust the complete color palette

    • Full color contrast control

    • Adjustable font sizes

  • Further optimization of semantic markup and ARIA implementation

coapp maintains a publicly accessible product development roadmap.

Accessibility-related improvements and initiatives can be reviewed here:

These measures are intended to progressively improve accessibility. Timelines may be adjusted depending on technical and strategic prioritization.

Ongoing Accessibility Governance

Accessibility is being embedded into our development workflow.

Ongoing measures include:

  • Automated review and assessment of frontend code changes

  • Regular automated accessibility testing

  • Continuous optimization of semantic structure and UI components

Accessibility considerations are incorporated into product development processes to gradually improve conformance levels over time.

Shared Responsibility

Accessibility compliance depends on both the technical platform and its individual configuration and usage.

coapp provides the technical foundation and continues to improve platform accessibility. However, operators are responsible for:

  • Creating accessible content

  • Ensuring accessible uploaded materials (e.g. PDFs, media)

  • Selecting accessible color schemes and branding elements

  • Maintaining their own accessibility statement where legally required

  • Assessing whether their specific implementation meets applicable legal requirements

Legal compliance (e.g. under the BFSG or other regulations) cannot be guaranteed solely by using the coapp platform. It depends on the individual configuration, content and operational setup of each customer instance.

Did this answer your question?