hannalaakso / accessible-timeout-warning Goto Github PK

We currently have some draft guidance (see "How client side and server could potentially communicate") for how the component should communicate with the server in case of an impending timeout.

We've also put some placeholders in the script for where these points of communication might happen.

We should look to improve the documentation for this, ideally on the basis of different server configurations.

There probably won't ever be definite guidance for this as the service team should consider what works best for their set up. However some examples would be really useful.

There is ongoing (as of 2020) work to publish a modal in the GOV.UK Design System. See acceptance criteria for more information.

Once the modal is published this project should be updated to use the GOV.UK Design System modal.

The frequency of the live region updates makes it difficult to use a screen reader. Suggest that the visible time updates are not included in the live region, but instead a hidden live region is created that updates less frequently (perhaps every 15 or 30 seconds).

Background

The component changes the content of at-timer with a countdown message at intervals.

Issue

When the component was tested on (See "Accessibility") VoiceOver + Safari + iOS 10.3.2 + iPhone 5s, there were issues with getting VoiceOver to read out numbers in longer strings when the content of at-timer changed.

For instance "We will reset your application if you do not respond in 2 minutes 30 seconds" was read out as "We will reset your application if you do not respond in".

To get around this we experimented with converting the numbers to letters at which point iOS read the message out correctly.

Next steps

This behaviour in iOS feels like an anomaly and was found on a c.2017 version of iOS so we should experiment removing the conversion to letters and test the component on the last couple of iOS versions to see if the problem can be replicated there.

If the problem can't be replicated we should probably just consider removing the code that converts numbers to letters. If there is an issue then bugs should be filed with browser vendors where relevant.

Since the project now forks govuk-frontend we should add unit and integration tests for the component following the conventions of govuk-frontend.

Where can I find the documententaion for this component?