A11y_.NET Core_ASP.NETCore_AngularFetchData_AI4W: No main landmark is defined on the "Fetch Data" page
Truptik12 opened this issue · comments
“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;#WCAG1.3.1;#DesktopWeb;#Win11;#Benchmark;#Element:Landmark;#AI4W;#AIManual;
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 fetch data link
- Run AI4W for and check for landmarks.
Actual:
No main landmark is defined on the "Fetch Data" page
This issue is observed throughout the application for all the Fetch Data pages.
Expected:
Main landmark should be defined on the "Fetch Data" page
User Impact:
If main landmark is not define on the page than users dependent on the screen reader will get difficulties to interact the page because when users will navigate in landmark mode, they will get difficulties to understand the purpose of the page.
Fixed in dotnet/spa-templates#70
#Closed;