-
Notifications
You must be signed in to change notification settings - Fork 0
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
Experiment with padding and font size #4
Comments
I put my comment on the other PR. It should have been here... |
I'd agree the current font size, especially the labels one, is too small. Also, a general trend in the WordPress stylesheet is to don't take advantage of the styles cascading, and that's shame 😞 Personally, I'm a bit bothered by some fields (url) using a different font face. I'd like to see always the same font. In the original design by M. Arestad, the font hierarchy was a bit different: Personally, I think white space and typography is key in this case, and we don't necessarily need bold. But I'm not a designer 🙂 |
@joyously for this prototype purpose, changing the entire way WordPress does hierarchy is out of scope. I do not also agree px is the best, but you can't just pop a rem/em/percentage in without looking at the entire hierarchy. In saying that, it totally is a near future debate and resolution WordPress will go through. Its not for this plugin though. @afercia I think overall we went too small in that style, as we are inferring not following to rule that design. I would +1 the same font, lets do that. I do feel we need bold or at least to test with or without bold. I am super keen our prototype doesn't get hung up on a typography debate, those can be had some other day. Its exciting to get this in front of people over spinning wheels on that. Lets do the MVP on this styling wise. |
When I mentioned accessibility concerns, I was not thinking of browser's ability to zoom, which is not much of a problem any more, but instead a friend with such a problem seeing that he had to set his screen resolution in WIndows really small so that everything would be big enough for him to read it. People with visual problems benefit from using a percentage on the body, so that it is relative to what they set as default in their browser options. Then everything else should be in ems, so it is relative to its parent. If you use 14px, I'll say it's small, and the guy with a vision problem can't even see it (setting browser default to 20px or higher). |
You can also localize your hierarchy. |
As this as a prototoype and type soup isn't tasty, that wouldn't be a good idea right now. This issue wasn't about this, so if we can lets get back on track. |
@joyously yep, I come from an era when the recommendation was to set |
@karmatosed Do I understand correctly that the "call-to-action" here is making the labels |
I changed the font-size of the field titles to 14px (see 07a244c). Let's close this one, and use more specific issues for any future work on design and layout. |
Margin/padding should be figured out:
Furthermore font-size should be figured out:
<label>
,<legend>
or<span>
)The text was updated successfully, but these errors were encountered: