Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question to principle4.guideline4_1.4_1_2.h91.inputtext.name #310

Open
LuciaLux opened this issue Nov 2, 2022 · 1 comment
Open

question to principle4.guideline4_1.4_1_2.h91.inputtext.name #310

LuciaLux opened this issue Nov 2, 2022 · 1 comment

Comments

@LuciaLux
Copy link

LuciaLux commented Nov 2, 2022

I have this input

<input _ngcontent-c1="" autocomplete="off" id="searchInput" name="query" required="" type="text" placeholder="Cerca" class="ng-untouched ng-pristine ng-invalid">

and the following error is generated:

Principle4.Guideline4_1.4_1_2.h91.InputText.Name 
THIS TEXTINPUT ELEMENT DOES NOT HAVE A NAME AVAILABLE TO AN ACCESSIBILITY API. VALID NAMES ARE: LABEL ELEMENT, TITLE UNDEFINED, ARIA-LABEL UNDEFINED, ARIA-LABELLEDBY UNDEFINED.

my question is:
the value given to the title, the ARIA-LABEL and the ARIA-LABELLEDBY, ie undefined, is correct?

@ironikart
Copy link
Contributor

The error looks correct to me. From the example you posted there is no programatic way to determine what accessible text is available. I'd suggest looking at the WCAG guidelines for possible remediations. The technique might not be exactly what you are after from the error message, but this should help: https://www.w3.org/WAI/WCAG22/Techniques/html/H44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants