You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by MarcoZ on 2010-04-06 07:28
Followup to MozBug551684: When a widget, button, heading or the like, that can be expanded or collapsed, changes state upon a key press, NVDA should notify the user automatically. The state change is reflected int he virtual buffer when arrowing away and back, but not when changing it directly. Should work similarly to checking/unchecking checkboxes.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2010-05-18 06:10
While we may consider implementing this, I believe the correct solution in most cases is for the element to be focusable. If it changes state when activated, it is clearly an interactive element. This does not necessarily mean it should be in the tab order.
Changes:
Milestone changed from 2010.2 to 2010.3
Reported by MarcoZ on 2010-04-06 07:28
Followup to MozBug551684: When a widget, button, heading or the like, that can be expanded or collapsed, changes state upon a key press, NVDA should notify the user automatically. The state change is reflected int he virtual buffer when arrowing away and back, but not when changing it directly. Should work similarly to checking/unchecking checkboxes.
The text was updated successfully, but these errors were encountered: