Table of Contents
Checklist accessible desktop and mobile app programming
When programming desktop and mobile apps, the recommendations of the manufacturing software company should be carefully read, observed and implemented in the design, planning, programming and testing. The following links are the entry points to the documentation of large software companies on this topic. Every programmer or group of programmers must deal with this topic and activate accessibility features especially for the developed application. This applies to development projects and contracts that are outsourced.
Not considering accessibility in published apps is not an option!
Documentations for desktop applications
Documentations for mobile applications
The golden rule is: Use word separators
API and schema design examples
Examples of IDs and similar entities
- use.dot.separators (often with reverse DNS prefixes)
- use/path/separators (often with URIs)
- use-hyphen-separators (often with GUIDs and the like)
Another common challenge is the use of shortcuts. While a user interacting with your API may recognize your abbreviations from context, a screen reader may not be able to do so, especially if your abbreviation is not common.
|Abbreviated (unfavorable)||Not abbreviated (correct)|
An added benefit is that code generators can more easily produce idiomatic terms that conform to case-sensitive conventions in the target language/platform.
|JSON||Dotnet||Dotnet with additional suffix|
|Interfaces built-in and tested|
|Usability implemented via mouse and keyboard|