In my work with Design Systems, accessibility often comes up as a topic. Questions can range from the incredibly basic, "What is accessibility?" to the more complex and nuanced, "Is the language of this modal clear enough?" Part of my job is to help guide the designers, developers, content producers, and product owners on their individual journeys understanding accessibility and how it impacts their work.
In an effort to not only help the teams I work with, but the larger digital product community I created what I’m calling the Accessibility Playbook, a manual for teams and individuals to reference in order to ensure the products and experiences they create can be used by the largest number of people.
All commands are run from the root of the project, from a terminal:
| Command | Action |
|---|---|
npm install |
Installs dependencies |
npm run dev |
Starts local dev server at localhost:4321 |
npm run build |
Build your production site to ./dist/ |
npm run preview |
Preview your build locally, before deploying |
npm run astro ... |
Run CLI commands like astro add, astro check |
npm run astro -- --help |
Get help using the Astro CLI |