![]() ![]() While this can be an annoyance for a sited user because they end up accidentally entering the day in the year section when they try to use the slashes, they can at least see what went wrong, and then go back and fix it. My suggestion via this forum link ( ) is to alter your date entry logic to allow users to both enter the dates without the slashes (which is what you have now except under a few edge cases where a slash is needed to move to the next section like 2 2/ 2022) as well as include the slashes where if the user is on the first digit of the day section and the / is pressed, do NOT advance them to the year section. The dateinput portion of the control does not account for users entering full dates into the control, meaning if a person was to try to type into the input where they included the slashes, it would throw them into the year section when they thought they were entering the day section.When testing your datepicker control in NVDA, there are a number of accessibility issues. ![]()
0 Comments
Leave a Reply. |