Introduction
This book will assist frontend developers in building accessible e-commerce websites and components.
The MIND Patterns are not to be confused with a visual design system, CSS framework or JavaScript library. Our patterns are instead intended to complement those systems by acting as foundational accessibility guidance.
These examples will assist the frontend developer with accessibility, but the source code is not considered to be final, production-ready code. Most examples leave additional steps; which typically will be any CSS styling and JavaScript behaviour that is not specifically related to core functionality or accessibility.
This book is a living, work-in-progress document.
Last updated: April 21st 2021 (dropped IE11 support)
Each pattern follows a progressive enhancement strategy (where applicable), aims to conform to WCAG 2.1 Level AA, and for the most part builds on from the excellent guidance set out in the WCAG Authoring Practices 1.1.
There are four main groups of component-related patterns:
​Messaging​
​Input​
​Navigation​
​Disclosure​
These groups spell out the MIND acronym. If you ever wonder what group does a pattern fall into - then use your MIND!
Three other important groups complement the above patterns:
​Structure​
​Anti-Patterns​
​Techniques​
We have not yet incorporated these three groups into any kind of clever or witty acronym. Disappointing, I know.
Every completed pattern will include:
Introduction
Working examples
Terminology
Best practices
Interaction design
Developer guide
ARIA Reference
The book also contains an appendix section with a list of ARIA Essentials, References, Utilities and FAQ.
There are 4 guiding principles of accessibility, collectively know as POUR:
Perceivable: People experience content in different ways (sight, hearing, and touch). Content needs to be transferable into recognizable (or perceivable) formats.
Operable: Content needs to be navigable (or operable) by multiple methods—not just a mouse
Understandable: Web content needs to be understandable. Language should be simple and concise; functionality should be consistent and intuitive.
Robust: Create web content that works for all (or most!) technologies. This includes operating systems, browsers, and mobile devices.
From a developer perspective, Operable and Robust are the most important principles!
Accessibility testing is performed with latest versions of:
Edge & Narrator
Chrome & JAWS
Safari & VoiceOver
Firefox & NVDA
Chrome & Chromevox
Don't feel like reading? You can, if you wish, dive straight into the working examples.
