Number of 'nights' not picked up by a screen reader
When using the date picker in the accommodation category of the PSW, the number of nights selected, 'nights', is not picked up by a screen reader unless the user navigates backwards from the 'clear' link. The order and placement of this could be reviewed for usability/accessibility as having ‘X nights’ announced by the screen reader as confirmation would improve user experience.
Given a user is using the PSW to select accommodation dates
When they have made their selection of dates
Then the screen reader reads out 'x nights' without having to tab backwards
Screen reader focus confusing once selecting 'save changes'
When 'saved changes' is selected to input guests/units in the accommodation category of the PSW, screen reader focus is on the position where the button was before it closed.
Given a user is using the PSW to input guests/units
When they select the 'save changes' button
Then screen reader focus is...
Can't abandon search from guest dropdown box
In the guest selection drown-down box, the user cannot abandon the search and tab to the next item on the page. Tabbing brings you into a continuous loop on the selection of units/adults/children.
Given a user has opened the guest selection dropdown box in the accommodation category of the PSW
When they choose to abandon the search without saving changes
Then the screen reader should bring them to the next sensible item on the page
Screen reader users on iPad and iPhone had issues with the focus moving unexpectedly wen they were interacting with the PSW. For example, when the user changed month, the focus went to another part of the page below the PSW which meant that they had to navigate back to the tool. This happened several times when interacting with this element.
The screen reader focus should not jump around when the user is interacting with the product search widget.
Raised from RNIB A11y testing March 2023
When a screen reader user adds a unit the focus stays on the “add a unit” link.
Some users will not realise that the new information has appeared above the link, and they need to move back to find the details for the second unit.
In addition, when interacting with the unit element, this opens automatically as a pop-up when the screen reader tabs to the element. There is no warning to tell the user that this is the case so they will not know that a pop-up has appeared.
The screen reader focus should go to a logical place so that new content is easily accessible. Additionally, feedback should be provided to alert the user that the information is above or that the pop up has opened.
Raised from RNIB A11y testing March 2023
Tabbing order of 'clear' is confusing for screen readers
When accessing the clear element on desktop with JAWS this is announced as “clear link”. It is not clear what is being cleared as it is in the tab order after the location field so in speech it appears that what is going to be cleared is the location.
The navigation of the elements in the form needs to be logical and the label of the clear button must tell the user what will be cleared if selected.
Number of 'nights' not picked up by a screen reader
When using the date picker in the accommodation category of the PSW, the number of nights selected, 'nights', is not picked up by a screen reader unless the user navigates backwards from the 'clear' link. The order and placement of this could be reviewed for usability/accessibility as having ‘X nights’ announced by the screen reader as confirmation would improve user experience.
Given a user is using the PSW to select accommodation dates When they have made their selection of dates Then the screen reader reads out 'x nights' without having to tab backwards
Screen reader focus confusing once selecting 'save changes'
When 'saved changes' is selected to input guests/units in the accommodation category of the PSW, screen reader focus is on the position where the button was before it closed.
Given a user is using the PSW to input guests/units When they select the 'save changes' button Then screen reader focus is...
Can't abandon search from guest dropdown box
In the guest selection drown-down box, the user cannot abandon the search and tab to the next item on the page. Tabbing brings you into a continuous loop on the selection of units/adults/children.
Given a user has opened the guest selection dropdown box in the accommodation category of the PSW When they choose to abandon the search without saving changes Then the screen reader should bring them to the next sensible item on the page
Old Jira ticket: https://jira.visitscotland.com/browse/VSD-249
Screen reader focus issue on iPhone and iPad
Screen reader users on iPad and iPhone had issues with the focus moving unexpectedly wen they were interacting with the PSW. For example, when the user changed month, the focus went to another part of the page below the PSW which meant that they had to navigate back to the tool. This happened several times when interacting with this element.
The screen reader focus should not jump around when the user is interacting with the product search widget.
Raised from RNIB A11y testing March 2023
When a screen reader user adds a unit the focus stays on the “add a unit” link.
Some users will not realise that the new information has appeared above the link, and they need to move back to find the details for the second unit.
In addition, when interacting with the unit element, this opens automatically as a pop-up when the screen reader tabs to the element. There is no warning to tell the user that this is the case so they will not know that a pop-up has appeared.
The screen reader focus should go to a logical place so that new content is easily accessible. Additionally, feedback should be provided to alert the user that the information is above or that the pop up has opened.
Raised from RNIB A11y testing March 2023
Tabbing order of 'clear' is confusing for screen readers
When accessing the clear element on desktop with JAWS this is announced as “clear link”. It is not clear what is being cleared as it is in the tab order after the location field so in speech it appears that what is going to be cleared is the location.
The navigation of the elements in the form needs to be logical and the label of the clear button must tell the user what will be cleared if selected.