This document discusses accessibility considerations and best practices for developing enterprise software at scale. It outlines the centralized approach SAP takes to ensure accessibility across applications developed using its platforms and frameworks. Key responsibilities of application developers are to associate labels with fields and use meaningful titles and tooltips, while the frameworks handle many accessibility functions like keyboard navigation and support for assistive technologies.
Uneak White's Personal Brand Exploration Presentation
Accessibility Enterprise
1. Stefan Schnabel SAP User Experience – Accessibility Accessibility at large scale for Enterprise Software - Architecture and Constraints
2.
3.
4.
5.
6.
7. Centralized approach / what to do where Application Logic UI Definition UI Programming UI Rendering Use semantic colors instead of hard-coded colors Provide meaningful information for labels, column headers and row headers UI templates and generators for navigation and layout Translate semantic colors into real colors (e.g. for traffic lights symbols, “critical” meanings and warnings) Link fields and corresponding labels Do not misuse UI elements Keyboard enablement Acknowledge desktop settings for colors and contrast (*) Compatibility with screen reader / magnifier Scaling / Font selection (*) hard-coded colors defined in application logic can not be overwritten by desktop settings Making use of the centralized capabilities of the UI Definition / Programming and Rendering, application developers can concentrate on limited set of rules and constraints
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Editor's Notes
Software Applications and Operating Systems (1194.21) Most of the specifications for software pertain to usability for people with vision impairments. For example, one provision requires alternative keyboard navigation, which is essential for people with vision impairments who cannot rely on pointing devices, such as a mouse. Other provisions address animated displays, color and contrast settings, flash rate, and electronic forms, among others. Web-based Intranet and Internet Information and Applications (1194.22) The criteria for web-based technology and information are based on access guidelines developed by the Web Accessibility Initiative of the World Wide Web Consortium. Many of these provisions ensure access for people with vision impairments who rely on various assistive products to access computer-based information, such as screen readers, which translate what's on a computer screen into automated audible output, and refreshable Braille displays. Certain conventions, such as verbal tags or identification of graphics and format devices, like frames, are necessary so that these devices can "read" them for the user in a sensible way. The standards do not prohibit the use of web site graphics or animation. Instead, the standards aim to ensure that such information is also available in an accessible format. Generally, this means use of text labels or descriptors for graphics and certain format elements. (HTML code already provides an "Alt Text" tag for graphics which can serve as a verbal descriptor for graphics). This section also addresses the usability of multimedia presentations, image maps, style sheets, scripting languages, applets and plug-ins, and electronic forms.
![Enterprise Software is different ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)