GNOME Accessibility Team

3.4 - Regressions

Contents

Note: This page has just been started. What is here at the moment is NOT all of the regressions.

This page lists:

the accessibility regressions introduced by other modules, which are present in GNOME 3.x. (Items which are present but are known to NOT be/cause regressions should be on the 3.4 "Issues" page.)
which we feel must be addressed

$/!\$ Team members should:

For those things which we also think really need doing for 3.4, please see our 3.4 "Must Haves" and 3.4 "Nice To Haves" pages

Key Contacts: Benjamin, Matthias
Work Remaining - Updated: 14-October-2011
1. Accessible event.any_data is incorrect for text-removed/text-changed:delete.
  - Impact: Orca users relying upon speech output cannot efficiently delete characters unless they do so from memory
  - Bug(s): 659445 which blocks Orca bug 659235
  - Next Action: Joanie will ping the Key Contacts for assistance, advice.
  - Person(s) Responsible: Benjamin, Joanie
2. Toggling the state of a GtkCheckButton causes accessible window activate and deactivate signals to be emitted.
  - Impact: Orca spews out a lot of irrelevent information each time the user toggles the state of a checkbutton because we think the user has switched windows.
  - Bug(s): 657578
  - Next Action: Joanie will ping the Key Contacts for assistance, advice.
  - Person(s) Responsible: Benjamin, Joanie

Key Contacts: ?
Work Remaining - Updated: 14-October-2011
1. Accessible icon with focus is not correctly reported.
  - Impact: When the user does the 'where am I?' command to obtain his/her present location, Orca cannot provide accurate information.
  - Bug(s): 660599 which blocks Orca bug 660126
  - Next Action: Figure out whom to ping.
  - Person(s) Responsible: None at this time