KMail messages are caret navigable when being composed (of course). But this does not seem to be the case for existing messages. Making all messages caret navigable improves accessibility: * Text selection without a mouse * Message access for users who are blind With respect to the latter, much work has been done recently in the area of Qt accessibility [1] and, as a result, Orca users are beginning to use KDE apps in the GNOME desktop. Unfortunately KMail will not be an option until existing/received messages are caret navigable. [1] http://userbase.kde.org/Accessibility/Getting_Started
Will test it. I never tested a11y in kmail
Just need info how it works ? I compiled atspi-2 and qt-at-spi I exported export QT_ACCESSIBILITY=1 and start app but I have: qt-at-spi/examples/calculator$ ./calculator Qt at-spi: error getting the accessibility dbus address: "The name org.a11y.Bus was not provided by any .service files" Accessibility DBus not found. Falling back to session bus. Registered DEC: true Error in contacting registry "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.a11y.atspi.Registry was not provided by any .service files" Could not query active accessibility event listeners. Registered event listener change listener: true FIXME: handle dialog end. Perhaps you have more info about it ? Perhaps I need to install some apps (at-spi or orca) don't know thanks for infos
Actually, in this particular case, you don't actually need to get Orca, at-spi2, etc. because what is being requested doesn't use those things. To put this bug another way -- perhaps the way I should have put it in the first place (apologies): People should be able to arrow around in the email messages they receive just like they can arrow around in Kate. I should be able to select the text in messages I receive using the keyboard and not the mouse -- without using Orca and without having at-spi2. In several GNOME applications (including Evolution), this can be accomplished by pressing F7 to toggle caret navigation. Having said that, *if* people can arrow around in the messages like they can in Kate, and *if* we get the right AT-SPI2 events from qt-at-spi as a result, *then* an Orca user should be able to read a message that way. And that would be extremely cool. :) Sorry for any confusion! And thank you so much for your interest!!
Hi Laurent, in order to get the accessibility to work you need either Orca or Accerciser running. But as Joanie said, that's unrelated in this case.
Ok thanks for infos. I look at and qtwebkit doesn't support it. We will wait until it supports it but it will great to have it.
Git commit 968379ebd14661d9d674d03c9833221e3e86ec7e by Montel Laurent. Committed on 19/11/2012 at 13:02. Pushed by mlaurent into branch 'master'. Fix Bug 297867 - [a11y] Existing/received messages should be caret navigable Needs QtWebKit-2.3 FIXED-IN: 4.10 M +19 -0 messageviewer/viewer_p.cpp M +2 -1 messageviewer/viewer_p.h http://commits.kde.org/kdepim/968379ebd14661d9d674d03c9833221e3e86ec7e