Accessibility Guidelines
The Web Content Accessibility Guidelines (WCAG) are recommendations and guidelines provided by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI). The goal of these are to make web applications accessible to people with disabilities. The latest standard is WCAG 2.2 released on 05 October 2023, which also covers most requirements from the Section 508 and ADA guidelines. imc AG tries to meet the accessibility requirements with the WCAG (Web Content Accessibility Guidelines) 2.1
The WCAG 2.1 guidelines consists of 4 principles and 13 guidelines:
Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
Guideline 1.1 Text Alternatives
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Guideline 1.2 Time-based Media
Provide alternatives for time-based media.
Guideline 1.3 Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Guideline 1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
Operable - User interface components and navigation must be operable.
Guideline 2.1 Keyboard Accessible
Make all functionality available from a keyboard.
Guideline 2.2 Enough Time
Provide users enough time to read and use content.
Guideline 2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
Guideline 2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
Guideline 2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
Understandable - Information and the operation of user interface must be understandable.
Guideline 3.1 Readable
Make text content readable and understandable.
Guideline 3.2 Predictable
Make Web pages appear and operate in predictable ways.
Guideline 3.3 Input Assistance
Help users avoid and correct mistakes.
Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies.
Accessibility in the imc Learning Suite
imc Learning Suite supports to setup a WCAG 2.1 AA compliant learning environment.
Accessibility as a Process
The imc Learning Suite has been built to be WCAG 2.1 AA compliant wherever possible. Currently, a number of elements are compliant, and our focus and commitment is to continuously improve and add features to ensure the learner experience is more accessible. We welcome feedback and suggestions for accessibility improvements.
Accessibility by Default
Accessibility is embedded into our Software Development Life Cycle (SDLC) to ensure compliance with WCAG standards.
This includes:
Design Reviews: Accessibility requirements are evaluated early in the design phase, ensuring compliance with WCAG 2.1 standards. This includes reviewing UI/UX components for keyboard navigation, color contrast, and screen reader compatibility.
Development & Testing Phases: Developers follow best practices for accessibility, incorporating automated and manual accessibility testing to identify and resolve issues.
Quality Gates & Exit Criteria: Accessibility compliance is a key criterion in our quality assurance process before release. Features must meet minimum accessibility standards before progressing to deployment.
Accessibility Testing Process
Sprint Integration: Accessibility considerations are included within the standard development specifications, ensuring new features adhere to accessibility standards from the start. Accessibility is tested manually using the Wave browser plugin by both developers and dedicated QA personnel during sprint development. Test automation is also applied where feasible.
QA Phase: During the regression testing phase before delivery, the Wave browser plugin is used in supported browsers (Chrome, Safari, Firefox, Edge). Additionally, the Axe plugin is utilized for automated testing in both regression and sprint development.
Fixing Issues:
Sprint and IP QA: Issues identified within the sprint cycle are addressed as part of the development process.
External Testing: If external audits identify issues, they may be addressed based on business impact and priority.
Customer-Based Testing: Findings from customer audits are handled through CB tickets and scheduled in upcoming patches.
By integrating accessibility into each stage of our development lifecycle, we ensure that compliance with WCAG 2.1 AA is not just a goal but a continuous and evolving process.
Accessibility of Content
Accessibility of a platform can only be achieved if both the system and the content are accessible!
The accessibility of the content (e.g. courses, WBTs, files) is dependant on the content provider. Content that is created by customers or external parties needs to be ensured that either their content itself fulfils the accessibility guidelines or that they provide additional support such as captions or alternative, accessible content. The imc Learning Suite supports content creators by providing features for adding captions, transcripts and alternative content for multimedia files.
As well as the provisions within the imc Learning Suite, imc can also provide services for accessible content creation.
Accessibility Scope (White list)
The focus of imc is to provide an accessible learning experience. Therefore we ensure accessibility can be reached in the areas of the imc Learning Suite which are core for the learner's experience. This white list is valid for imc Learning Suite 14.10.
We can assure that the following areas are compliant with accessibility guidelines:
Navigation
Common areas
Login
Registration
Profile (View/Edit)
Personal data
Change password
Delete profile
Imprint
Terms of use
Privacy policy
Inbox
Enrollment form
Catalogue
Course syllabus with the configurable layout
Certificates of completion (PDF)
Custom course room
Individual course syllabus
Media pages for
File
Link
Multimedia file
WBT (HTML/AICC/SCORM/"xAPI/Tin Can")
Event
Activity
External LTI tools (1.1/1.3)
3rd party content
My staff
Mange staff enrolment
Test and feedback with the following question types
Free text
Yes/no
Multiple choice (1 of n/n of n)
Matrix (single and multi selection)
Internal Dashboard with the following panels (new Design):
Course panel
Bookshelf panel
Recommended learning
Top contents
Mandatory courses
Current courses
Pending enrolments
Classification page
My experience area
Training calendar
Channels
Channels Manager
Channels Learner
Channel Contents
Accessibility Limitations
Screen reader support is limited to JAWS 2019 in Chrome
WCAG 2.1 AA can only be achieved, if the agreed customer design applies with the contrast and size requirements of WCAG 2.1 AA
Mobile App e.g. certain icons are not read, limitations related to tests completion by learner
To ensure WCAG 2.1 guideline Enough Time (2.2), timing in tests needs to be disabled
There are limitations regarding advanced configurations in the areas white listed above
For features not on the white list, accessibility cannot be ensured. The administrative frontend is not compliant to accessible standards.
Role and Responsibilities
In case a customer detects accessibility issues for the standard product, we have the following process:
QA checks (with the help of dev and design) the provided customer document in a LMSILS ticket concerning our predefined accessability scope (white list)
For agreed accessibility issues, internal bugs are created and will be planned in to be fixed.
Feedback will be provided viy the DESK ticket.
Design considers and reviews the accessibility coverage for new implementations
Key Accessibility Regulations and Standards
As a software company based in Germany with international clients, IMC needs to comply with several accessibility regulations and standards. These ensure that our products are usable by people with disabilities. Below are the key regulations:
European Union
EU Web Accessibility Directive (Directive (EU) 2016/2102)
This directive applies to public sector websites and mobile apps, requiring them to meet accessibility standards. The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA are the benchmark.
European Accessibility Act (Directive (EU) 2019/882)
Expands accessibility requirements to cover private sector services and products like software, e-commerce, and electronic devices. This law will become fully enforceable by June 2025.
WCAG 2.1 (Web Content Accessibility Guidelines)
While not legally binding on its own, WCAG 2.1 is widely adopted across the EU, and it is the basis for many local laws and directives, including the ones above. Aim for Level AA compliance.
Germany
Barrierefreie-Informationstechnik-Verordnung (BITV 2.0)
The German equivalent of the EU Web Accessibility Directive, requiring public sector websites and apps to be accessible. It is based on WCAG 2.1 Level AA standards.
Behindertengleichstellungsgesetz (BGG)
A broader law promoting equality for people with disabilities, indirectly impacting digital accessibility requirements.
United States
Americans with Disabilities Act (ADA)
Although not a law specific to websites, courts have interpreted the ADA to apply to websites and digital platforms. WCAG 2.1 Level AA is generally seen as the benchmark to meet ADA compliance.
Section 508 of the Rehabilitation Act
Applies to federal government websites and contractors. Requires conformance with WCAG 2.1 Level AA.
Other International Standards
Canada: Accessibility for Ontarians with Disabilities Act (AODA)
Requires WCAG 2.1 AA compliance for public websites of companies and organizations operating in Ontario.
Australia: Disability Discrimination Act (DDA)
Requires digital services to be accessible, with WCAG 2.1 AA being the de facto standard.
Best Practice for International Clients:
Since IMC serves clients worldwide, it's safest to ensure that our products comply with WCAG 2.1 Level AA standards. This standard is widely accepted and serves as the basis for many accessibility laws around the globe.