a11y: role=navigation is not permitted on UL tag - causes failure on Section 508 scans
See original GitHub issueHi, thanks for contributing!
This project is maintained in my spare time, so in order to help me address your issue as quickly as possible, please provide as much of the following information as you can.
– Michael
[^ delete this message]
=======
Angular version:
ngx-pagination version:
Description of issue:
Steps to reproduce:
Expected result:
Actual result:
Demo: (if possible, edit this StackBlitz demo and paste the link to your fork)
Any relevant code:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Developers - a11y: role=navigation is not permitted on UL tag
a11y : role=navigation is not permitted on UL tag - causes failure on Section 508 scans.
Read more >All WCAG 2.1 Techniques | WAI
Techniques for WCAG 2.1. Summary. Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet...
Read more >Air Force Section 508 Playbook
The Playbook provides guidance to the Air Force to ensure information and communication technology (ICT) is compliant with Section 508 guidelines and standards....
Read more >ARIA: navigation role - Accessibility - MDN Web Docs - Mozilla
The navigation role is used to identify major groups of links used for navigating through a website or page content.
Read more >ANDI - Alerts
Why did ANDI alert this? This form element has no HTML markup that would provide an accessible name for the element. Why is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
OK, available now in v5.1.0. 👍
Also, if role=“navigation” is used anywhere, it’s always supposed to be accompanied by an aria-label (the only exception is when there is only one role=“navigation” on the entire page. Thank you again, we love this component.