Nice primer on type! However, the tracking example is misleading advice. That body copy is not legible due to the font choice and close tracking. Notice how “darn” becomes “dam” and how much more difficult reading becomes as you zoom out. Generally, messing with tracking is only advisable at display sizes or for all-caps small text, when you may want to increase it.
These are some good points, James — I don’t disagree, but I do think that may not be the job of the screens right above platform doors, at risk of overloading them. Ideally, the whole station environment works together, and passengers could have these doubts confirmed earlier in their journey. In my ideal world, I would have a giant screen with a…
Yes! There was testing that informed the designs in the first place, as well as the current testing that’s taking place in Terminal 8. If there are any areas where these designs don’t work as intended, we’ll make the tweaks before rolling them out to all stations.
Seems like creating a buzzword for no reason. Correct me if I’m missing something, but how is this not just thinking about animation and video in the user interface? How does it not fall under UI, UX, or content (which in my opinion are already splitting hairs and share a ton of overlap?)
Great point that I didn’t even consider — shame on me for accepting that status quo given how many problems there are with the rest of it. Thanks!
Thanks for the feedback! I tried to keep the restrictions of the current technology, though certainly different sized displays would yield all different sorts of likely better designs. The current newest clocks are just computers displaying a webpage so in terms of technical capability they can do pretty much anything within reason.
It’s mostly ridiculous because line-height should always be defined as a unit less number. It’s a ratio of space to characters, so just define it as a number that will be multiplied by the font size. This is a fundamental of web typography that many people miss.