New issue
Advanced search Search tips

Issue 808294 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 20
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Google Forms a11y: reading validation text incorrectly

Project Member Reported by leberly@chromium.org, Feb 2 2018

Issue description

Chrome OS 65.0.3325.35 (Official Build) dev (64-bit)
Firmware Version	Google_Lulu.6301.136.57

Steps to reproduce:
# Turn on Chromevox screen reader using ctrl + alt + z
# Create new Google Form with an example question that has a short answer field
# In that question, go to More Options Menu > Check "Response Validation"
# Set the validation dropdown fields to "Text" and "email address" 
# View the form as a responder (preview feature will work for this)
# Put focus in the question response edit field. ChromeVox includes "Edit text, email entry" in the description of the field
# Start to type a response in the question field. 
Expected: user is only read warning about email formatting after leaving the edit field. User already received the hint that it must be an email format when focusing on the text box
Actual: User is never given warning about email formatting unless they tab out of the form and tab back into it. 

A user in the mailing lists reported that a warning was being read after each keystroke using NVDA and Firefox. Now I will repro with other software to isolate the issue.


 
Status: ExternalDependency (was: Assigned)
Summary: Google Forms a11y: reading validation text incorrectly (was: Google Forms reading validation text incorrectly )
Google Chrome	66.0.3336.5 (Official Build) canary (64-bit) (cohort: Clang-64)
Windows 10 Enterprise Version 1607 Build 14393.2007
NVDA 2017.4
JAWS 2018.1801.81 ILM 
Firefox ESR 52.6.0 (64-bit)

In both JAWS and NVDA in Chrome, the form behaves approximately as expected. The user receives the alert about needing it to be a valid email address upon stopping typing one letter. After that, the letters are read normally. 

In Firefox with both JAWS and NVDA, I can reproduce that the alert is read after each letter typed. 

Therefore, I will be resolving this bug and filing it internally. 
Labels: OS-Windows
b/72839606
Labels: a11y-secondary
Status: WontFix (was: ExternalDependency)
Resolving this bug as WontFix since it does not repro on Chrome. Bug has been reported internally for appropriate team. 

Sign in to add a comment