Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 20 users
Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature
Team-Accessibility

Blocked on:
issue 463671



Sign in to add a comment
Orca screen reader doesn't work with chromium
Reported by nadeau....@gmail.com, Oct 12 2009 Back to list
Chrome Version       : <Copy from: 'about:version'>
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4:
Firefox 3.x:
IE 7:
IE 8:

What steps will reproduce the problem?
1.
2.
3.

What is the expected result?


What happens instead?


Please provide any additional information below. Attach a screenshot if
possible.
While using the orca screen reader and I open chromium it will read the
menus when you first open chromium. It will also read the menus when you
hit alt f and bring up the file option. But when I type in a url and go to
it chromium does not read the website at all. Any website that I try can
not be read with the orca screen reader.
 
Labels: -OS-All -Area-Misc OS-Linux Area-UI Feature-Accessibility
Comment 2 by evan@chromium.org, Apr 22 2010
Status: Untriaged
It's because the renderer is out of process.  Getting a11y right here is likely to be 
hard.
Comment 3 by evan@chromium.org, Jun 9 2010
Labels: Mstone-X
Status: Available
Labels: -Type-Bug -Pri-2 Type-Feature Pri-3
We've resolved the issue with accessibility and Chrome's multi-process architecture in a cross-platform way, and Chrome accessibility is now making good solid progress on Windows and Mac OS X. Implementing ATK and supporting Orca on Linux would now be relatively straightforward, but nevertheless time-consuming.

At this point, the number of Orca users is very small, so it doesn't make sense to prioritize this feature request until Windows and Mac accessibility is essentially finished, since those platforms have many thousands of disabled users.

However, if anyone in the community would like to work on implementing ATK and Orca support in Chrome, we'd be more than happy to help them get started and review the patches.

Comment 6 by infap...@gmail.com, Jun 23 2010
Just to comment that there are already a work done to implement ATK support on WebKit. But right now this is only available on the WebKitGtk+ port. You can check it on the directory WebCore/accessibility/gtk.

It provides the accessibility support for the WebKitWebView [1] GTK+ Widget. The main work is done by wrapping/proxying the accessibility objects from WebKit.

Right now the work is in progress and using Orca as reference, although the target browser for the moment is Epiphany, a Gtk+ browser. Anyway, this is also useful for the a11y support in other apps using WebKitGtk+, like DevHelp (an API documentation browser for GTK+ and GNOME).

As I said, work is in progress, Joanmarie Diggs (Orca maintainer) has created a metabug [2] with the things that Orca requires to work properly with WebKitGtk+.

Anyway, not sure how this work could be used in other ports (I don't have too much experience with WebKit internal infrastructure).

[1] http://webkitgtk.org/reference/webkitgtk-webkitwebview.html
[2] https://bugs.webkit.org/show_bug.cgi?id=25531
Comment 7 by knopp...@gmail.com, Aug 15 2011
As of today, the problem des not seem to be resolved yet, i.e. the rendering area of chromium (last tested version: 12.0.742.112~r90304-1) is not readable by orca. Unfortunately, this makes chromium currently a bad choice as browser for blind-friendly GNU/Linux distributions.

Question: Is someone actually working on this, with a contact address? Is there an official milestone plan including accessibility issues to be resolved with a specific version of chromium?
Cc: -klink@chromium.org -dmazzoni...@gmail.com dtseng@chromium.org
Labels: -Pri-3 -Mstone-X Pri-2
Owner: dmazz...@chromium.org
Status: Started
Summary: Orca screen reader doesn't work with chromium (was: NULL)
Project Member Comment 9 by bugdroid1@chromium.org, May 2 2012
Summary: Orca screen reader doesn't work with chromium (was: NULL)
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135020

------------------------------------------------------------------------
r135020 | dmazzoni@chromium.org | Wed May 02 16:00:58 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135020&r2=135019&pathrev=135020
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135020&r2=135019&pathrev=135020
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135020&r2=135019&pathrev=135020
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135020&r2=135019&pathrev=135020
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135020&r2=135019&pathrev=135020
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135020&r2=135019&pathrev=135020

Add initial GTK web accessibility framework.

This enables Linux desktop assistive technology such as the Orca screen
reader to access the web contents. Builds on the same accessibility stack
used by Mac & Windows already.

This change works with Orca now, but it's minimal: all that works is getting
the correct feedback when you tab through focusable links and controls in
a webpage. Future changes will add the rest of the support.

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links.
TBR=darin


Review URL: http://codereview.chromium.org/9839069
------------------------------------------------------------------------
Project Member Comment 10 by bugdroid1@chromium.org, May 2 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135027

------------------------------------------------------------------------
r135027 | jam@chromium.org | Wed May 02 16:28:26 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135027&r2=135026&pathrev=135027
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135027&r2=135026&pathrev=135027
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135027&r2=135026&pathrev=135027
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135027&r2=135026&pathrev=135027
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135027&r2=135026&pathrev=135027
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135027&r2=135026&pathrev=135027

Revert 135020 - Add initial GTK web accessibility framework.

This enables Linux desktop assistive technology such as the Orca screen
reader to access the web contents. Builds on the same accessibility stack
used by Mac & Windows already.

This change works with Orca now, but it's minimal: all that works is getting
the correct feedback when you tab through focusable links and controls in
a webpage. Future changes will add the rest of the support.

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links.
TBR=darin


Review URL: http://codereview.chromium.org/9839069

TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10316010
------------------------------------------------------------------------
Project Member Comment 11 by bugdroid1@chromium.org, May 3 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135160

------------------------------------------------------------------------
r135160 | dmazzoni@chromium.org | Thu May 03 08:52:51 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135160&r2=135159&pathrev=135160
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135160&r2=135159&pathrev=135160
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135160&r2=135159&pathrev=135160
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135160&r2=135159&pathrev=135160
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135160&r2=135159&pathrev=135160
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135160&r2=135159&pathrev=135160

Re-land: Add initial GTK web accessibility framework.

This enables Linux desktop assistive technology such as the Orca screen
reader to access the web contents. Builds on the same accessibility stack
used by Mac & Windows already.

This change works with Orca now, but it's minimal: all that works is getting
the correct feedback when you tab through focusable links and controls in
a webpage. Future changes will add the rest of the support.

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links.
TBR=darin
Review URL: https://chromiumcodereview.appspot.com/9839069
------------------------------------------------------------------------
Project Member Comment 12 by bugdroid1@chromium.org, May 3 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135166

------------------------------------------------------------------------
r135166 | dmazzoni@chromium.org | Thu May 03 09:20:06 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135166&r2=135165&pathrev=135166
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135166&r2=135165&pathrev=135166
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135166&r2=135165&pathrev=135166
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135166&r2=135165&pathrev=135166
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135166&r2=135165&pathrev=135166
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135166&r2=135165&pathrev=135166

Revert 135160 - Re-land: Add initial GTK web accessibility framework.

This enables Linux desktop assistive technology such as the Orca screen
reader to access the web contents. Builds on the same accessibility stack
used by Mac & Windows already.

This change works with Orca now, but it's minimal: all that works is getting
the correct feedback when you tab through focusable links and controls in
a webpage. Future changes will add the rest of the support.

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links.
TBR=darin
Review URL: https://chromiumcodereview.appspot.com/9839069

TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10348011
------------------------------------------------------------------------
Project Member Comment 13 by bugdroid1@chromium.org, May 6 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135593

------------------------------------------------------------------------
r135593 | dmazzoni@chromium.org | Sun May 06 08:25:00 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135593&r2=135592&pathrev=135593
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135593&r2=135592&pathrev=135593
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135593&r2=135592&pathrev=135593
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135593&r2=135592&pathrev=135593
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135593&r2=135592&pathrev=135593
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135593&r2=135592&pathrev=135593

Add initial GTK web accessibility framework (new with valgrind fix).

This is the same as http://codereview.chromium.org/9839069/ which was
landed but reverted due to a valgrind failure in content_unittests.

The valgrind failure was because browser_accessibility_manager_unittest.cc
is constructing its own subclass of BrowserAccessibility (for testing),
but BrowserAccessibilityManagerGtk was assuming that any BrowserAccessibility
could be static_casted to a BrowserAccessibilityGtk. I fixed this by
making ToBrowserAccessibilityGtk() a virtual method with a default impl that
returns NULL.

Original change:

This enables Linux desktop assistive technology such as the Orca screen 
reader to access the web contents. Builds on the same accessibility stack 
used by Mac & Windows already. 

This change works with Orca now, but it's minimal: all that works is getting 
the correct feedback when you tab through focusable links and controls in 
a webpage. Future changes will add the rest of the support. 

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links. 
TBR=darin,sky
Review URL: https://chromiumcodereview.appspot.com/10381010
------------------------------------------------------------------------
Project Member Comment 14 by bugdroid1@chromium.org, May 6 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135595

------------------------------------------------------------------------
r135595 | dmazzoni@chromium.org | Sun May 06 10:10:07 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135595&r2=135594&pathrev=135595
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135595&r2=135594&pathrev=135595
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135595&r2=135594&pathrev=135595
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135595&r2=135594&pathrev=135595
 D http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135595&r2=135594&pathrev=135595
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135595&r2=135594&pathrev=135595

Revert 135593 - Add initial GTK web accessibility framework (new with valgrind fix).

This is the same as http://codereview.chromium.org/9839069/ which was
landed but reverted due to a valgrind failure in content_unittests.

The valgrind failure was because browser_accessibility_manager_unittest.cc
is constructing its own subclass of BrowserAccessibility (for testing),
but BrowserAccessibilityManagerGtk was assuming that any BrowserAccessibility
could be static_casted to a BrowserAccessibilityGtk. I fixed this by
making ToBrowserAccessibilityGtk() a virtual method with a default impl that
returns NULL.

Original change:

This enables Linux desktop assistive technology such as the Orca screen 
reader to access the web contents. Builds on the same accessibility stack 
used by Mac & Windows already. 

This change works with Orca now, but it's minimal: all that works is getting 
the correct feedback when you tab through focusable links and controls in 
a webpage. Future changes will add the rest of the support. 

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links. 
TBR=darin,sky
Review URL: https://chromiumcodereview.appspot.com/10381010

TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10379029
------------------------------------------------------------------------
Project Member Comment 15 by bugdroid1@chromium.org, May 7 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135714

------------------------------------------------------------------------
r135714 | dmazzoni@chromium.org | Mon May 07 13:44:33 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135714&r2=135713&pathrev=135714

Introduce trivial dependency on libatk.

This change adds a call to a libatk function that never gets executed, so
the Linux packaging scripts can be updated to allow a libatk dependency.
This will be followed by a subsequent change that actually implements the
libatk dependency.

BUG=24585
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10380030
------------------------------------------------------------------------
Project Member Comment 16 by bugdroid1@chromium.org, May 9 2012
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=135998

------------------------------------------------------------------------
r135998 | dmazzoni@chromium.org | Wed May 09 00:05:20 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_cocoa.mm?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/content_browser.gypi?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_win.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_gtk.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gtk_preserve_window.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.cc?r1=135998&r2=135997&pathrev=135998
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_win.cc?r1=135998&r2=135997&pathrev=135998
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_mac.mm?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac_unittest.mm?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_widget_host_view_mac.mm?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/dump_accessibility_tree_helper_mac.mm?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_mac.mm?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win_unittest.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_win.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager.cc?r1=135998&r2=135997&pathrev=135998
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=135998&r2=135997&pathrev=135998
 A http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_gtk.cc?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility.h?r1=135998&r2=135997&pathrev=135998
 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_manager_win.cc?r1=135998&r2=135997&pathrev=135998

Add initial GTK web accessibility framework (third attempt).

Previous attempts to land this patch:
1. http://codereview.chromium.org/9839069/
2. http://codereview.chromium.org/10382013/
The previous attempts failed to land due to test failures and problems
depending on libatk with the official Linux build. The build is now resolved,
and the test failures have been fixed by adding an IsNative method to
BrowserAccessibility. Please look carefully at the IsNative calls in the
code; the rest is the same.

Original description:

This enables Linux desktop assistive technology such as the Orca screen 
reader to access the web contents. Builds on the same accessibility stack 
used by Mac & Windows already. 

This change works with Orca now, but it's minimal: all that works is getting 
the correct feedback when you tab through focusable links and controls in 
a webpage. Future changes will add the rest of the support. 

BUG=24585
TEST=Run Chrome on desktop Linux with Orca turned on, tab through links. 
Review URL: https://chromiumcodereview.appspot.com/10382051
------------------------------------------------------------------------
Project Member Comment 17 by bugdroid1@chromium.org, May 10 2012
Labels: merge-merged-1132
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=136438

------------------------------------------------------------------------
r136438 | mmoss@chromium.org | Thu May 10 16:18:37 PDT 2012

Changed paths:
 M http://src.chromium.org/viewvc/chrome/branches/1132/src/content/browser/renderer_host/render_widget_host_view_gtk.cc?r1=136438&r2=136437&pathrev=136438

Merge 135714 - Introduce trivial dependency on libatk.

This change adds a call to a libatk function that never gets executed, so
the Linux packaging scripts can be updated to allow a libatk dependency.
This will be followed by a subsequent change that actually implements the
libatk dependency.

BUG=24585
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10380030

TBR=dmazzoni@chromium.org,dharani@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10377098
------------------------------------------------------------------------
Project Member Comment 18 by bugdroid1@chromium.org, Nov 14 2012
The following revision refers to this bug:
    http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=24486

------------------------------------------------------------------------
r24486 | dmazzoni@google.com | 2012-05-03T19:26:00.507285Z

------------------------------------------------------------------------
Project Member Comment 19 by bugdroid1@chromium.org, Nov 14 2012
The following revision refers to this bug:
    http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=24573

------------------------------------------------------------------------
r24573 | dmazzoni@google.com | 2012-05-07T20:44:14.187464Z

------------------------------------------------------------------------
Project Member Comment 20 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Area-UI -Feature-Accessibility Cr-UI-Accessibility Cr-UI
Project Member Comment 21 by bugdroid1@chromium.org, Jul 31 2013
------------------------------------------------------------------------
r214752 | dmazzoni@chromium.org | 2013-07-31T15:56:00.781087Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.h?r1=214752&r2=214751&pathrev=214752
   M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/accessibility/browser_accessibility_gtk.cc?r1=214752&r2=214751&pathrev=214752

Implement AtkComponent and AtkValue interfaces.

BUG=24585
R=aboxhall@chromium.org

Review URL: https://codereview.chromium.org/21148002
------------------------------------------------------------------------
Labels: Hotlist-Recharge Hotlist-Recharge-Stale
This issue likely requires triage.  The current issue owner maybe inactive (i.e. hasn't fixed an issue in the last 30 days).  It has also not been modified in a year (prior to this update).  Thanks for helping out!

-Anthony
Project Member Comment 23 by sheriffbot@chromium.org, Jun 23 2016
Labels: Hotlist-OpenBugWithCL
A change has landed for this issue, but it's been open for over 6 months. Please review and close it if applicable. If this issue should remain open, remove the "Hotlist-OpenBugWithCL" label. If no action is taken, it will be archived in 30 days.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Hotlist-OpenBugWithCL
This work is not finished. This is a meta-bug for a big feature.
Owner: ----
Status: Available
Unassigning because we're not currently working on it.

Blockedon: 463671
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
To put this in perspective quite often Linux users are developers that are meant to be providing accessibility for the web, however, there isn't really many options to get accessibility right. The aim would be to be able to try and use your web application without using the screen and only a screen reader. However, when you are using webcomponents like Polymer Epiphany doesn't work, Chrome Vox doesn't work and now Chromium doesn't work with Orca. 

I know accessibility isn't the most popular topic, and neither is Linux but this was raised in 2009, surely this can get some traction?
Sign in to add a comment