Open
Description
👀 Before submitting...
- I upgraded to pagy version 9.3.4
- I searched through the Documentation
- I searched through the Issues
- I searched through the Q&A
- I asked Pagy Trained AI - Warning - The information may not be 100% accurate, but it serves as a good starting point for further investigation.
🧐 REQUIREMENTS
- I am providing a VALID code file that confirms the bug
- I am NOT posting any of the USELESS THINGS listed above
- I am aware that this issue will be automatically closed if the code file is missing or INVALID
💬 Description
- Reproduction: repro.ru.txt (no changes made)
- What actually happens: When using any screenreader (NVDA + Chrome used) the previous and next link are announced according to the aria-label attached, but are not recognised as "next" and "previous" links, breaking any override for the next/previous links, breaking shortcuts set up to navigate, and potentially breaking voice commands depending on the used assistive technology.
- What should happen: The
prevandnextlinks should haverel="prev"andrel="next", when enabled, so that screenreaders, shortcuts, and voice commands work as intended.
Relevant code change was introduced here: 48382d6#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edR54
Workaround is to not use pagy_nav and self-implement, which we have done now.