Best practice - Service features

When you’re building frontends, there are existing frameworks which can help you quickly build usable and accessible services.

There is some baseline functionality you will need to add to your service to meet the Web Content Accessibility Guidelines AA standard.

This doesn’t cover fundamentals such 1.4.1 Use of Color as 1.4.3 Contrast but is more to highlight features that will need to be included.

2.2.1 Timing Adjustable (A)

There are several ways we can meet this criterion.

You can manage a sessions time out pattern to allow the user to extend the time limit. This balances security with usability.

You can also meet this criterion by making your session longer than 20 hours, however, we need to apply this in the context of the service.

There may be cases where a real-time event such as two-factor authentication where a strike time limit is appropriate.

Full success criterion for 2.2.1 Timing Adjustable

3.3.4 Error Prevention (Legal, Financial, Data)

Following good practices for development means we should be validating the user input page by page and giving feedback to the user on how to correct any issues such as format using the error messages pattern.

However, the data can pass validation and still not be correct so we still need to give the user the option to check it.

When designing a very large transaction with multiple sections, it may help to include a check answers page at the end of each section.

Full success criterion for 3.3.4: Error Prevention (Legal, Financial, Data)