New issue
Advanced search Search tips

Issue 707927 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

[Braille] Issues when composing emails with braille

Project Member Reported by lpalmaro@chromium.org, Apr 3 2017

Issue description

Chrome Version: 59.0.3055.0
OS: Chrome

When attempting to compose an email, running into a few issues:
1) Not clear how to create an @ sign in the To field. 
2) Can't seem to tab between fields using the braille display 
3) Can't seem to edit the draft properly using only the braille display 


 
Labels: phase4

Comment 2 by dtseng@chromium.org, Apr 12 2017

1. see  crbug.com/707933 . With that bug fixed, a user that encounters either an email or url text field will automatically be switched to an 8-dot braille table of the user's choice. In U.S. english comptuer braille, the @ sign is written as dots 4-7. To input an @ sign, these keys need to be pressed together.
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 12 2017

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

commit 72bb94a66c02d96c6a4b258ce7e8c5ebb0272273
Author: dtseng <dtseng@chromium.org>
Date: Wed Apr 12 22:10:01 2017

Ignore unknown focusable nodes if they have children

BUG=710892, 707927 
TEST=navigate by object in Gmail's compose view. Verify that object navigation doesn't skip the "unknown" node which contains the contents of the form (e.g. to, from, etc). Also, verify that ChromeVox never lands on the unknown node directly and does not mention it in ancestry summarization.

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

[modify] https://crrev.com/72bb94a66c02d96c6a4b258ce7e8c5ebb0272273/chrome/browser/resources/chromeos/chromevox/cvox2/background/automation_predicate.js

Project Member

Comment 4 by bugdroid1@chromium.org, Apr 18 2017

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

commit d8bfbee9bffdb2827fc28d84dc44c13c349ce317
Author: dtseng <dtseng@chromium.org>
Date: Tue Apr 18 14:28:16 2017

Improve Learn Mode for braille

- output dots ... chord, when we don't have a mapping and a user presses a chord combination
- when a user types a dot pattern, back-translate the pattern using the current braille table and output.
For example, if a user presses dot 4 in English computer braille, they will hear "@".
- when a user types a chord that maps to a command or modifier, they will receive that as output.
For example, "control" (dots 2-5 chord), "backspace" (dot 7 chord)

TEST=open Learn Mode. Press various braille keys.
BUG= 707927 , 707940 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

[modify] https://crrev.com/d8bfbee9bffdb2827fc28d84dc44c13c349ce317/chrome/browser/resources/chromeos/chromevox/chromevox/background/kbexplorer.js

Comment 5 by dtseng@chromium.org, Apr 18 2017

Owner: lpalmaro@chromium.org
Status: fixed (was: Assigned)
This should be fixed; please verify.

Comment 6 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 7 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61
Status: Verified (was: Fixed)

Sign in to add a comment