At the time of writing, support for screenreaders is not very good on desktop platforms for Compose. It does [work out of the box on macOS](https://github.com/JetBrains/compose-jb/issues/1366#issuecomment-962919016), is [being worked on for Windows](https://github.com/JetBrains/compose-jb/issues/1344) and the outlook for screenreader support on Linux [is not that promising](https://github.com/JetBrains/compose-jb/issues/1366#issuecomment-992295089).
At the time of writing, support for screenreaders is not very good on desktop platforms for Compose. There is [a page concerning Accessibility](https://github.com/JetBrains/compose-jb/tree/master/tutorials/Accessibility) in the Compose repository. Screenreaders [work out of the box on macOS](https://github.com/JetBrains/compose-jb/issues/1366#issuecomment-962919016), it is [being worked on for Windows](https://github.com/JetBrains/compose-jb/issues/1344) and the outlook for screenreader support on Linux [is not that promising](https://github.com/JetBrains/compose-jb/issues/1366#issuecomment-992295089).
Even though screenreaders do work "out of the box" on macOS, many things don't work quite as expected yet, which is probably more Compose's fault than anyone other's. @ialokim has opened a [bunch of tickets](https://github.com/JetBrains/compose-jb/issues/created_by/ialokim) on the Compose repository already, some of them about the screenreader problems, however at the time of writing this, they all await further action from the core team.
Even though screenreaders do work "out of the box" on macOS, many things don't work quite as expected yet, which is probably more Compose's fault than anyone other's. @ialokim has opened a [bunch of tickets](https://github.com/JetBrains/compose-jb/issues/created_by/ialokim) on the Compose repository already, some of them about the screenreader problems, however at the time of writing this, they all await further action from the core team.
