-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Optionally include higher contrast colour scheme #2300
Comments
I've noticed that text kinda thinner, which make harder to keep focus on main chat as other elements seems same size and low contrast. Left panel is suppose to be visible separation but it feels like its part of chat. Same goes for usernames making them grey text make it worse, should be same color but bold, like in slack and many irc apps, especially when we don't have avatar generation(random image if nothing set) you can easily lost track in busy room. Also not sure why time is hidden by default for all messages but last one, making user unnecessary move mouse just to see time of message. These small things make it overall low contrast and harder to keep focus on main content as your eyes keep cling for some UI elements instead chat. I know some stuff is personal preference but I've tried to be constructive about it. |
Related to #1635 |
+1 the font is very light and makes the app hard to use |
I would happy to see more darkened default colors for the meanwhile. |
PRs for contrasty themes would be enormously appreciated. https://github.com/vector-im/riot-web/blob/master/docs/theming.md is the doc of how to add themes. |
I hunted down this github just to cosign that the contrast ratios are way too low and it's super inaccessible. was unable to keep using for more than an hour due to eye strain. especially in dark mode i couldn't even see the unlocked icon. https://imgur.com/a/y9mmp use this contrast checking tool: http://webaim.org/resources/contrastchecker/ you want a 4.5:1 ratio |
plus one to yiskah, i also cant really tell when a room has new messages due to the contrast issue |
i'm not a huge css coder but i'll see if i can do anything about it myself, later tonight or tomorrow |
Are there any naming conventions or guidelines for theme names?
…On Mar 10, 2017 3:19 PM, "hoodie" ***@***.***> wrote:
i'm not a huge css coder but i'll see if i can do anything about it
myself, later tonight or tomorrow
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2300 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGLNG3LCVJgSG6ZslbQ8Mu0NSzRdJZSLks5rkdqbgaJpZM4KBEib>
.
|
Are there any naming conventions or guidelines for theme names?
no; i'd suggest light-contrasty and dark-contrasty :)
|
Uploaded a pull request, but probably best to ignore for now. Allan Day
and I are working on some further refinements to the design. Visit
#designUX on Matrix for screenshots.
On Mar 10, 2017 4:57 PM, "Matthew Hodgson" ***@***.***> wrote:
Are there any naming conventions or guidelines for theme names?
no; i'd suggest light-contrasty and dark-contrasty :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2300 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGLNG-VDJPPGsUPc8ins7JKiwC6oztQNks5rkfF-gaJpZM4KBEib>
.
|
Just resubmitted PR for light high contrast theme, incorporating feedback from graphic designer Alan Day. On to dark high contrast theme next. |
Related: matrix-org/matrix-react-sdk#7036 |
This can probably be closed now that we have matrix-org/matrix-react-sdk#7036 |
I could include a screenshot here, but I guess you all know what Vector / Riot looks like :) Comparing it to Slack, the color contrast is pretty low and is straining my eyes a bit. That goes mainly for the UI bits, but even the main chat message text is
#454545
, whereas Slack's is#2c2d30
. The left sidebar is worse though, with its grey text on light green background. Any chance we could get more contrast as a default?The text was updated successfully, but these errors were encountered: