An ongoing process
We consider accessibility an ongoing process. It is intertwined with all aspects of design and development, and is dependent on team effort. Thinking about accessibility has led us to simpler and more elegant solutions for everyone.
Example: Contrast and accessible colors
One of our first challenges was about color contrast. We wanted our customers to be able to choose any color for their branding, but still make sure the interface had sufficient contrast. We’ve blogged about this and presented on it at CSSConf, Berlin 2018.
Here are additional resources from the talk:
- Automatically generating an accessible color palette (blog post)
- The Norwegian Accessibility Law (blog post)
- Color contrast definition (WCAG)
- Relative luminance definition (WCAG)
- Contrast criteria for non-text elements (WCAG 2.1)
- color.js npm package
- CSS Custom Properties Documentation
- How to use CSS Custom Properties
Sharing what we learn
We’re a small team and, as with many startups, none of us are experts in accessibility. But we believe in having an open process and sharing what we learn with the community to show that accessibility is something you can and should think about from the very start. (And since we’re based in Norway, we’re actually required by law to be accessible).
We regularly do accessibility walkthroughs with external advisors to weed out errors we’ve made. Here’s a Google Spreadsheet (mostly in Norwegian) which lists everything on our current fix list.