Currency Field

User stories

The following user stories can be used to understand when this component should be used, and how to know when it's been implemented correctly.

  • As someone using the component, I want to be able to easily understand the information required from me.
  • As someone with a cognitive disability, I want to be able to understand if any personal information is required, for example whether it's the transaction amount I paid or the transaction currency I paid in.
  • As someone with a cognitive disability, I want to be able to understand any errors related to the currency field, as well as how to resolve the error.
  • As a keyboard-only user, I want to be able to navigate to the currency field using the Tab key.
  • As a screen reader user, I want the label relating to the currency field to be announced when navigating to the field.
  • As a screen reader user, I want any additional information provided alongside the currency field's label to be announced when navigating to the field.
  • As a screen reader user, I want any error messages relating to the currency field to be announced when they become present.
  • As a screen reader user, I want to be able to understand the currency that the information is required in.
  • As a voice-control user, I want to be able to navigate to the currency field using the associated label.

Test steps

Use these steps to check that the checkbox component has been implemented correctly:

  1. Turn on a screen reader.
  2. Navigate to the currency field using the Tab key.
  3. Verify that the currency field has a visible label.
  4. Verify that a name for the currency field is announced and that it includes the visible label.
  5. Verify that the correct currency type is announced.

If any errors appear when the form is validated, complete the following checks:

  1. Turn on a screen reader.
  2. Navigate to the currency field using the Tab key
  3. Verify that once the currency field receives focus, that there is an announcement to convey that there is an error with this field.

Accessibility checklist

 

User stories