SDL2 example doesn't do anything

[Jookia]

Building accesskit-c then the SDL2 example works, but actually running SDL2 gives no output. The screen reader (Orca) doesn't recognize the window exists. Now indow is shown in accerciser.

[Jookia]

0.18.0 works, 0.19.0 onwards seems broken.

[DataTriny]

I can reproduce on OpenSUSE Tumbleweed. Orca seem to get killed when the window pops up.

Our Rust winit examples run without issue on Linux as well as the Windows C example. Not sure what is different.

[DataTriny]

Actually I might not have the same issue because Orca is able to see the window after it restarts. Which desktop environment are you using? Is it Wayland or X11?

On GNOME Wayland I can see another accessibility tree being created for the window roughly at the same time but from GTK and it sends quite a lot of signals. I don't know who is creating this parallel tree at the moment.

[Jookia]

X11 on i3 Feb 2, 2026 05:49:01 Arnold Loubriat ***@***.***>:

…

[Image]*DataTriny* left a comment (AccessKit/accesskit-c#76)[#76 (comment)] Actually I might not have the same issue because Orca is able to see the window after it restarts. Which desktop environment are you using? Is it Wayland or X11? On GNOME Wayland I can see another accessibility tree being created for the window roughly at the same time but from GTK and it sends quite a lot of signals. I don't know who is creating this parallel tree at the moment. — Reply to this email directly, view it on GitHub[#76 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABNHOZ7AZHA6WLVIPM5NR34JZDBVAVCNFSM6AAAAACTM437E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMZRG42DQNRWHE]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/AABNHO535L7TSPBWOGTQOP34JZDBVA5CNFSM6AAAAACTM437E2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTXEMPMD2.gif]

[DataTriny]

0.18.0 works, 0.19.0 onwards seems broken.

@Jookia can you please double check this point? If confirmed, the most relevant change in accesskit_unix 0.18 which is part of accesskit-c 0.19 would be AccessKit/accesskit#628 or maybe AccessKit/accesskit#651.

With Orca running, can you please execute the following?

busctl get-property --user org.a11y.Bus /org/a11y/bus org.a11y.Status IsEnabled
busctl get-property --user org.a11y.Bus /org/a11y/bus org.a11y.Status ScreenReaderEnabled

If both commands return b true, can you please monitor the private AT-SPI bus to see if we call the registry? You can get the address by running:

busctl call --user org.a11y.Bus /org/a11y/bus org.a11y.Bus GetAddress

Then run this before starting the example (make sure to not open other windows while this command is running):

dbus-monitor --address <BUS_ADDRESS> "interface=org.a11y.atspi.Socket"

The expected result is to see one call to the Embed method. Going further require knowledge of the AT-SPI protocol.

Logs from Orca would really help. You can enable them by starting Orca like so:

orca --replace --debug-file orca.out

[Jookia]

I will double check in a few days. I went back and checked I think 0.18.0.is broken too, it is 0.17.0 that works. But I was not doing clean builds so it's possible some dependencies were bleeding over between builds. Feb 3, 2026 06:07:36 Arnold Loubriat ***@***.***>:

…

[Image]*DataTriny* left a comment (AccessKit/accesskit-c#76)[#76 (comment)] 0.18.0 works, 0.19.0 onwards seems broken. @Jookia[https://github.com/Jookia] can you please double check this point? If confirmed, the most relevant change in accesskit_unix 0.18 which is part of accesskit-c 0.19 would be AccessKit/accesskit#628[AccessKit/accesskit#628] or maybe AccessKit/accesskit#651[AccessKit/accesskit#651]. With Orca running, can you please execute the following? busctl get-property --user org.a11y.Bus /org/a11y/bus org.a11y.Status IsEnabled busctl get-property --user org.a11y.Bus /org/a11y/bus org.a11y.Status ScreenReaderEnabled If both commands return *b true*, can you please monitor the private AT-SPI bus to see if we call the registry? You can get the address by running: busctl call --user org.a11y.Bus /org/a11y/bus org.a11y.Bus GetAddress Then run this before starting the example (make sure to not open other windows while this command is running): dbus-monitor --address <BUS_ADDRESS> "interface=org.a11y.atspi.Socket" The expected result is to see one call to the *Embed* method. Going further require knowledge of the AT-SPI protocol. Logs from Orca would really help. You can enable them by starting Orca like so: orca --replace --debug-file orca.out — Reply to this email directly, view it on GitHub[#76 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABNHO2FRPWZ53MU3FKAQFT4J6N7LAVCNFSM6AAAAACTM437E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMZXGEYDAMRSG4]. You are receiving this because you were mentioned. [Tracking image][https://github.com/notifications/beacon/AABNHO4ADBTN7G4CZSNPBLD4J6N7LA5CNFSM6AAAAACTM437E2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTXEWWAMG.gif]

[DataTriny]

There's also 0.17.1 with some updates to the underlying Rust library, please make sure to check it as well for regression. Thanks.

[Jookia]

Hi there, I haven't tried the AccessKit example yet but here's the output of the commands:

jookia@titan:~% pidof orca
735424
jookia@titan:~% busctl get-property --user org.a11y.Bus /org/a11y/bus org.a11y.Status IsEnabled
b true
jookia@titan:~% busctl get-property --user org.a11y.Bus /org/a11y/bus org.a11y.Status ScreenReaderEnabled   (exited 130)
b false

Edit: It looks like I have to run gsettings set org.gnome.desktop.a11y.applications screen-reader-enabled true to get AccessKit to talk to Orca, because ScreenReaderEnabled is a proxy for that key. Running that fixes AccessKit. Is AccessKit only for GNOME screen readers and no other assistive tech?

Edit 2: I looked at Orca's source code and it doesn't touch either of these settings. So this seems like it would break anything non-GNOME like KDE or Xfce too. :\

Edit 3: It looks like Plasma does set this key, but Xfce doesn't read it. Not sure about other DEs.

Edit 4: It seems like this is the behaviour most applications expect. I've had this dumped in my X11 profile for years now:

export GTK_MODULES=gail:atk-bridge
export GNOME_ACCESSIBILITY=1
export QT_ACCESSIBILITY=1
export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
export QTWEBENGINE_ENABLE_LINUX_ACCESSIBILITY=1

I guess they are unifying around gsettings set org.gnome.desktop.a11y.applications screen-reader-enabled true ?