Done
Details
Assignee
Vilde StabellVilde StabellReporter
Vilde StabellVilde StabellLabels
Code reviewer
Runar KaspersenRunar Kaspersen(Deactivated)Tester
Gwen Tripet-CostetGwen Tripet-CostetTimes transitioned to development
2Original estimate
Time tracking
11.42h loggedSprint
NoneFix versions
Priority
Medium
Details
Details
Assignee
Vilde Stabell
Vilde StabellReporter
Vilde Stabell
Vilde StabellLabels
Code reviewer
Runar Kaspersen
Runar Kaspersen(Deactivated)Tester
Gwen Tripet-Costet
Gwen Tripet-CostetTimes transitioned to development
2
Original estimate
Time tracking
Sprint
None
Fix versions
Priority
Created October 18, 2023 at 8:31 AM
Updated June 18, 2024 at 10:44 AM
Resolved June 18, 2024 at 10:44 AM
For estimation, we should consider this risky, since we’ve struggled with it before
Background:
Currently the progress in the question set (“Question x of y“) is announced by setting focus to the qs-progress-announcer element. Setting focus to elements that aren’t visible is considered bad practice, as the visually-lost focus can confuse keyboard users and introduces more steps to navigating the site for them.
Additionally, setting focus to hidden elements has caused quite messy accessibility problems for us before, with the Question.read( ) function making content types completely unusable by keyboard (described here: )
Potential solution:
This was attempted fixed in , but time constraints and lacking relevancy to the scope of that issue made us go for a less drastic solution.
The pr introduces a new bug that sometimes reads “Question 1 of x“ twice when clicking the ‘retry’ button after answering all the questions and submitting. If that is solved, this would be a good solution.