Although fluid typography as a concept solves a lot of issues with the wide array of available device screen sizes, the current implementation seems to have a negative impact on accessibility. Some browsers do not support it. Some cases in some browsers, users can not adjust the font size. Using screen width calculations overrides the user's default font size settings etc. After weighing up the pros and cons of fluid typography, I do not recommend that we implement it at this stage. We might be able to look into this again once the accessibility issues have been fixed.
We want to look into fluid typography and see the pros and cons so we can decide if we want to implement it.
Due to the growing number of screen resolutions, website content is required to be implemented responsively so users can access the content in various devices. However, it can be difficult to have smooth responsive typography that will work perfectly with each screen resolution due to the way breakpoints work. As a result, we want to investigate fluid typography, a mathematic formula that can be added into SCSS/ CSS which would allow the content to change sizes according to different screen widths.
This would allow us to implement a single set of typography settings where otherwise we might have many.
Fluid Typography is a way to scale font-size according to the width of the viewport. Look at Fluid Typography for more details and sample. There are several more versions which can be found on Simplified Fluid Typography or The State of Fluid Web Typography.
An example of a fluid typography formula. It calculates the font size accordingly with the view port size.
Comparing with Lens implementation:
Our current implementation is using a typeset, where we set our font size, with breakpoint attributes to control which typeset shows on which breakpoints.
A sample website that has implemented the fluid typography
Fluid typography has been implemented in a variety of sites covering a wide range of topics and industries. The following are the breakpoints and typography settings for the Invision site which is a good example of fluid typography in a production website.
|Breakpoints||Type of content||Font size||Line heights|
|medium 400-799||h1||calc(32px + (0 * (100vw – 400px)) / 399)||calc(44px + (0 * (100vw – 400px)) / 399)|
|h2||calc(24px + (0 * (100vw – 400px)) / 399)||calc(36px + (0 * (100vw – 400px)) / 399)|
|h3||calc(20px + (0 * (100vw – 400px)) / 399)||calc(32px + (0 * (100vw – 400px)) / 399)|
|p||calc(16px + (0 * (100vw – 400px)) / 399)||calc(28px + (0 * (100vw – 400px)) / 399)|
|large 800-1599||h1||calc(32px + (12 * (100vw – 800px)) / 799)||calc(44px + (12 * (100vw – 800px)) / 799)|
|h2||calc(24px + (12 * (100vw – 800px)) / 799)||calc(36px + (12 * (100vw – 800px)) / 799)|
|h3||calc(20px + (12 * (100vw – 800px)) / 799)||calc(32px + (12 * (100vw – 800px)) / 799)|
|p||calc(16px + (12 * (100vw – 800px)) / 799)||calc(28px + (12 * (100vw – 800px)) / 799)|
|Extra large 1600 +||h1||56||78|
If we would like to implement fluid typography, we will need to design a similar set of values including the viewport size and the font sizes of all types of content. Designing a new collection of typography settings across multiple breakpoints and which look good across all content types will require significant design resource.
- It allows us to set only maximum and minimum font size for each type of content.
- It automatically calculates the font size and line height according to the width of the viewport.
Firefox browser does not support this yet. An alternative solution for this is to add a Linear scaling between 2 font sizes using calc and vw to support it.
- Big effect on accessibility: Matej Latin from The State of Fluid Web Typography stated "My problem with all of the fluid web typography techniques is that they all override user’s default font size set in the browser (from my tests, this was only the case with Chrome). And in some cases and in some browsers, the font size can’t be resized by the user because the viewport units are used. This means that none of these solutions is completely compliant from the accessibility point of view." Although, this seems to be seen only on Chrome, but a very large group of our users are using it.