New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Chrome: Label not rendered in browse mode for radio buttons and check boxes #1562
Comments
Comment 1 by ateu on 2011-07-30 14:46 |
Comment 2 by ateu on 2011-10-24 17:16 |
Comment 3 by Ahiiron (in reply to comment 2) on 2011-10-24 19:47
These bugs are known, have a look at the following and please comment and vote so they gain higher priority. Not all text on webpages seen by NVDA: |
Comment 4 by ateu on 2011-11-11 18:08 I'd really like hear Mick or Jamie about it: Are they really problems due to a chrome bug? |
Comment 5 by ateu on 2012-03-07 16:38 I'd like you investigate the problem with reading chekbox content and announce of title. Furgive me if I am wrong. Thanks |
Comment 6 by ateu on 2012-08-03 22:52 |
Comment 7 by jteh on 2012-08-04 10:23 |
Comment 8 by ateu on 2012-08-19 14:16 In chrome 16 was possible read the title with NVDA+T. |
Comment 9 by jteh (in reply to comment 8) on 2012-08-19 23:01
Technical: IAccessible::accName on the Chrome application accessible no longer includes the title of the document, even though its window accessible still does. |
Comment 10 by jteh on 2012-08-31 06:18 |
Comment 11 by ateu on 2012-09-25 10:21 Is it possible use MSHTML or Webkit instead of geckoIa2 in chrome app module? |
Comment 12 by jteh on 2012-09-25 10:31 |
Comment 14 by jteh on 2012-10-15 04:18 I'm narrowing the scope of this ticket to just this one issue. Regarding further Chrome issues, Chrome uses IAccessible2, as does Firefox, so it should be exposing content in pretty much the same way. Therefore, any remaining issues are almost certainly due to issues in Chrome, not NVDA. Unless you have reason to suspect otherwise, please file these as bugs against Chrome. |
Comment 15 by ateu on 2012-10-16 15:17 |
Comment 16 by jteh on 2012-10-16 23:16 |
Comment 17 by ateu (in reply to comment 7) on 2013-02-23 18:41
Are you sure jaws uses different APIs for chrome and firefox?
|
Comment 18 by jteh on 2013-02-24 00:59 |
Comment 19 by ateu (in reply to comment 18) on 2013-02-24 01:21
I'm sorry. Now I understud. |
Comment 22 by jteh on 2013-11-06 05:41 |
Comment 23 by James Teh <jamie@... on 2013-11-06 05:42
|
Comment 24 by James Teh <jamie@... on 2013-11-06 05:43
Changes:
|
Comment 25 by James Teh <jamie@... on 2013-11-26 22:44
Changes:
|
Comment 26 by jteh on 2013-11-26 23:04 |
Attachment home-icon.gif added by reanim888 on 2014-10-26 12:02 |
Reported by ateu on 2011-06-13 00:22
Hello,
I know all Google Chrome accessibility problems. But thise which here I'll describe, I think it ccan be fixed, becose I have been compared using others screen readers, like system Access and Jaws 12.
NVDA anounce headins twice when h is pressed in brows mode.
This is an older problem.
It's not possible read the typed content in the adressbar and some editfields.
When navigating using arrow keys, NVDA doesn't reads the text of checkboxes.
forgive me if i'm wrong and it cannot be fixed.
Blocking #3569
The text was updated successfully, but these errors were encountered: