New issue
Advanced search Search tips

Issue 761230 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

aria-autocomplete not exposed on <input type="text"> without role

Project Member Reported by ja...@nvaccess.org, Sep 1 2017

Issue description

Chrome Version: 62.0.3201.2 (Official Build) canary (64-bit)
OS: Windows 10 Version 1703 (OS Build 16251.0) 64-bit

STR (with the NVDA screen reader):
1. Start NVDA.
2. Open this URL in Chrome: data:text/html,<input type="text" aria-autocomplete="inline">
3. Tab to the text input.
Expected: NVDA should report "edit  has autocomplete"
Actual: NVDA reports "edit" but not "has autocomplete"

If you add role="textbox", the autocomplete state is exposed as expected. The HTML AAM says that <input type="text"> should map to role="textbox", so it should be treated the same regardless of the explicit role.

 
Status: Available (was: Untriaged)
Google Chrome	64.0.3253.0 (Official Build) canary (64-bit) (cohort: Clang-64)
Windows 10 Enterprise Version 1607 Build 14393.1770
NVDA 2017.3
JAWS 2018.1710.42 private preview release

I can reproduce this issue. NVDA reads "edit" only. 
I also tested with JAWS and it said "edit type in text". 

I also tested in Firefox 56.0.2 and it said "edit has autocomplete" 

Comment 3 Deleted

Comment 4 Deleted

Comment 5 Deleted

Comment 6 Deleted

Comment 7 Deleted

Comment 8 Deleted

Comment 9 Deleted

Comment 10 Deleted

Comment 11 Deleted

Comment 12 Deleted

Comment 13 Deleted

Project Member

Comment 14 by bugdroid1@chromium.org, Dec 4 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d

commit 80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d
Author: Nektarios Paisios <nektar@chromium.org>
Date: Mon Dec 04 16:24:08 2017

According to spec native text controls should automatically get the ARIA textbox role

According to HTML to platform accessibility mappings 1.1 native text boxes input and textarea, but not content editables, should get an ARIA role of textbox.
I went through all our code in Blink and observed that aria-autocomplete was the only case where we didn't apply the same treatment to ARIA and native text controls.
R=aleventhal@chromium.org, dmazzoni@chromium.org

Bug:  761230 
Change-Id: Ie25e0b072b24f1f6ebf6d5b2e317b656fb463fdf
Tested: manually, browser test
Reviewed-on: https://chromium-review.googlesource.com/804915
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521358}
[modify] https://crrev.com/80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d/content/test/data/accessibility/aria/aria-autocomplete-expected-android.txt
[modify] https://crrev.com/80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d/content/test/data/accessibility/aria/aria-autocomplete-expected-blink.txt
[modify] https://crrev.com/80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d/content/test/data/accessibility/aria/aria-autocomplete-expected-win.txt
[modify] https://crrev.com/80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d/content/test/data/accessibility/aria/aria-autocomplete.html
[modify] https://crrev.com/80fcc0006f18421ea22bc3ba0d35a0cddf3dea1d/third_party/WebKit/Source/modules/accessibility/AXNodeObject.cpp

Status: Fixed (was: Available)

Sign in to add a comment