> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/interaction/principle-of-readability.md). # Principle of Readability Text must be easily legible and understandable for the intended audience. The Principle of Readability is a fundamental principle in typography that emphasises the importance of designing text that is easy to read and understand. It is based on the idea that the readability of a text is influenced by several factors such as typeface, font size, line spacing, colour, contrast, and much more. In essence, the Law of Readability states that text should be designed in a way that makes it easy for readers to comprehend and engage with the content. This can be achieved by using legible fonts, appropriate font sizes, and adequate line spacing. Additionally, designers should consider the contrast between the text and background colour to ensure that the text is easy to read. The principle is particularly important in digital design where users are often bombarded with large amounts of text. By designing text that is easy to read and understand, designers can create a more engaging user experience that encourages users to interact with the content. For instance, consider a website with poorly designed typography. If the font size is too small or the line spacing is too narrow, it can be difficult for users to read and comprehend the content. However, if the website uses appropriate typography such as a legible font size and adequate line spacing, it can create a more enjoyable reading experience for users. #### Further Reading {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/interaction/principle-of-readability.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.