Query: Entering 'autocomplete list box' on desktop & mobile devices

[MazOneTwoOne]

Hopefully this is the best way to ask this question.

On our service we have implemented an editable combobox which has a list autocomplete. We have followed W3C guidance and the alphagov-accesible-autocomplete component implementation.

Just have some questions on how you would expect a user to enter the 'autocomplete list' on different devices with and without the use of a screen reader.

For desktop/laptop devices [without screen reader]:

• A user would go into the 'autocomplete list', by using the ‘down’ arrow on the keyboard. We don’t tab into the listbox. Is that the correct expected behaviour?

For desktop/laptop devices [with screen reader]:

• A user would go into the 'autocomplete list', by using the ‘down’ arrow on the keyboard (with the use of another combined key press e.g. option or ctrl). We don’t tab into the listbox. Is that the correct expected behaviour?

For mobile devices [without screen reader]:

• A user would go into the 'autocomplete list', by using touch and selecting the suggested item in the list. We would not be able to swipe or a virtual keyboard. Is that the correct expected behaviour?

For mobile devices [with screen reader]:

• A user would go into the 'autocomplete list', by using touch and selecting the suggested item in the list. We would not be able to swipe or a virtual keyboard to enter the list (unless using Android device). A user could use swipe gestures, once they have entered into the list. Is that the correct expected behaviour?