New issue
Advanced search Search tips

Issue 642976 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

input type=text value is not read by Windows Narrator

Reported by sean...@gmail.com, Aug 31 2016

Issue description

Chrome Version       : 55.0.2845.0 (Official Build) canary (64-bit)
URLs (if applicable) : http://www.powermapper.com/tests/screen-readers/labelling/input-text-aria-label/
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
         IE: PASS (11)

What steps will reproduce the problem?
(1) Start narrator
(2) Tab into a text box with content in it

What is the expected result?
When the user focuses the text box, the content should be read by narrator.

What happens instead?
Nothing

Please provide any additional information below. Attach a screenshot if
possible.

 

Comment 1 by tkent@chromium.org, Sep 1 2016

Components: UI>Accessibility
Status: Available (was: Unconfirmed)
Summary: input type=text value is not read by Windows Narrator (was: input type=text value is not read by screen readers)
Changing summary to reflect Windows Narrator.

Chrome works with the most popular screen readers on Windows including JAWS, NVDA, and Window-Eyes, but we don't support Narrator yet.

It'd help to know what Windows version you were using.

Comment 3 by sean...@gmail.com, Sep 1 2016

Oops! I just tried with NVDA, and it does seem to work fine.

I was trying with Windows 10 Narrator.
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Labels: triage-nektar
Labels: -triage-nektar a11y-secondary
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 14

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment