You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to fix:
Fix any of the following:
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references >elements that are empty
Form element does not have an implicit (wrapped)
Form element does not have an explicit
Element has no title attribute
Element has no placeholder attribute
Element's default semantics were not overridden with role="none" or role="presentation"
Environment: Chrome version 88.0.4324.146
====
This accessibility issue was found using Accessibility Insights for Web 2.23.0 (axe-core 4.1.1), a tool that helps find and fix accessibility issues. Get more information & download this tool at >http://aka.ms/AccessibilityInsights.
The text was updated successfully, but these errors were encountered:
Hi @madhaze and thanks for the report. I think the aria-label route seems the most logical and compatible. Would you be able to make a PR for this change ?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Removing
<label>
causes accessibility scans to fail.For accessibility
<input>
s need to have<label>
or can use aria-label. https://www.w3.org/WAI/tutorials/forms/labels/right now if
"notitle": true
is set the element does not render.It adding a class like bootstraps
sr-only
to the<label>
or addingaria-label
attribute to the<input>
would help make the form more accessible.Below is the return from doing a test on https://jsonform.github.io/jsonform/playground/index.html?example=gettingstarted with the "notitle": true set.
The text was updated successfully, but these errors were encountered: