found using 2002.11.26.04 on 10.2.2. OS X provides some screen reading capabilities via the Speech sys prefs --in this case i noticed that chimera's behavior different from other browsers. setup ----- go to the Spoken User Interface tab located in the Speech system preference. in the "other spoken items" section, select (enable) the "text under the mouse" checkbox. to observe ---------- just hover the mouse pointer over text in UI elements and web content, and listen to your Mac read aloud to you. :) afaict, both tooltips (chrome) and titletips (web content) were *not* spoken aloud in chimera, IE or omniweb. works in chimera ---------------- menus (main and context) navigation & bookmark toolbars window titlebar elements titles in sidebars Prefs toolbar & individual panel/tab elements does NOT work in chimera ------------------------ Prefs main category text (General, Privacy & Security) Pref icons (show all region) items (bookmark links, history entries) in sidebars text in web content area (workaround: select and use Speech Service) titles in browser tabs works in Omniweb ---------------- menus (main and context) navigation toolbar window titlebar elements items and UI elements in drawers (sidebars) Prefs toolbar & individual panel elements Prefs main categories (Basic, Advanced) does NOT work in Omniweb ------------------------ bookmarks toolbar Pref icons (show all region) text in web content area (workaround: select and use Speech Service). IE had very limited capabilities here: screen reading for this feature only seemed to work in these areas: window titlebar elements menubar and context menu items Add (erratically) in the Favorites explorer bar

how tricky would this be to more consistently implement this throughout chimera?

Posting an update with last nights NB and 10.3+: works in Camino ---------------- menus (main and context) navigation & bookmark toolbars window titlebar elements titles in sidebars Prefs toolbar & individual panel/tab elements items (bookmark links, history entries) in manager does NOT work in chimera ------------------------ Prefs main category text (General, Privacy & Security) Pref icons (show all region) text in web content area (workaround: select and use Speech Service) titles in browser tabs

Text in the web content area not being spoken is a gecko/widget-bug. The rest seems to be Camino's fault.

Does the content-area part depend on the Apple Accessibilty stuff (like the Dictionary hover thing in 10.4, bug 301451)?

Yes, you need to implement support for the universal access / accessibility APIs (if nothing is there already), but note that they are not 10.4-only, though there are some new features that are new.

The Core bug is bug 157209.

Support for this has been implemented with bug 352329. Please file individual bugs as needed. You need to build with --enable-accessibility to test it.

So don't we need to add --enable-accessibility to Camino's build settings before we can really call this fixed?

Does that work fix tab titles, too? We shouldn't call this FIXED until we actually use the fix, anyway.

(In reply to comment #8) > So don't we need to add --enable-accessibility to Camino's build settings > before we can really call this fixed? Yeah, that's correct. Would you guys be interested in trying to build with that on? I would love to hear you comments.

There seems to be conflicting reports over whether tab widget titles get spoken. The Dock menu also doesn't get spoken, but I'm not sure if that is our issue or the Dock's....

(In reply to comment #11) > There seems to be conflicting reports over whether tab widget titles get > spoken. > > The Dock menu also doesn't get spoken, but I'm not sure if that is our issue or > the Dock's.... If you're talking about Camino, then both of those are (pretty easily solved) camino issues (not core). The custom tab widget class (in camino) just needs to implement the informal NSAccessibility protocol and respond to such attributes as NSAccessibilityTitleAttribute.

Like I wrote in comment 10. If any of you build with --enable-accessibility and try stuff with it, it helps me a lot. Reassign to default owner since this bug seems to be also about remaining Camino issues (comment 11).

Yeah, this is a bug about problems in Camino chrome; adjusting the summary to better reflect that. I think we should have a separate bug for flipping on --enable-accessibility by default on the trunk at some point (unless it'll be flipped on for everyone at some point) Joel Craig has been building his Intel trunk builds with --enable-accessibility for a few weeks now; I really haven't heard of any issues yet, but cc'ing him so he can file bugs ;)

Thanks Smokey. Let's see what I can add: Menu items are read. However, each item is doubled or tripled in the list with Spoken User Interface turned ON. Navigation buttons, URL and Google bar are read. If only favicons are used on the bookmark bar, only "button" is read. If item on bokmark bar also contains title info, all info is read. Only active tab title is read. Hovering over inactive tab reads active tab info. Window titlebar is only read in certain areas of titlebar (NOT over the actual text). Preferences dialogue and all contents seems to work properly. Dock menu and contents works properly. Opening and closing contextual menu works. Contents of contextual menu is not read. This is using today's home-grown Intel-only build with all OS updates.

Build Succeeded after I disabled --enable-accessibility. Problem cropped up between now and I believe Saturday.

Comment on attachment 260433 [details] build errors That's not at all this bug. If there are build problems, that's a separate bug for the Core accessibility component.

Mass un-setting milestone per 1.6 roadmap. Filter on RemoveRedonkulousBuglist to remove bugspam. Developers: if you have a patch in hand for one of these bugs, you may pull the bug back to 1.6 *at that point*.

This bug is really quite a mess now. The things sairuh filed this on all work now (except the content area, which is Gecko's bug, and can be partly worked around with the Speech Service), so closing WFM. I filed: Bug 410384 – Tab titles are not accessible to VoiceOver Bug 410385 – Downloads aren't accessible to VoiceOver If you find more issues, please file separate bugs.