New issue
Advanced search Search tips

Issue 866338 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature
Team-Accessibility



Sign in to add a comment

[Orca] Text input fields in HTML and in browser chrome are inaccessible

Project Member Reported by joanmari...@gmail.com, Jul 23

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3500.0 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome/Chromium
  * export ACCESSIBILITY_ENABLED=1, and
  * launch with --force-renderer-accessibility

2. Launch the attached accessible-event listener in a terminal

3. Load "data:text/html,<input value="foo" />" in browser

4. Give the input focus

5. Arrow around in the input

6. Select text in the input

7. Change the text in the input

8. Repeat steps 4 through 7 for the Address and search bar

What is the expected behavior?
The accessible-event listener would print out events for:

* focus changes
* content changes
* selection changes
* caret movements

In addition, the text content would be printed out with each logged event.

What went wrong?
The accessible-event listener only prints out events for focus changes along with an error that the text interface is not implemented.

Did this work before? No 

Chrome version: 70.0.3500.0  Channel: n/a
OS Version: 
Flash Version: 

Compare to: Firefox (with accessibility enabled), Epiphany

Documentation: https://developer.gnome.org/atk/stable/AtkText.html

Impact: The address and search bar, and text entries in content, are inaccessible to Orca users.
 
entry-events.py
757 bytes View Download
Labels: Needs-Triage-M70
Components: -UI UI>Accessibility
Cc: dmazz...@chromium.org
Labels: -Type-Bug Type-Feature
Components: UI>Accessibility>Compatibility
Status: Available (was: Unconfirmed)

Sign in to add a comment