-
Notifications
You must be signed in to change notification settings - Fork 77
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
Input Date Picker - Add context to default placeholder text to AT - (2036569968) #5581
Comments
By default the component has placeholder text |
Research will be determined in April for next dev steps needed. |
We should provide context the placeholder text string is the date format, where the format is only provided to screen readers via an Something like: <calcite-input aria-describedby="input-format" />
<span id="input-format" class="sr-only">Date format: MM/DD/YYYY</span> Since the context would need to change depending on the selected locale, there may be a better format to compliment all languages with translation strings. W3C example: https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/datepicker-dialog/#ex_label cc: #3671 for context to a similar solution when implementing a placeholder for |
Installed and assigned for verification. |
Verified with NVDA with Firefox and JAWS with Chrome on |
Module:
17a Input Date Picker
Violation:
Avoid use of placeholder values to label or explain input
WCAG Reference:
Instance ID:
2036569968
Severity:
8
Description:
[Issue]
There are form fields that rely on the placeholder attribute to supply their accessible name. Examples include:
[User Impact]
Users with cognitive disabilities may be unable to determine the purpose of the field after the placeholder disappears. Some assistive technologies will not use the placeholder attribute as a field's accessible name, so screen reader users will have difficulty determining what fields are for and speech input users will have difficulty navigating to them.
[Code Reference]
Note:
[Suggestion]
Avoid use of placeholder values to label or explain input.
Labels must meet the following requirements:
<label>
element with a for attribute set to the ID of the field.[Compliant Code Example]
Media Type:
Forms
Additional Resources:
The text was updated successfully, but these errors were encountered: