Name Description Size Coverage
linux -
qaccessible.cpp ! \class QAccessible \brief The QAccessible class provides enums and static functions related to accessibility. \ingroup accessibility \inmodule QtGui This class is part of \l {Accessibility for QWidget Applications}. Accessible applications can be used by people who are not able to use applications by conventional means. The functions in this class are used for communication between accessible applications (also called AT Servers) and accessibility tools (AT Clients), such as screen readers and braille displays. Clients and servers communicate in the following way: \list \li \e{AT Servers} notify the clients about events through calls to the updateAccessibility() function. \li \e{AT Clients} request information about the objects in the server. The QAccessibleInterface class is the core interface, and encapsulates this information in a pure virtual API. Implementations of the interface are provided by Qt through the queryAccessibleInterface() API. \endlist The communication between servers and clients is initialized by the setRootObject() function. Function pointers can be installed to replace or extend the default behavior of the static functions in QAccessible. Qt supports Microsoft Active Accessibility (MSAA), \macos Accessibility, and the Unix/X11 AT-SPI standard. Other backends can be supported using QAccessibleBridge. In the Unix/X11 AT-SPI implementation, applications become accessible when two conditions are met: \list \li org.a11y.Status.IsEnabled DBus property is true \li org.a11y.Status.ScreenReaderEnabled DBus property is true \endlist An alternative to setting the DBus AT-SPI properties is to set the QT_LINUX_ACCESSIBILITY_ALWAYS_ON environment variable. In addition to QAccessible's static functions, Qt offers one generic interface, QAccessibleInterface, that can be used to wrap all widgets and objects (e.g., QPushButton). This single interface provides all the metadata necessary for the assistive technologies. Qt provides implementations of this interface for its built-in widgets as plugins. When you develop custom widgets, you can create custom subclasses of QAccessibleInterface and distribute them as plugins (using QAccessiblePlugin) or compile them into the application. Likewise, Qt's predefined accessibility support can be built as plugin (the default) or directly into the Qt library. The main advantage of using plugins is that the accessibility classes are only loaded into memory if they are actually used; they don't slow down the common case where no assistive technology is being used. Qt also includes two convenience classes, QAccessibleObject and QAccessibleWidget, that inherit from QAccessibleInterface and provide the lowest common denominator of metadata (e.g., widget geometry, window title, basic help text). You can use them as base classes when wrapping your custom QObject or QWidget subclasses. \sa QAccessibleInterface 130064 -
qaccessible.h 23965 -
qaccessible_base.h 15493 -
qaccessiblebridge.cpp ! \class QAccessibleBridge \brief The QAccessibleBridge class is the base class for accessibility back-ends. \internal \ingroup accessibility \inmodule QtWidgets Qt supports Microsoft Active Accessibility (MSAA), \macos Accessibility, and the Unix/X11 AT-SPI standard. By subclassing QAccessibleBridge, you can support other backends than the predefined ones. Currently, custom bridges are only supported on Unix. We might add support for them on other platforms as well if there is enough demand. \sa QAccessible, QAccessibleBridgePlugin 2933 -
qaccessiblebridge.h 1055 -
qaccessiblebridgeutils.cpp 6007 -
qaccessiblebridgeutils_p.h 1249 -
qaccessiblecache.cpp ! \class QAccessibleCache \internal \brief Maintains a cache of accessible interfaces. 7356 -
qaccessiblecache_mac.mm 1685 -
qaccessiblecache_p.h A regular event, used when the object is still alive 3094 -
qaccessiblehelper.cpp This function will return the offset of the '&' in the text that would be preceding the accelerator character. If this text does not have an accelerator, -1 will be returned. 4063 -
qaccessiblehelper_p.h 1780 -
qaccessibleobject.cpp ! \class QAccessibleObject \brief The QAccessibleObject class implements parts of the QAccessibleInterface for QObjects. \ingroup accessibility \inmodule QtGui This class is part of \l {Accessibility for QWidget Applications}. This class is mainly provided for convenience. All subclasses of the QAccessibleInterface that provide implementations of non-widget objects should use this class as their base class. \sa QAccessible, QAccessibleWidget 4557 -
qaccessibleobject.h 1587 -
qaccessibleplugin.cpp ! \class QAccessiblePlugin \inmodule QtGui \brief The QAccessiblePlugin class provides an abstract base class for plugins provinding accessibility information for user interface elements. \ingroup plugins \ingroup accessibility Writing an accessibility plugin is achieved by subclassing this base class, reimplementing the pure virtual function create(), and exporting the class with the Q_PLUGIN_METADATA() macro. \sa {How to Create Qt Plugins} 1521 -
qaccessibleplugin.h 839 -
qaccessiblewindow.cpp Accessibility interface for a QWindow. Reports the window itself, with the window's child QWindows as its children, so that content Qt hosts in a child window is reachable even on a platform bridge that does not know about native windows. A window reaches the accessibility tree only when concrete QWindow subclasses opt in, by registering an accessible factory, and implementing accessibleRoot(). A plain QWindow does not do this, which keeps Qt's own implementation-detail windows out of the tree. The node reports window(). A bridge that does know about native windows reads it to find the native handle, and substitutes that handle for the node, in which case the native element supplies its own children. 5152 -
qaccessiblewindow_p.h 1423 -
qplatformaccessibility.cpp accessiblebridge plugin discovery stuff 3246 -
qplatformaccessibility.h 1223 -