Skip to content
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

ARIA toggle buttons are not conveyed properly when using Firefox #1867

Closed
nvaccessAuto opened this issue Oct 27, 2011 · 3 comments
Closed

ARIA toggle buttons are not conveyed properly when using Firefox #1867

nvaccessAuto opened this issue Oct 27, 2011 · 3 comments

Comments

@nvaccessAuto
Copy link

Reported by bgaraventa on 2011-10-27 17:53
When viewing ARIA toggle buttons (with role=button and aria-pressed=true/false) using NVDA in the latest version of Firefox, toggle buttons are identified as clickable, and no role or state is
identified. Strangely enough it works properly when viewing it in IE, which is usually the other way around.

An example of this can be found at
http://whatsock.com/
where all of the navigation links such as Overview, Accessibility, and so on are ARIA toggle buttons.

@nvaccessAuto
Copy link
Author

Comment 1 by Ahiiron (in reply to comment description) on 2011-10-27 19:09
Replying to bgaraventa:

When viewing ARIA toggle buttons (with role=button and aria-pressed=true/false) using NVDA in the latest version of Firefox, toggle buttons are identified as clickable, and no role or state is

identified. Strangely enough it works properly when viewing it in IE, which is usually the other way around.

An example of this can be found at

http://whatsock.com/

where all of the navigation links such as Overview, Accessibility, and so on are ARIA toggle buttons.

Using Nightly 32bit, this is interesting. The buttons say "pressed not checked" when activated, but just "not checked" when they aren't. How should this content really be spoken, pressed/not pressed, or checked/unchecked?

@nvaccessAuto
Copy link
Author

Comment 2 by bgaraventa on 2011-10-27 19:32
I'd recommend omitting the state when not pressed, and just include the active state when active. E.G. announce "toggle button" as the role, and then when active, announce "toggle button pressed"

Definitely don't use the word "checked" however, since this implies a checkbox or radio button metaphor that doesn't apply when using a button that is pressed or not pressed.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2011-10-27 22:06
Duplicate of #1757 (see the last comment). Fixed in 2011.3.
Changes:
Added labels: duplicate
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant