Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
en:general:accessibility_desk_mobile_apps [2023/03/10 15:22] – [Documentations for mobile applications] thinderen:general:accessibility_desk_mobile_apps [2024/02/15 16:31] – [Documentations for desktop applications] thinder
Line 18: Line 18:
   * SUSE : https://www.suse.com/de-de/products/accessibility/   * SUSE : https://www.suse.com/de-de/products/accessibility/
  
 +<WRAP center round info 80%>
 +==== Related GWDG news articles ====
 +  - [[https://gwdg.de/about-us/gwdg-news/2023/GN_7-8-2023_www.pdf#page=15|GWDG News 7-8|23]] - Accessible Software Development with Microsoft Visual Studio 2022
 +<WRAP center round important 60%>
 +German only!
 +</WRAP>
 +
 +</WRAP>
 ===== Documentations for mobile applications===== ===== Documentations for mobile applications=====
  
Line 28: Line 36:
  
 </WRAP> </WRAP>
 +
 +====API and schema design examples====
 +  - use_underscores
 +  - useCamelCase
 +  - use-kebab-case
 +
 +==== 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)
 +
 +==== Abbreviations ====
 +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) ^
 +| pvtKey | privateKey |
 +
 +==== Additional services ====
 +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 ^
 +| dataContentType | DataContentType | DataContentTypeEntity |
 +
  
 ===== Check list ===== ===== Check list =====
Line 34: Line 63:
 |           | Bilingualism implemented | |           | Bilingualism implemented |
 |           | Usability implemented via mouse and keyboard | |           | Usability implemented via mouse and keyboard |
 +|           | API Naming |
 {{:en:general:checkliste_barrierefreie_desktop-_und_mobile-app_programmierung.pdf|The checklist to download }} {{:en:general:checkliste_barrierefreie_desktop-_und_mobile-app_programmierung.pdf|The checklist to download }}