Accessibility Information

‍I. General Service Description‍


The “AMBOSS Program” is an online knowledge and learning program for the healthcare sector that can be licensed on a subscription basis or for specific periods by consumers, businesses, and public institutions (e.g., universities). The digital learning concept is aimed in particular at medical students, residents, nurses, physicians and other healthcare professionals.

The AMBOSS Program is a cloud-based software that can be accessed via a browser or the AMBOSS apps. The AMBOSS Program includes the following features in particular:

  • Digital library
  • Question databases for exam preparation
  • Learning plans, learning recommendations
  • Evidence-based clinical decision support tools
  • Drug databases

You can reach us via mail, phone, or email:

AMBOSS SE
Torstr. 19, 10119 Berlin
+49-30-5770-2210
hello@amboss.com‍

‍

II. Using Our Services‍


With the AMBOSS Program, users can intuitively access medical learning and reference content via various entry points. The content is organized thematically, searchable, and follows didactic structures tailored to the needs of medical students, residents, nurses, physicians and other healthcare professionals. 

Once inside the platform, AMBOSS offers a structured and self-explanatory navigation through its various content areas. Users can access content directly or explore topics in greater depth via supporting materials and contextual links. Both theoretical knowledge and practical clinical applications are covered – from anatomy and pharmacology to complex disease patterns and treatment protocols.

Users can adapt their learning experience to their individual level of knowledge and professional phase. The content is context-sensitive and allows for seamless switching between study and clinician modes – both in browsers and on mobile devices.

Legal information such as Terms of Use and Privacy Policy is accessible at all times via the platform.

‍

III. Accessibility Requirements and Scope‍


Our accessibility obligations are based on Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services (European Accessibility Act, “EAA”), which requires compliance with harmonized accessibility standards across the European Union, and its national implementing legislation. The EEA references European standard EN 301 549 (version 3.2.1) as the official accessibility standard which defines the technical accessibility requirements for information and communication technology. This standard  aligns with the Web Content Accessibility Guidelines (WCAG) 2.1, conformance levels A and AA, which we use as a guide for implementing the accessibility requirements.

In addition, we meet accessibility requirements under applicable U.S. laws, including the Americans with Disabilities Act (ADA), Sections 504 and 508 of the Rehabilitation Act, and relevant state-level legislation. These also incorporate or reference WCAG 2.1 AA as the prevailing technical standard.

This accessibility statement refers to the following websites and applications:

According to the EAA, accessibility obligations apply to digital services in the context of electronic commerce, particularly those that enable a contractual or transactional interaction with end users (hereinafter with regard to AMBOSS “AMBOSS E-Commerce Communication”). This includes for example the AMBOSS shop, transactional emails and the AMBOSS Terms of Use. 

Based on this scope, the following (non-transactional) features of the AMBOSS Program are out of scope:

  • Informational and editorial content and/or features within all of our websites and applications without any transactional function;
  • Publicly accessible webpages on our DACH, US and International websites with informational and editorial content and/or features without any transactional function;
  • B2B-only offerings on our DACH, US and International websites not intended for transactions with end-users.

Nonetheless, AMBOSS is committed to progressively enhancing the accessibility of all digital content, wherever technically and practically feasible.‍

‍

IV. Compliance with Accessibility Requirements


AMBOSS is committed to making its services accessible to all users. We strive to meet the requirements of WCAG 2.1 (conformance level AA) to fulfill our legal requirements for the in-scope digital services listed above. This means we continuously assess and improve our services based on the principles of Perceivability, Operability, Understandability, and Robustness.

Our services have been tested with screen readers (e.g., NVDA), keyboard-only navigation, and automated tools (e.g., WAVE, axe DevTools), using Firefox and Chrome on both desktop and mobile devices. Accessibility testing will be systematically integrated into the software development lifecycle (SDLC) moving forward, in line with applicable legal requirements.‍

‍

1. Perceivability (Vision & Hearing)‍


We apply legible, high-contrast fonts with adequate spacing and structure across the platform. Users can utilize browser-native zoom and text-scaling features without functional loss in most areas. Core learning and reference content, as well as content related to user onboarding and navigation between features/pages, are designed to remain fully accessible under these conditions. All relevant images include alternative text. Visual cues (e.g., highlights and status messages) are supported by textual equivalents to ensure accessibility for users with hearing impairments.

However, limitations remain in specific legacy flows and platforms, such as:

  • Color contrast issues on some DACH, US and International websites elements (links on blue backgrounds, buttons, form placeholders) still require manual remediation.
  • iFrame accessibility challenges remain on embedded content on our DACH, US and International websites like demo booking pages and score predictors.
  • Purchase flows on the DACH web application including purchase related emails sometimes break layout or zoom functionality, impacting users on smaller or older devices, especially in landscape mode. Ongoing evaluations will determine whether these elements will be migrated to an updated, accessibility-compliant system.
  • The signup and login flows on the iOS Knowledge/Wissen Apps are only partially compliant with the requirement that animations respect system-level “Reduce Motion” settings.
  • The Side and Top Navigation on our DACH and International web application displays search bar background/hint text, sidebar icons, and username icon text that fail contrast requirements.
  • The User Profile Completion page on our DACH and International web application has content visibility issues with tooltips and hover states.
  • The Authentication Pages on our DACH and International web application show layout issues where the "Try AMBOSS for free" element gets cut off in landscape mode on mobile devices.
  • The paid trial paywall on our DACH web application does not display timeline content fully at 200% zoom in the second modal view, showing only subscription options and the submit button.‍

‍

2. Operability (Keyboard, Motor Skills)‍


All key features of the AMBOSS E-Commerce Communication are fully operable using only a keyboard. Focus indicators are clearly visible, the tab order is intuitive, and interactive elements meet minimum size and spacing requirements. No essential functions require drag-and-drop or other complex gestures. Platform navigation works reliably in both portrait and landscape orientations. Importantly, we do not impose time limits on platform usage.

Known exceptions currently under remediation include:

  • The Roadshow and Group Discount pages on our DACH, US and International websites exhibit limited keyboard and screen reader support due to legacy technical stacks and incomplete semantic markup.
  • The signup/login and paywall services on the iOS Knowledge/Wissen Apps are partially compliant with the requirement that all functionality is operable via a keyboard or alternate input method, and does not have keyboard traps.
  • The Paid Trial Paywall on our DACH and International web application requires improved keyboard focus management and has inconsistent focus indicators.
  • The Authentication Pages on our DACH and International web application have input fields that do not properly handle pointer cancellation events.
  • The User Profile Completion page on our DACH and International web application  traps focus on text input fields and password fields, and input fields lack proper pointer cancellation handling.‍

‍

3. Understandability‍


We prioritize clarity and simplicity in all user-facing content. Navigation elements use consistent and recognizable labels, and interface logic follows common web conventions. Sentences and paragraphs are kept short and structured to reduce cognitive load. This approach is consistently applied across the AMBOSS Program, including its apps, and has already improved formerly problematic areas (e.g., the updated login pages for institutional access as of June 2025).

Areas currently flagged for improvement include:

  • Our institutional access methods on our DACH and International web application  and access to those are currently under construction, and there are still some minor inconsistencies in navigation and content wording. These are currently under development and are expected to be compliant by end Q4 2025.
  • The Side and Top Navigation on our DACH and International web application shows navigation inconsistency across user types, with the search bar not consistently rendered for all user types.
  • The User Profile Completion on our DACH and International web application page has footer links with slightly different arrangements between pages at certain resolutions.‍

‍

4. Robustness & Security‍


AMBOSS builds on semantically valid HTML and incorporates ARIA attributes to improve compatibility with assistive technologies. We aim to ensure interoperability with a wide range of user agents, including screen readers and browser-based accessibility extensions.

In areas involving third-party integrations, such as Stripe-based payment forms and embedded tools like Calendly or YouTube videos, we design our interfaces to be accessible wherever possible. However, the accessibility performance of these external providers lies outside our direct control.

Crucially, no accessibility-related functionality on the AMBOSS Program (e.g., screen reader compatibility or zoom features) collects or processes additional personal data. Accessibility is implemented with full respect for user privacy and data minimization principles.

Improvements currently in progress include:

  • Enhancing ARIA attribute usage and validation to prevent misinterpretations by assistive technologies across all websites and applications.

  • Collaborating with external providers like Stripe to monitor and encourage accessibility compliance where feasible.

  • Strengthening semantic HTML structure across all websites to improve screen reader compatibility and navigation.

  • The signup and login flows on the iOS Knowledge/Wissen Apps are only partially compliant with the requirement that accessible names include the visible label text.

  • The Authentication Pages on our DACH and International web application do not properly communicate form errors and success messages to screen readers.

  • The User Profile Completion page on our DACH and International web application has missing aria-label attributes, though screen readers recognize labels through alternative means.
  • The paid trial paywall located on our DACH web application contains elements where the accessible name does not include the visible label text, leading to inconsistencies for users of screen readers.

    ‍

5. Non-Accessible Communication‍


While we aim to make all AMBOSS E-Commerce Communication accessible, some parts are under reconstruction and will be completely replaced or migrated and therefore may not fully meet WCAG 2.1 AA standards. This includes:

  • Older purchase flows including legacy purchase confirmation emails for users with accounts predating current standards. A technical and economic feasibility assessment is ongoing to determine next steps.
  • The paywall and signup/login services on the iOS & Android Qbank / Kreuzen Apps  are partially WCAG 2.1 A compliant. We have an internal plan in place to address them as part of our ongoing accessibility efforts.
  • International web application, in particular purchase flows and purchase related information access, has not yet been comprehensively assessed for accessibility compliance (single issues have been identified and stated above). This service is currently undergoing restructuring as part of an ongoing payment provider migration and therefore needs to be evaluated at a later stage.‍

6. Outlook


Accessibility at AMBOSS is not a one-off compliance checkbox, but an ongoing process. We are committed to iteratively improving our services so that all users – regardless of abilities or assistive tools – can engage with our services on equal footing.

Our roadmap includes:

  • Completion of the English-language checkout redesign to conform with WCAG 2.1 AA.
  • Replacement of legacy communication systems affecting subsets of users.
  • Migration of Blog, Roadshow, Group Discount pages and Event pages into the central CMS for improved accessibility, design consistency, and maintainability.
  • Continuous testing, user feedback inclusion, and design reviews to ensure accessibility by default in all new features.

    ‍

7. Date & Method‍


This statement was last updated on 27.06.2025.

Our websites and apps were assessed using:

‍

8. Feedback & Contact


If you experience any accessibility barriers, please contact us at: hello@amboss.com

In case of conflict you can contact the official arbitration board pursuant to § 34 BFSG:
https://www.schlichtungsstelle-bgg.de/Webs/SchliBGG/DE/AS/startseite/startseite-node.html