Overview
Accessibility at SAP refers to the possibility for everyone, especially people with disabilities, to access and use technology and information products. SAP ensures the accessibility of the products via the Product Standard Accessibility, enforced by the Innovation Cycle process, using various process steps to plan, develop, test, and report these quality features.
Accessible Typography
Framework Level Accessibility
Many fundamental accessibility features are built into the core design elements upfront and are available to app teams out of the box. This process ensures consistency across all products.
SAP UI Frameworks that provide accessibility out of the box:
- SAP UI5
- UI5 Web Components
- Fundamental UI
Application Level Accessibility
Many applications extend the standard functionalities of the UI elements or create new ones tailored to their needs. In such cases, application designers and developers need to consider accessibility standards.
See also:
Product Standards - Accessibility
Usage
The current default theme for SAP is called Morning Horizon. In addition, SAP provides alternative themes: Evening Horizon and the accessibility themes SAP High-Contrast Black (HCB) and SAP High-Contrast White (HCW). They are following the requirements of the international Web Content Accessibility Guidelines WCAG 2.2. SAP Horizon themes fulfill the requirements for minimum color contrast for their respective uses.
Recommended
- Support at least one default theme and one high-contrast theme.
- Provide a way to switch between themes via the Personalization option in the User Menu.
- Persist users' theme choice throughout the product.
Not Recommended
- Avoid providing the Evening Horizon theme without providing Morning Horizon.
- Avoid mixing light and dark themes, especially high-contrast ones.
See also:
Accessibility Testing Workflow
1. Contact Havva Mehfooz (havva.mehfooz@sap.com) from
for your test request
2. ATL will send you a test request form which has to be filled out with product related info.
3. Contact the development manager of the product to be tested and give them a heads-up.
(the ATL will create many bugs that will have a high impact on the responsible dev team)
4. Obtain a test system that can be accessed by the ATL
5. Create a test catalog, test plan, and test package in
6. Create “test case” workflow files (e.g. in Word) which describes what has to be tested.
7. Upload the test case file to GTP (Global Test Production)
8. Return the test request form to the ATL
9. After the testing you will receive a test report from the ATL
10. The test report must be converted to an which is possible with an easy click on an integrated button in the excel sheet.
11. ASD-File has to be sent to ACC-Team from Nicole Windmann with Oliver Keim (oliver.keim@sap.com)
as a contact.
12. ACC-Team will create the and provide the documents on the
self-service-page
Current Testing Status
BTP UX Deep-Dive Dashboard
Use the BTP UX Deep-Dive Dashboard to find out more about the of the products and services in BTP!
