Accessibility

Good web accessibility means that everyone is able to understand and use your website, no matter their physical or mental disabilities.

Examples of disabilities

When talking about web accessibility, the most common topic is screen readers that are often used by blind people. But there are many more disabilities to keep in mind. Some examples of things to consider include:

• Blind users

  Ensure your website works with a screen reader. This requires an understanding of how to use appropriate HTML elements effectively.

• Motor impaired users

  Ensure your website is navigable without a mouse, and focused elements get a clear indicative highlight.

• Visually impaired users

  Ensure sufficient contrast and support adjustable font sizes through browser or OS settings. Provide alt texts for images to convey their meaning. Also highlight currently focused elements with a border or indicator for non-mouse users.

• Users with Sensitivity to Visuals (e.g. Seizures, Migraines)

  Minimize flashing or excessive animations. Implement the CSS media feature "prefers-reduced-motion" to accommodate users who disable animations, while still having them visible to other users.

• Users with Learning disabilities

  This is often the highest level of consideration (with some exceptions) that government websites need to take into consideration for people with troubles focusing and processing information. It is often solved by having an easy-to-read version of your texts.

• Deaf users

  Ensure videos include subtitles or, where possible, provide sign language interpretations.

WCAG - what is that?

WCAG (Web Content Accessibility Guidelines) defines accessibility standards for websites. It has three levels:

• A: Basic accessibility
• AA: Recommended for most organizations, covering common barriers.
• AAA: The highest level, often required for very specific websites like banks or governments.

Aim for AA-level compliance even if it's not required. As developers, we have the power to make the web more inclusive for everyone.

For accessible components, you can use resources like www.w3.org/WAI/ARIA/apg/patterns which contains examples of accessible components based on the official WCAG guidelines.