-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Accessibility by default #7862
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
Comments
I agree with this assessment, this seems like a thoughtful API to build to, both for accessibility and in general. |
If Bevy wants or needs an accessibility SME, I'm happy to step up. I think we may actually be the first general-purpose game engine integrating accessibility into its core (I.e. not a blind person-specific game engine, and not as a third-party plugin.) |
Brilliant. We will discuss this for the next round of SME appointments. |
Actually, the Quorum language (https://quorumlanguage.com/) has a (sorta...) general-purpose game engine built-in, and Andreas Stefik, the lead author/researcher, has published a BSD-licensed C++ library making communicating accessibility-relevant information from the game engine to the operating system easier. That said, Quorum is built on top of Java. That alone can be a disadvantage in games development and the development process with quorum is relatively clunky - no automated recompilimg, for instance. The Quorum Studio IDE, in particular its accessible scene editor, is a boon to blind (or deafblind, like me) programmers, though. I'll be watching this issue with interest. |
Jeez, I'd totally forgotten about Quorum when I suggested that Bevy was the first general-purpose accessible game engine. Granted, it's pretty niche, but I wish it'd taken off more, and at least based on what I've read, it's a great example of making a 3-D game engine and editing environment both blind-accessible and visual. Might be worth us looking more closely into for inspiration of how to make visual editing more accessible in the upcoming editor. Gotta admit, I'm occasionally tempted to abandon Bevy for Quorum even though it is a custom JVM language. It'd be nice for us to aspire to that level of accessibility both for developers and players. :) I can submit a blog post update PR clarifying things a bit if there's interest. I think we should leave the existing claim in, but I'm comfortable giving Quorum the distinction of being the first general-purpose visual-first game engine that made the engine itself accessible. It just sounds like less of a big deal when spelled out like that. :) Thanks for speaking out for Quorum. |
Giving people credit never hurts, especially fellow open-source projects. Besides, Stefik and his team will probably be happy to share experiences and expertise. Still, Bevy's design system speaks to me more than that of the Quorum engine; I'm not talking about any disadvantages of the JVM and garbage collection yet, but the cleanliness of game code encouraged by Bevy's design decision is definitely an advantage. |
Definitely cool with this as an initial step, but I think its very important to resolve this in the near future.
Originally posted by @cart in #6874 (comment)
The text was updated successfully, but these errors were encountered: