🦾 Fable Results: Date Selection Component (Storybook Design) #6652
Closed
RM-1978
started this conversation in
UI components
Replies: 2 comments 1 reply
-
|
Requirement 1: Date Validation is already assigned to @substrae in the Insight Tracker #7324 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@RM-1978 is this discussion still ongoing or can it be closed? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@mnigh it might be worth noting what tickets were created to resolve these issues, and then close if they are all taken care of. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Fable User-requested adjustments (Q4 2022-23)
List of Fable user insights/ results for the Date Picker (Storybook Design)
New requirement 1?
Develop date validation criteria for the component.
Why
The date component does not announce an error message when an invalid date is entered (e.g., February 30, 2031)
New requirement 2?
Manual evaluation of the component with Narrator and VoiceOver to be sure that there are no issues with these out-of-the box readers.
Why
Fable tester recommended test because they Were testing using JAWS and NVDA.
New requirement 3?
Adjust the alert to announce the errors on a single input for the day and year fields of the date picker. For example, if the day is invalid in February, then it would be best to say enter a valid day.
Why
Difficult to use the stepper for selecting the year and day. There isn't any feedback indicating whether the value was adjusted, Relevant WCAG criteria: 2.1.1 Keyboard, 4.1.2 Name, Role, Value Adjustment would allow us to satisfy relevant WCAG Criteria: 2.1.1 Keyboard, 4.1.2 Name, Role , Value
New requirement 4?
Adjust the combo or edit box for the year does to ensure it changes when using the VO arrow keys.
Why
If you don't enter the year, the field only fills in one number. When you manually enter the year, it does move the digits for the year correctly. This makes it difficult to understand with a screen reader. WCAG: 2.1.1 Keyboard,4.1.2 Name, Role, Value
New requirement?
For each of the fields when navigating the form, it reads the field contents before the form label.
Why
it would be better if the form label is read first to more easily understand what is needed by a screen reader.
Who needs to work on this:
@esizer with @RM-1978
Who needs to review this:
@substrae, @Jerryescandon @mnigh and @petertgiles
Done when
Beta Was this translation helpful? Give feedback.
All reactions