Inclusivity via accessibility

Already working on semantics within HTML, I got an affinity with digital accessibility during my final internship at the Accessibility Foundation. In my specific case: websites, web shops, and web applications.

Focus on the need for accessible solutions has also always remained.

Let's address inclusivity!

Convention, businesscase and law

The UN Convention on the Rights of Persons with Disabilities recognizes using the web as a basic human right for everyone. Building accessible solutions is intended for developers and organizations that want to create high quality websites and web tools, and not exclude people from using their products and services.

There is also a strong business case for accessibility:

  • overlap with mobile web design and usability;
  • semantically built websites are better for SEO;
  • minimize legal risks when digital accessibility laws are effective;
  • reach more people.

The power of the Web is in its universality.
Access by everyone regardless of disability is an essential aspect.

Tim Berners-Lee, W3C Director and inventor of the World Wide Web

I stand for and help with inclusiveness:

  • Accessible environment for the blind and the visually impaired;
  • Accessibility for people with a disability (such as Parkinson's disease);
  • WCAG 2.1 and whether or not use WAI aria.

I like to share the knowledge I gained in the past 15+ years and tens of thousands of hours. In favour of digital agencies and businesses. I assist all kinds of companies by transferring knowledge or speaking at events (Either as a guest or a speaker).

Event invitation or request consultancy

Like to get started right away and make a website or a webshop even more accessible? One test alone won't show all the pitfalls. Use a combination of tooling’s or knowledge to determine the pitfalls more accurately. For example:

  • Color usage (we like to use: https://accessible-colors.com/);
  • Are user buttons for interactions accessible when using a keyboard, e.g. (navigation) dropdowns;
  • Use semantic HTML to inform the browser of the correct context of your content when using a screenreader;I
  • Is the focus in the browser window always visible? It should be in order to help and assist the visually impaired or people with a motor disability (who often can't use a mouse or mousepad);
  • Does the responsive or smartphone equivalent of the website comply to WCAG 2.1?

Want to talk about inclusivity?

Rather not do it yourself? Let me do an audit for your website, webshop, or application to test the accessibility on different perspectives.

You may think of:

  • Color usage
  • Are user interactions, e.g. dropdown menu's, accessible on the keyboard;
  • Is the coding semantically build, or is WAI ARIA used in the right way;
  • Is the focus on buttons visible at all times;
  • Is there a responsive or smartphone equivalent, and does it comply to WCAG 2.1.