Cursor Guideline

1 Guideline

By now there isn't any guideline for the behaviour of the cursor, especially when opening a view.
Example: In "Create" screens, the cursor is not in the first (or only) field you have to complete, i.e., the "Title" field.

There might also be other situations in which the behaviour of the cursor could be optimized and/or should be streamlined.
Therefore, I suggest to introduce a new "Cursor Guideline".
 
 
 

2 Status

• Effective from release: { not approved yet | x.y }
• Approved by Jour Fixe at: { link to Jour Fixe agenda }
  
• Implementation status: { implemented completely | partly implemented | needs implementation }
• Funding for streamlining existing features: { name of organisation }
• Implementation of guideline: { all developers | name of responsible developer }

3 Components that are not compliant with the Guideline

• "Create" screens: Cursor is not automatically set in the "Title" field.
• "After create" screens where a first sub-element of an object is to be created, e.g. in Forums: Cursor is not automatically set in the "Title" field.
• Main header bar: Not every screen element can be accessed by the "Tab" key, e.g., "Conversations" and "Background Tasks".
• Top actions: Not every screen element can be accessed by the "Tab" key, e.g., the  "bell" icon for starting news notifications in courses.
• Tab bars: Not every screen elements is highlighted when the cursor is on it, e.g., the "..." at the end of the tab bar when the screen is too small to show all the tabs.
• Forms: Not every screen elements is highlighted when the cursor is on it, e.g., "+" and "-" buttons for adding lines (e.g., when uploading attachments in a forum posting.

4 Discussion

...