Accessibility statement: who needs one and what to include

Last updated: 14 September 2026

At Welcoma, accessibility is not just a feature of our product — it is part of how we believe the web should work.

We want welcoma.app to be usable by as many people as possible, including people who use assistive technologies or who experience visual, hearing, motor, cognitive or other accessibility barriers.

We are committed to continuously improving the accessibility and usability of our website, products and digital experiences.

1. Our Accessibility Commitment

Welcoma is developed with accessibility in mind.

Our goal for welcoma.app is to follow the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA wherever reasonably possible.

WCAG provides internationally recognised recommendations for making web content more accessible to people with disabilities.

We treat accessibility as an ongoing process rather than a one-time project. As our website, dashboard and products evolve, we continue to review accessibility and address barriers that we identify or that are reported to us.

2. Current Conformance Status

Our goal is to achieve and maintain alignment with WCAG 2.2 Level AA.

However, we do not currently represent that every page, component or piece of content on welcoma.app has been independently certified as fully conforming to every WCAG 2.2 Level AA success criterion.

Some areas may still require improvement, particularly as:

• new features are introduced;
• existing functionality is updated;
• third-party services or embedded content change;
• new content is published; or
• accessibility requirements and technologies evolve

We actively work to identify and improve such areas.

We actively work to identify and improve such areas. If you encounter an accessibility barrier, we encourage you to tell us so that we can investigate it.

3. Measures We Take to Support Accessibility

We consider accessibility throughout the design, development and improvement of Welcoma.

Our accessibility efforts include areas such as:

• clear and consistent page structures;
• meaningful headings and content hierarchy;
• keyboard-accessible interactions where applicable;
• visible keyboard focus;
• appropriate colour and contrast considerations;
• readable typography;
• text resizing and display flexibility;
• meaningful labels for interactive controls;
• accessible forms and validation where possible;
• descriptive links and buttons;
• alternative text for meaningful images where appropriate;
• reduced reliance on colour alone to communicate information;
• responsive layouts for different screen sizes;
• compatibility considerations for assistive technologies;
• continuous accessibility review and improvement; and
• mechanisms for users to report accessibility problems

Accessibility is considered as part of our ongoing product and website development process.

4. Welcoma Accessibility Menu

welcoma.app may provide the Welcoma Accessibility Menu, which gives visitors additional options to adapt parts of the website experience to their individual needs and preferences. Depending on the available configuration, these options may include features relating to:

• text size and readability;
• text spacing;
• line height;
• contrast and colour adjustments;
• readable fonts;
• link and heading highlighting;
• focus visibility;
• keyboard navigation;
• reading assistance;
• animation controls;
• cursor and visual adjustments;
• accessibility profiles; and
• other usability preferences.

These tools are intended to provide additional user-controlled adjustments.

The accessibility menu is a supplementary usability tool. It does not replace accessible website design, semantic HTML, keyboard support, meaningful content structure, manual accessibility testing or remediation of accessibility issues in the underlying website.

5. Keyboard Accessibility

We aim to make important functionality on welcoma.app usable with a keyboard without requiring a mouse.

This includes working toward predictable:

• Tab navigation;
• focus order;
• focus indicators;
• links and buttons;
• form controls;
• menus;
• dialogs; and
• other interactive components.

If you encounter an element that cannot be reached or operated using a keyboard, pleasev report it to us.

6. Screen Readers and Assistive Technologies

We aim to develop welcoma.app using web technologies and structures that can work with commonly used assistive technologies.

Our accessibility approach may include:

• semantic HTML;
• accessible names and labels;
• appropriate heading structures;
•  form labels;
• alternative text;
• keyboard-operable controls; and
• WAI-ARIA where appropriate.

Because combinations of browsers, operating systems and assistive technologies can behave differently, we cannot guarantee identical operation in every possible technical environment.

If you experience a problem using welcoma.app with a screen reader or another assistive technology, please contact us and provide information about the technology and browser you are using where possible.

7. Visual Accessibility and Readability

We aim to make the visual presentation of welcoma.app easier to perceive and understand.

Our approach includes consideration of:

• text and background contrast;
• readable font sizes;
• scalable text;
• clear visual hierarchy;
• visible focus states;
• distinguishable interactive controls;
• understandable layouts; and
• responsive presentation across different screen sizes.

Visitors may also use available Welcoma accessibility controls, browser settings or operating-system accessibility settings to further personalise their experience.

8. Motion and Animation

Where animations, transitions or moving elements are used, we aim to avoid unnecessary movement that may interfere with accessibility.

Where technically appropriate, users may also be able to reduce or stop certain animations through accessibility controls or their browser and operating-system preferences.

We continue to review motion-related functionality as the website develops.

9. Language and Understandable Content

We aim to make Welcoma content clear, structured and understandable.Where appropriate, we use:

• descriptive headings;
• short sections;
• lists;
• clear labels;
• understandable navigation;
• descriptive calls to action; and
• plain-language explanations of technical accessibility concepts.

Welcoma may also provide translation and plain-language functionality as part of certain products or features.

Automated translation or AI-generated simplified content may not always be perfect and should not be considered a substitute for professionally reviewed accessible content.

10. Compatibility

welcoma.app is designed with modern web technologies and is intended to work with current versions of commonly used web browsers.

These may include:

• Google Chrome;
• Mozilla Firefox;
• Microsoft Edge; and
• Apple Safari.

We also aim to support the use of keyboard navigation and common assistive technologies.

Accessibility may be reduced when using:

• significantly outdated browsers;
• unsupported operating systems;
• disabled JavaScript where functionality depends on it;
• browser extensions that substantially alter page behaviour; or
• unusual combinations of assistive technologies and browsers.

If you discover a compatibility problem, please let us know.

11. Technical Specifications

The accessibility of welcoma.app relies on standard web technologies that may include:

• HTML;
• CSS;
• JavaScript;
• SVG; and
• WAI-ARIA where appropriate.

These technologies are used to provide the structure, presentation and interactive functionality of the website.

We aim to use native and semantic web technologies wherever practical rather than relying unnecessarily on custom accessibility behaviour.

12. Accessibility of the Welcoma Customer Dashboard

Our accessibility efforts are not limited to the public welcoma.app website.

We also aim to continuously improve accessibility within customer-facing Welcoma functionality, including areas such as:

• account management;
• website management;
• accessibility settings;
• licence management;
• reports;
• scanning functionality;
• accessibility statement tools; and
• other dashboard features.

Because the Welcoma platform continues to evolve, some newer or more complex application functionality may present accessibility challenges that are still being addressed.

We welcome feedback about accessibility barriers within the Welcoma dashboard as well as on our public website.

13. Third-Party Content and Services

Some functionality on welcoma.app may depend on or link to third-party services.

Although we aim to select and implement third-party services carefully, we do not always control the accessibility of:

• external websites;
• embedded third-party content;
• payment interfaces;
• external documents;
• third-party applications; or
• services operated independently from Welcoma.

If a third-party component creates an accessibility barrier while you are using Welcoma, please contact us. Where reasonably possible, we will investigate the issue and consider an accessible alternative or improvement.

14. Known and Potential Limitations

Despite our efforts to make welcoma.app accessible, some accessibility limitations may remain.

These may occur particularly in:

• newly released features;
• complex interactive components;
• third-party integrations;
• legacy content;
• documents or media;
• automatically generated content; or
• combinations of browsers and assistive technologies that we have not yet evaluated.

We do not want accessibility problems to remain unnoticed.

If you encounter a barrier that prevents or makes it difficult for you to access information, complete an action or use a Welcoma feature, please contact us.

We will review reported issues and, where reasonably possible, work toward an appropriate solution.

15. Accessibility Is an Ongoing Process

Digital accessibility requires continuous attention.

Websites and software change, new content is published, technologies evolve and accessibility standards continue to develop.

For this reason, we regularly review and improve Welcoma rather than treating accessibility as a one-time implementation.

Our ongoing work may include:

• reviewing new functionality for accessibility;
• identifying accessibility barriers;
• improving keyboard interaction;
• improving semantic structure;
• improving forms and controls;
• reviewing colour and visual presentation;
• improving assistive-technology support;
• addressing reported accessibility issues; and
• updating our accessibility practices as standards and technologies evolve.

16. Automated Tools Are Not Enough

As a company building accessibility technology, we believe it is important to be clear about the limitations of automated accessibility tools.

Automated tools can help identify many technical accessibility issues, but they cannot reliably identify or resolve every accessibility barrier.

Meaningful accessibility may also require:

• manual evaluation;
• keyboard testing;
• screen-reader testing;
• content review;
• design review;
• human judgement; and
• testing by people using different assistive technologies.

For this reason, Welcoma does not consider the presence of an accessibility widget or the result of an automated scan alone to be proof that a website is fully accessible or legally compliant.

17. Welcoma Products on Customer Websites

This Accessibility Statement applies specifically to welcoma.app and Welcoma’s own digital services.

Customers may install or use Welcoma products on independently operated websites.

Welcoma does not control the complete design, source code, content, third-party plugins or ongoing changes made to those customer websites.

The availability of the Welcoma accessibility widget on a third-party website therefore does not, by itself, mean that the entire website conforms to WCAG or any particular accessibility law.

Each website owner remains responsible for assessing and improving the accessibility of their own website.

18. Accessibility Feedback

We welcome feedback about the accessibility of Welcoma.

If you:

• encounter an accessibility barrier;
• cannot access particular information;
• cannot operate a feature using a keyboard;
• experience a problem with a screen reader;
• find content difficult to understand;
• require information in an alternative accessible format; or
• have a suggestion for improving accessibility,

please contact us.

When reporting an accessibility issue, it is helpful if you can include:

• the page or URL where the problem occurred;
• a short description of the issue;
• the browser you were using;
• your device or operating system, where relevant; and
• the assistive technology you were using, if applicable.

You are not required to provide information about a disability in order to report an accessibility issue.

19. Contact Us About Accessibility

Accessibility questions, feedback and requests for assistance can be sent to:

webAufstieg GmbH
Welcoma Accessibility Team
Anton-Huber-Straße 20
73430 Aalen
Germany

Email: info@welcoma.app
Phone: +49 7361 6339046

We aim to review accessibility feedback as promptly as reasonably possible and to investigate reported barriers appropriately.

If immediate access to specific information or functionality is difficult because of an accessibility issue, please tell us what you are trying to access so that we can consider an alternative way to assist you.

20. Assessment and Review

Welcoma’s accessibility is reviewed as part of our ongoing website and product development.

Our accessibility approach may include a combination of:

• internal review;
• automated accessibility testing;
• manual testing;
• keyboard testing;
• review of interface components; and
• feedback received from users.

An automated test alone is not treated as a complete accessibility evaluation.

Unless expressly stated otherwise, this Accessibility Statement should not be interpreted as an independent third-party certification of full WCAG conformance.

21. Standards and Legal Frameworks

Our accessibility work is primarily guided by WCAG 2.2 Level AA.

Depending on the service, customer or jurisdiction, other accessibility frameworks and laws may also be relevant, including:

• EN 301 549;
• the European Accessibility Act (EAA);
• the German Barrierefreiheitsstärkungsgesetz (BFSG);
• the Americans with Disabilities Act (ADA);
• Section 508; and
• applicable UK accessibility requirements.

References to these standards and laws describe frameworks that may be relevant to digital accessibility.

They should not be interpreted as a statement that welcoma.app has been formally certified under every listed law or standard.

22. Changes to This Accessibility Statement

We may update this Accessibility Statement as:

• welcoma.app changes;
• new Welcoma functionality is introduced;
• accessibility improvements are implemented;
• accessibility standards evolve; or
• our accessibility evaluation identifies new information.

The current version will be published on welcoma.app together with the latest revision date.

23. Our Commitment

We believe accessibility should help people use the web with greater independence, choice and confidence.

Our goal is not simply to provide an accessibility menu. It is to continue improving the underlying accessibility, usability and inclusiveness of Welcoma itself while building tools that help other website owners do the same.

If something on Welcoma prevents you from accessing information or completing an action, we want to know about it.

Accessibility feedback:
info@welcoma.app