Screen reader is not announcing error when required "Title", "Genre" and "Rating" fields kept blank: A11y_ASP.NET_Movies_Create Movies_ScreenReader

[PoojaNamde]

GitHub Tags:

#A11yMAS; #A11yTCS; #A11ySev2; #BM_ASP.NET_Web_Jun2024; #.NETCore; #WCAG4.1.3; #DesktopWeb; #Win11; #FTP; #Narrator; #NVDA; #ChromiumEdge; #Chrome;

Environment Details:

App name: ASP.NET
Window Version: Win 11
OS Build: 22621.3085
Screen readers: Narrator, NVDA 2023.3.3

Repro Steps:

1. Turn on Narrator/NVDA.
2. Download the "BlazorWebApp" zip file and run .exe file.
3. Command prompt will open, TAB to "http://localhost:5000/" link and press CTRL + ENTER key.
4. TAB to "Movies" tab and hit ENTER key. TAB to "Create New" button and hit ENTER key.
5. TAB to "Title", "Genre" and "Rating" fields and observe that Narrator Screen reader is not announcing error when required "Title", "Genre" and "Rating" fields kept blank.

Actual Result:

Narrator Screen reader is not announcing error when required "Title", "Genre" and "Rating" fields kept blank.

Similar issue also observed with Chrome + NVDA.

Expected Result:

Narrator Screen reader should be announcing error when required "Title", "Genre" and "Rating" fields kept blank

User Impact:

Screen reader users will not be able to get information about the required fields and will miss out the information.

Attachment

56284_A11y_ASP.NET_Movies_Create.Movies_NVDA.webm

56284_A11y_ASP.NET_Movies_Create.Movies_Narrator.webm

[Yash14j]

GithubTags:#Rev:yaja;

[PoojaNamde]

#Regressed:09-20-24;

Verified the bug in the environment http://localhost:5000/movies/create
still able to repro it. hence reactivating it.
Please find repro attachment for reference.

Video.9-20.at.10.48.webm

[PoojaNamde]

Verified the bug in the environment https://localhost:7202/Movies/[Create](https://localhost:7202/Movies/Create)
still able to repro it. hence reactivating it.
Please find repro attachment for reference.

[PoojaNamde]

#Closed; #Regressed:11-15-24;

Verified the bug in environment
Bug is fixed and does not repro. Hence closing the bug.
Please find the closing attachment