Graphical user interface, text, application Description automatically generated

Box 1: AccessibleLabel

Scenario: Before deploying the app to production, you must ensure that the app conforms to Microsoft accessibility and performance guidelines.

User2 is visually impaired and cannot see images.

AccessibleLabel is a label for screen readers.

An empty value for Image, Icon, and Shape controls will hide the controls from screen reader users.

Box 2: TabIndex

User3 is unable to use a mouse.

TabIndex determines if the control participates in keyboard navigation.

Keyboard navigation is an important aspect of any app. For many, the keyboard is more efficient than using touch or a mouse. The navigation order should:

Mirror what is seen visually.

Only have a tab stop at controls that are interactive.

Follow either an intuitive across and then down "Z" order or a down and then across "reverse-N" order.

Graphical user interface, text, application, email Description automatically generated

Box 1: Security role

Scenario: Employees must only be able to access their own time tracking records from the app.

Testers report that they can see time entries in the Time Tracker app, not just their own.

Box 2: Field-level security

Scenario: Employees must only be able to modify time records for the current and previous day.

Testers report that they can edit any existing time entries.

Box 3: Hierarchical security

You use field security tables to apply field-level security, which restricts field access to specified users and teams.