[A11Y] Pagefind : résolution du bloquage au lecteur d'écran#1579
Merged
Conversation
Olivia206
requested review from
SebouChu,
alexisben,
arnaudlevy and
pabois
as code owners
July 10, 2026 07:59
Contributor
djLintHugolintDirectories are perfect ✅Partials calls are perfect ✅Lines are perfect ✅Complexity is perfect ✅ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type
Description
Le lecteur d'écran était bloqué par la balise
<pagefind-body>, l'empêchant d'accéder aux filtres et aux résultats. C'est un problème inhérent à pagefind. Cela empêche la validation du critère 12.9 du RGAA. L'enlever ne change rien à l'affichage et au bon fonctionnement de la recherche.On en profite pour rendre la restitution du compte des résultats dynamique, pour que cela se mette à jour avec la saisie des filtres.
Niveau d'incidence
Référence (ticket et/ou figma)
#1577