TextInputWithTokens

The 'Text input with tokens' component has a number of issues for assistive technology users, including keyboard-only, voice control, and screen reader users. The component should not be used until the issues are resolved.

The tokens can only be reached with a keyboard by using the arrow keys when the cursor is at the beginning text input. This is not intuitive for keyboard, voice control users or screen reader users.

For screen reader users, there is no indication that a text input has tokens present, and the need to use arrow keys means the tokens are unlikely to be found.

In JAWS and NVDA there are issues with navigating and removing tokens. In both JAWS and NVDA, once a token has focus the screen reader switches from forms/focus mode to virtual/browse mode. A user has to manually switch back to forms/focus mode to navigate to other tokens, which is not an intuitive interaction. In Firefox with NVDA and JAWS, the token label and the instructions are not announced when the other tokens receive focus.