Skip to content

build: build qtbase with a11y bridge from source#863

Draft
saw-jan wants to merge 1 commit into
mainfrom
build/build-qtbase-with-a11y
Draft

build: build qtbase with a11y bridge from source#863
saw-jan wants to merge 1 commit into
mainfrom
build/build-qtbase-with-a11y

Conversation

@saw-jan

@saw-jan saw-jan commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Partially fixes #860
Do not use qtbase from cache but instead build it from source with a11y and a11y-atspi-bridge features enabled.

Important

The build system MUST have the necessary libraries installed

  • libatspi2.0-dev
  • libdbus-1-dev

To confirm the features, run the following command:

strings <path-to>/lib/libQt6Gui.so | grep -i QSpiAccessibleBridge

Signed-off-by: Saw-jan <saw.jan.grg3e@gmail.com>
@saw-jan saw-jan requested review from TheOneRing and dragotin April 23, 2026 11:56
Comment thread .craft.ini
dev-utils/gtk-doc.ignored = True

#libs/qt6.version = ${Variables:QtVersion}
libs/qt6/qtbase.featureArguments = -DQT_FEATURE_accessibility=ON -DQT_FEATURE_accessibility_atspi_bridge=ON

@saw-jan saw-jan Apr 28, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how can we do it for linux only?

@TheOneRing

Copy link
Copy Markdown
Contributor

As this makes total sense for all of KDE, I'll try to upstream the change and enable accessibility for the KDE Qt packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[A11y] Screen reader cannot read the contents of desktop client

2 participants