-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Accessibility and visual improvements #110
Comments
@Finnboy94 I will say although those are some suggestions to work with, it is one of the main goals for |
If anything, it sounds like the CSS is the real problem, in my opinion. |
That's very possible, yeah. I'll see if I can find ways to improve it myself, although being blind CSS is not the easiest to work with. |
How are you even reading this is you are blind? You're probably messing with me, but I think you mean colorblind, right? |
Actually no, I am totally blind since birth. I use a screen reading software, more specifically Non-Visual Desktop Access (NVDA) on a Windows 10 machine or, if on my phone, VoiceOver on iOS. |
The automatic refresh causes screen readers to throw keyboard focus to the end of the message list frame. This causes you to lose the current position. As a resolution I think maybe javaScript could be used to have a different update type, maybe even make the updating dynamic so that the messages arrive in real time.
A few sighted users reported that the message list and the buttons in the bar (suck has messages, update chat box etc) are of different size, more specifically the button bar is larger.
Not sure if this is desireable, but I also received a suggestion that the login an dregister be split, so that login is on the front page and registering a different page.
This is what's on my mind right now.
The text was updated successfully, but these errors were encountered: