[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-accessibility
Subject:    Re: [Kde-accessibility] An accessible Qt? I think not.
From:       Leo Spalteholz <leo.spalteholz () gmail ! com>
Date:       2005-11-16 0:55:15
Message-ID: 7c98fd570511151655h3105cdf9vef465fa192202ba4 () mail ! gmail ! com
[Download RAW message or body]

I've run into something interesting.  Inspecting Skype (which is built
on Qt 3.2), there are no immediately obvious problems.  The menus are
perfect, and even accessible through the tree (using AccExplorer). 
Opera, on the other hand, as well as all the examples that come with
Qt4 are bad, and don't expose most functionality through MSAA.

I wonder if there were some regressions in Qt4, or if Skype did extra
work to support MSAA.

Leo

On 11/15/05, Gary Cramblitt <garycramblitt@comcast.net> wrote:
> On Monday 14 November 2005 08:00 pm, Leo Spalteholz wrote:
> > Specifically for Qt, support is quite poor (although Openoffice is far
> > worse).
>
> Leo responded to me that this is Qt4.  That's very disappointing.  Leo please
> do report these to Trolltech and keep us informed.
>
> I can understand the menu problems you report had you said Qt3.  The QMenuBar
> and QPopupMenu widgets contained the individual menu items in a QMenuData
> structure that (I'm guessing) did not inherit the QAccessible interface.  In
> Qt4, the menus have been unified into a QMenu widget with QAction items.  I
> would have thought QAction would inherit the QAccessible interface and
> provide the accessible information.  Perhaps it is because QAction inherits
> from QObject, not QWidget that Inspect32 doesn't see the accessible info?  Or
> perhaps Inspect32 doesn't know how to ask the QMenu widget for the individual
> menu items?
>
> The listview problems are probably similar issues.  Are you using the
> model/view architecture?
>
> I'm also a bit confused because I had understood there must be an accessible
> plugin installed that intermediates between Qt and Inspect32. ???
>
> My understanding is that oo.org does not support MSAA.  It does support the
> Java Accessibility API and AT-SPI, so it isn't surprising at all that
> Inspect32 would "fail miserably" on oo.org.
>
> --
> Gary Cramblitt (aka PhantomsDad)
> KDE Text-to-Speech Maintainer
> http://accessibility.kde.org/developer/kttsd/index.php
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility@kde.org
> https://mail.kde.org/mailman/listinfo/kde-accessibility
>
_______________________________________________
kde-accessibility mailing list
kde-accessibility@kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
[prev in list] [next in list] [prev in thread] [next in thread]