-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Accessibility support? #388
Comments
@ethindp I'm afraid this is really out-of-scope for raygui project. AccessKit seems to be a lower level library, like GLFW (that is integrated into raylib). |
@raysan5 May I ask why such a critical feature like this would be out-of-scope? AccessKit might not be the most high-level library but it's much higher level than the OS accessibility abstractions (UIA, AT-SPI2, whatever MacOS implements). |
@ethindp Mostly two reasons:
Thanks for your comprehension. |
@ethindp Note that raygui is a free and open source project. If you think that feature is crucial for your target project, you can fork it and implement it yourself. |
Ah okay, thank you for your explanations. |
I'm not sure how easy this would be for an immediate-mode UI, but I thought I'd ask. There is a library called AccessKit that simplifies this task a lot and abstracts away the platform-specific things you'd need to normally use. The API documentation is mostly in Rust (as the library is written in Rust) but there are C examples. I can help if we can figure out the problem of "it's an immediate-mode UI", but it would be amazing if this could be done. A prerequisite is issue #385 as it will be a requirement for screen readers and individuals who cannot use the mouse.
The text was updated successfully, but these errors were encountered: