Issue metadata
Sign in to add a comment
|
ChromeVox Next doesn't speak states / properties of links |
||||||||||||||||||||||
Issue descriptionIt's legal for a link to have aria-expanded on it, but ChromeVox Next doesn't announce it. The output rule for "link" doesn't include state. I think that the output rule should always include state unless there's a good reason for it not to. It'd be easier to have ChromeVox speak everything legal and then cut back on verbosity when it's annoying rather than the current default where it's leaving things out and we get bug reports about things missing.
,
Sep 20 2016
We should be enforcing all of those in Blink, though...
,
Sep 20 2016
,
Sep 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/807f7aaa0a7986dd91089305dcc626d09f197553 commit 807f7aaa0a7986dd91089305dcc626d09f197553 Author: dtseng <dtseng@chromium.org> Date: Thu Sep 22 19:38:20 2016 Update link output rule. BUG= 648615 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2358603002 Cr-Commit-Position: refs/heads/master@{#420428} [modify] https://crrev.com/807f7aaa0a7986dd91089305dcc626d09f197553/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js [modify] https://crrev.com/807f7aaa0a7986dd91089305dcc626d09f197553/chrome/browser/resources/chromeos/chromevox/cvox2/background/output_test.extjs
,
Sep 23 2016
,
Sep 23 2016
For the record, the bits are not really enforced by Blink. For example, a client would have to have knowledge of a toggle button taking the |pressed| state; when not present, the client would need to interpret it as "not pressed" rather than undefined. The conclusion was to try and make Blink publish a json-formatted derivation of the rules for Aria.
,
Sep 23 2016
,
Oct 13 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Sep 20 2016