This is a spin-off bug from bug 561660. There it was pointed out that when navigating amongst objects via structural navigation, it may be desirable to hear the role information at the end, whereas when navigating with other methods hearing that information first might be preferable.

Independent of the method of navigation (and the aforementioned bug), users on the Orca list have requested that certain roles (e.g. link) be spoken before the link rather than after.

In addition, what about flat review? Presumably it should be customizable too. Plus, a user potentially might want the presentation of role information to be different from that in focus tracking mode.

And there's bug 520595 in which it has been requested that for users with learning disabilities no context (including role information) should be spoken.

We could, of course, take this to the extreme and say that for every mode of navigation a user should be able to customize if/when and where accessible role information be presented on a *per role basis.* I propose we don't do that. :-) However, I do think it is worth considering the implementation of the following:

* Speak no role information
* Speak role information at the beginning
* Speak role information at the end

and to make this configurable for:

* focus tracking mode
* flat review
* structural navigation

I also propose that *for now* the customization be kept out of the UI. (In other words, users interested in changing Orca's behavior would need to edit their orca-customizations.py and/or app-settings file(s). Depending on user feedback on the overall functionality, we can open a new RFE for adding the option(s) to the UI. Besides, right now we're under string and UI freeze.... :-)