ARIA attributes with invalid values on Next.js
What this is
3 elements have an ARIA attribute with a value that is not allowed or points to an element that does not exist.
Who it affects
- Screen reader users
Standards
How to fix it
- Use a valid value (for example `true`/`false`) and make sure every `aria-labelledby`/`aria-controls` id exists on the page.
On Next.js
ARIA attributes live in your JSX; search the component, fix or delete the attribute. Prefer native elements over ARIA roles where possible.
Other platforms
Prompt for an AI coding tool
Scan your site with AccessibilityBrief and you get a ready-to-use prompt for this problem, with the exact elements on your pages filled in.
Check your own website
Paste a web address. The free scan checks one page and shows what it finds.
More fixes
Automated testing detects only a portion of WCAG issues. Manual testing is required to assess full conformance.