-
Notifications
You must be signed in to change notification settings - Fork 5
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
User reported issue: student who is color blind cannot differentiate atoms/molecules. #149
Comments
@oliver-phet it would be helpful to get more specific feedback about which atoms are hard to differentiate. I played several different levels and compared the various colorblind preview options, and I'm not immediately seeing any issues. The levels are randomly generated, however, so it's certainly possible that there are some problematic combinations. |
I reviewed the possible challenges and confirmed that chlorine (green) is never paired with oxygen (red).
None of the colorblind previews (pasted in below) show issues with white atoms and those of other colors. Additionally, the white atoms represent Hydrogen, which is always significantly smaller than the other atoms. So even if the colors are hard to distinguish, the size difference is significant. I'm not trying to invalidate this student's experience, but it's possible that there is some other issue. I'm not sure what we can do about this, short of some sort of high contrast mode like we have in Build an Atom. I'll assign to @kathy-phet to prioritize. |
Deciding on better colors would probably be easier if they could be tweaked using the Color Editor. But making the atom and molecule colors dynamic would be a big lift -- unless you were OK with the colors not updating until the Game challenge changes. It would also require redoing the memory tests in #155, since making colors dynamic has a high probability of introducing memory leaks (due to listeners added to ProfileColorProperty instances). |
Assigning to @arouinfar for now, though this may need input by the accessibility team.
The text was updated successfully, but these errors were encountered: