Issue 703277 link

Starred by 1 user

Issue metadata

Status:	Assigned
Owner:	█ nek...@chromium.org Last visit > 30 days ago
Components:	UI>Accessibility>Compatibility
EstimatedDays:	----
NextAction:	----
OS:	Windows
Pri:	1
Type:	Bug
a11y-secondary
Team-Accessibility

Merge the ScreenReader and HTML accessibility modes on Windows

Project Member Reported by nek...@chromium.org, Mar 20 2017

Issue description

It's hard to create a screen reader only mode that doesn't contain at least some HTML attributes on Windows.

Comment 1 by dmazz...@chromium.org, Mar 21 2017

Labels: -Pri-3 Pri-1

Nektarios, could you file a bug for the underlying NVDA & JAWS issues with not having the tag name? We could consider merging this fix since it's small and safe

Project Member

Comment 2 by bugdroid1@chromium.org, Mar 21 2017

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

commit 20bfdecc5f865755ad8b8a18fdc9fd3bac161fca
Author: nektar <nektar@chromium.org>
Date: Tue Mar 21 16:52:51 2017

Merges the |kHTML| and |kScreenReader| AccessibilityModes on Windows.

Unfortunately there is no easy way to separate the HTML and ScreenReader accessibility modes on Windows.
HTML mode includes HTML tag name, HTML attributes and inner HTML for math tags.
However, screen readers rely on some of the above for correct functioning: For example, the HTML tag name is used in some IA2 roles. Input fields expose their type attribute.
Unless we create a new EnhancedScreenReader mode only for Windows, it's hard to separate the two existing modes.
BUG=703277
R=dmazzoni@chromium.org, aleventhal@chromium.org

Review-Url: https://codereview.chromium.org/2765533002
Cr-Commit-Position: refs/heads/master@{#458440}

[modify] https://crrev.com/20bfdecc5f865755ad8b8a18fdc9fd3bac161fca/content/browser/accessibility/browser_accessibility_win.cc