Creates accessibility issues

Please fix A11Y errors & warnings.

While we enjoy using this plugin in multiple websites, I can’t help but be annoyed by the fact that it creates accessibility warnings itself. Here are the few I find most straightforward to fix:

1. Local link destination does not exist
– href=”#content” does not point to anything. Anyways, this can be avoided by replacing ‘a’ tag with a ‘button’ tag instead.

2. Redundant WAI-ARIA attribute
– If you’re using a tag ‘nav’ there’s no need to include role=”navigation”

3. Non-distinguishable landmarks
– ‘nav’ tag is commonly used in many websites. It’s good if you include an aria-label to distinguish your nav with others in the same page

These are only the once I wrote here. I’de recommend that you validate it so that it is fully A11Y compliant.

• This topic was modified 4 years, 4 months ago by owenfar.