Mobile Accessibility Guidelines - Notifications

Feedback and assistance should


Non-critical feedback or assistance should be provided when appropriate.


Occasional feedback and assistance can help people learn how to use something unfamiliar. It can be especially helpful for young children and people with cognitive impairments.

When someone is not completing an objective correctly and/or does not progress multiple times, support and encouragement can motivate them to continue or keep trying. For example, in a game or other interactive content this could include hints, tips or the option to pass and move on to other content.


iOS

Where necessary, provide help documentation in the application. Make sure that the content is easy to find - for example, place the Help option within the application’s navigation and/or settings menu.

Additionally, provide context-sensitive help where necessary. For example, if a user is creating a password, indicate the number of characters that represents a strong password.

Haptic feedback and alerts can be useful, but be careful not to overuse these, as users may find them too intrusive and may even ignore future notifications or choose to switch them off entirely. Use these methods to deliver important - ideally actionable - information such as error messages, responses to chat messages, and so on.

For more information, refer to the .

iOS Example (Objective-C)

// In a ViewController that is hosted in a UINavigation controller provide feedback on the bottom toolbar as follows
UILabel *aLabel = [[UILabel alloc] initWithFrame:CGRectMake(0, 0, 50, 44)];
aLabel.text = @"Some helpful info";
// Configure the label with font, size etc.
 
UIBarButtonItem *labelBarButtonItem = [[UIBarButtonItem alloc] initWithCustomView:aLabel];
self.toolbarItems = @[labelBarButtonItem];

Android

Where necessary, provide help documentation in the application. Make sure that the content is easy to find - for example, place the Help option within the application’s navigation and/or settings menu.

Additionally, provide context-sensitive help where necessary. For example, if a user is creating a password, indicate the number of characters that represents a strong password.

For more information, refer to the document.

Android Pass Example

For simple feedback you could use a Toast or a Snackbar:

Example 1

A toast

Toast.makeText(context, "Hello, I'm a hint!", Toast.LENGTH_SHORT).show();

Example 2

A snackbar

Snackbar.make(parentView, "Hello, I'm a hint!", Snackbar.LENGTH_SHORT).show();

HTML

Where necessary, provide help documentation in the application. Make sure that the content is easy to find - for example, place the Help option within the application’s navigation and/or settings menu.

Additionally, provide context-sensitive help where necessary. For example, if a user is creating a password, indicate the number of characters that represents a strong password.

Avoid overwhelming the user with too much feedback.

HTML Pass Example

<label for="myPassword">Please enter your password</label>
<input id="myPassword" type="password" aria-describedby="passwordInstructions"</>
<span tabindex="-1" id="passwordInstructions">Enter at least 14 characters for a strong password.</>

Testing

Procedures

  1. Start the screen reader.
  2. Activate the app or game.
  3. Locate or activate any feedback, hints or help.
  4. Verify that this assistance is both visual and available to the screen reader.
  5. Verify that this assistance is appropriate and not over-bearing.

Outcome

The following check is true:

  • Assistance provided is appropriate and inclusive;
    • visual;
    • announced by a screen reader.