A11y_.NET Core_ASP.NETCore_AngularForgotPassword_ScreenReader: No asterisk marks are provided for the required fields
Truptik12 opened this issue · comments
42337_A11y_.NET Core_ASP.NETCore_AngularForgotPassword_ScreenReader.zip
“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11yMAS;#A11yTCS;#.NET Core[aspnetcore]-Win32-June2022;#.NET Core;#A11ySev2;#WCAG3.3.2;#DesktopWeb;#Win11;#Benchmark;#NVDA;#Narrator;
Environment Details:
.NET Core
ASP.NET Core
Operating System: Windows 11 Enterprise 21H2
Chrome: Version 102.0.5005.115 (Official Build) (64-bit)
Steps to Reproduce:
- Open command prompt.
- Create a folder using command "mkdir foldername" e.g. "mkdir Angular"
- Move to the created directory using command "cd foldername"
- Run the following command "dotnet new angular -au Individual" and hit enter.
- Run the following command "dotnet run"
- Copy the First URL link from Command prompt and copy it
- Paste it in URL section of Browser and hit Search
- Browser page will open with above template loaded
- Hit enter on login link
- Tab and navigate to "forgot your password?" link and press enter.
- The screen reader announces "Email" is a required field, but no asterisk is provided.
Actual:
No asterisk marks are provided for the required fields.
This issue is observed throughout the application for all the required fields.
This is also observed with chromium edge and Narrator
Expected:
Asterisk marks should be provided for the required fields.
User Impact:
Low vision users face difficulty to identify which control is required.
@merriemcgaw for 6.0, we added area-required for our forms, so for example for login username, we have area-required=true, is that sufficient indication for which inputs are required?
<input class="form-control" autocomplete="username" aria-required="true" type="email"
If this is regarding users who can see, then there's text indicating that "the email field is required" already, which is much more obvious than single asterisk would be:
Your comments make a lot of sense to me. Let's set up some time in Office Hours to discuss this issue. I think we might be able to get them to lower it to Sev3 which we don't have an SLA around.
Per discussion in accessibility office hours, the current product behavior is sufficient and this bug should be closed, reassigning back to the OP
Closing the bug as per the above comments.