New issue
Advanced search Search tips

Issue 635627 link

Starred by 2 users
Status: Archived
Owner:
dtseng@chromium.org
Closed: Aug 2017
Cc:
dtseng@chromium.org
lpalmaro@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
Team-Accessibility



Sign in to add a comment

ChromeVox should read misspelled markers

Project Member Reported by dtseng@chromium.org, Aug 8 2016 
Tracks this feature

Comment 1 by dtseng@chromium.org, Aug 8 2016

Blockedon: 635630

Comment 2 by dtseng@chromium.org, Aug 11 2016

Summary: ChromeVox should read misspelled markers (was: ChromeVox should read text markers)

Comment 3 by lpalmaro@chromium.org, Aug 19 2016

Labels: Phase3

Comment 4 by dtseng@chromium.org, Oct 25 2016

Labels: -Phase3 phase4

Comment 5 by dmazz...@chromium.org, Mar 6 2017

Labels: NewComponent-Accessibility-ChromeVox

Comment 6 by dmazz...@chromium.org, Mar 27 2017

Labels: NewComponent-Accessibility

Comment 7 by dmazz...@chromium.org, Apr 21 2017

Components: UI>Accessibility>ChromeVox
Labels: -newcomponent-accessibility -newcomponent-accessibility-chromevox

Comment 8 by dmazz...@chromium.org, Apr 21 2017

Components: -UI>Accessibility

Comment 9 by dtseng@chromium.org, Aug 7 2017

Status: fixed (was: Started)

Comment 10 by leberly@chromium.org, Oct 18 2017

Blockedon: -635630

Comment 11 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)
►

Sign in to add a comment