We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently Pyflow communicates information about the state of a block only through color.
For inclusivity reasons we should always communicate information through more than one way (symbols, animation, texture...).
In general we should follow inclusivity guidelines when designing an object, here is a good example: https://docs.microsoft.com/en-us/windows/uwp/gaming/accessibility-for-games
The text was updated successfully, but these errors were encountered:
Are you conflating the terms inclusivity and accessibility? The link to Microsoft's accessibility for games is great. Thank you.
I would add that efforts could be made to make features of PyFlow more discoverable as well.
Sorry, something went wrong.
No branches or pull requests
Currently Pyflow communicates information about the state of a block only through color.
For inclusivity reasons we should always communicate information through more than one way (symbols, animation, texture...).
In general we should follow inclusivity guidelines when designing an object, here is a good example:
https://docs.microsoft.com/en-us/windows/uwp/gaming/accessibility-for-games
The text was updated successfully, but these errors were encountered: