Opened 15 years ago
Closed 14 years ago
#39 closed task (fixed)
Port QAccessible
| Reported by: | Dmitry A. Kuminov | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | Qt 4.6.2 |
| Component: | QtGui | Version: | 4.5.1 Beta 1 |
| Severity: | highest | Keywords: | |
| Cc: |
Description
Provide the OS/2 version of the QAccessible class.
Change History (3)
comment:1 Changed 14 years ago by
| Milestone: | Qt Enhanced → Qt 4.6.1 |
|---|---|
| Severity: | → low |
comment:2 Changed 14 years ago by
| Priority: | major → blocker |
|---|---|
| Severity: | low → highest |
comment:3 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
It turned out that we only need to enable the compilation of the accessible code, no patches are necessary. On OS/2, we use the Unix implementation of QAccessible which redirects all notifications to registered QAccessibleBridge instances (implemented as plugins through QAccessibleBridgePlugin which are searched in the $PLUGIN_DIR/accessiblebridge directory). Note that this is only done if the QT_ACCESSIBILITY is set to 1, otherwise accessibility is a complete no-op.
Note also that the current Qt source bundle provides no QAccessibleBridge/QAccessibleBridgePlugin implementations. An experimental one is available at svn://labs.trolltech.com/svn/accessibility/qdbusbridge though.
So, the above means that we've actually got quite a working QAccessible implementation, not a dummy one, only that we don't have any QAccessibleBridge plugins for OS/2 yet. It's rather easy to create one if somebody really wants to provide some level of accessibility on OS/2 (e.g. add support for the screen reader to Qt applications) -- the interfaces are simple.
OS/2 doesn't have any well defined accessibility support so it is going to be a dummy implementation which should be not difficult.
Taking into account that printing through CUPS went little bit faster than planned I think it makes sense to complete this ticket for 4.6.1: it turns out that applications that use accessibility features are not that rare and #adding ifndef QT_NO_feature to the sources of these applications to make them build on OS/2 is not very convenient.