To get the most out of this book
This book is for people who’ve worked on digital products – designers, developers, content strategists, researchers, and beyond. We assume you understand the basics of building websites or apps, but not necessarily accessibility or inclusive design.
You don’t need to be an expert. What matters is that you’re ready to shift your perspective – to see inclusion not as a checklist, but as a core design value that benefits everyone.
If you bring curiosity, openness, and a willingness to question default practices, you’ll find this book both practical and transformative.
Download the color images
We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://packt.link/gbp/9781835888223.
Conventions used
There are a number of text conventions used throughout this book.
CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and X/Twitter handles. For example: “Tags such as <header>, <article>, and <section> provide clear definitions of their role, allowing both browsers and assistive technologies to interpret and navigate the page effectively.”
A block of code is set as follows:
@media (prefers-color-scheme: dark) {
body {
background-color: #121212;
color: #f5f5f5;
}
}
Bold: Indicates a new term, an important word, or words that you see on the screen. For instance, words in menus or dialog boxes appear in the text like this. For example: “Semantic HTML structures a web page using elements that inherently describe their purpose, making content more meaningful and accessible.”
Warnings or important notes appear like this.
Tips and tricks appear like this.