Blog: Most Popular

  • Is input type=”date” ready for use in accessible websites?

    Media Type: Blogposts

    One of the 'new' HTML5 elements - input type="date" - was intended to simplify the collection of dates on websites, and to reduce user errors whilst doing so. So is…

  • My favourite accessible accordion pattern

    Media Type: Blogposts

    Accordions are useful components in web pages for temporarily hiding content until it's needed. But is it possible to make an accessible accordion component? Here's an illustrated walkthrough of the code…

  • Accessible accordions part 2 – using <details> and <summary>

    Media Type: Blogposts

    After a comment on my previous blog post about accessible accordion patterns, I decided to do some investigation on the details and summary HTML elements. They could be the best…

  • Do accessible websites still need to support Internet Explorer 11?

    Media Type: Blogposts

    As a developer who cares about accessibility, should you or shouldn’t you be supporting Internet Explorer 11? I’ll explore both sides of the case for continuing to develop for it...

  • Collecting dates in an accessible way

    Media Type: Blogposts

    There are many different ways to collect dates from users in website forms. But what's the best way to do that in a way that's accessible to everyone? In this…

  • Figure and figcaption – extended alternate text for screen readers?

    Media Type: Blogposts

    The usual way of making images accessible for people who can't see them is to provide alternative text using the alt attribute of the element. However, in many websites, images…

  • Dos and don’ts on designing for older people (POSTER)

    Media Type: Posters

    Older people could be your web site or app's most underserved audience. Turn them into customers with our poster of tips from our Digital Accessibility Experts Live webinar last week...

  • How to use HTML5 sectioning elements to create useful accessible landmarks

    Media Type: Blogposts

    HTML5 sectioning elements like <header>, <nav>, <main> can be good for accessibility, as screen reader users can hear them voiced as ‘landmarks’, but only if they are used correctly...