1. Creating bulletproof headings

    Written by on May 12, 2016 in Development

    With some changes to the W3C guidelines on the horizon, Julie walks us through some best practices for headings, one of the web’s most humble-yet-powerful elements.

  2. Real users on Adobe PDFs

    Written by on May 5, 2016 in Development, Examples, UX

    This week, Joanna mines one of our most valuable resources—Simply Accessible’s usability panel—real users who test what we make to ensure our sites and apps are truly accessible. We asked them what barriers they face when accessing PDF documents on the web. Here’s what they had to say.

  3. ARIA thunder: why we published a controversial post (and why we’ll probably do it again)

    Written by on April 22, 2016 in Development, Understanding accessibility

    Our post last week about the pitfalls of ARIA tabs pushed some buttons in the accessibility community. This week, Derek responds to the reactions and shares why we felt it was important to publish something that made our readers uncomfortable.

  4. Danger! ARIA tabs

    Written by on April 14, 2016 in Development, Examples

    ARIA is a great way to make things technically accessible, sometimes without requiring markup changes. But it can be tricky, even if you’re using it in a technically correct way. In this post, Jeff breaks down an ARIA tabs interaction to see how ARIA can impact users with disabilities—and how to make tabs truly accessible.

  5. Keyboard support for mobile: the tutorial

    Written by on March 31, 2016 in Development, UX

    In a tasty follow-up to her article about keyboard accessibility for mobile devices, Devon walks us through a pizza-themed tutorial, bringing keyboard support life in the most delicious way.

  6. Three common accessibility pitfalls for developers: information and relationships

    Written by on March 24, 2016 in Development

    In the third post of her “Accessibility pitfalls for developers” series, Julie takes on information and relationships. This success criteria is about making sure that everyone gets the information, even if they can’t perceive the page the way other people can.

  7. Three common accessibility pitfalls for developers: colour contrast

    Written by on February 18, 2016 in Design, Development

    In the next installment of her “Accessibility pitfalls for developers” series, Julie takes a look at the second most common accessibility problem we see: colour contrast. Colour is most often a designer’s domain, so why a post about colour for developers? Well, the answer is as complex as the projects themselves.

  8. Supporting the keyboard for mobile

    Written by on February 11, 2016 in Development, UX

    Keyboard support means you have the freedom to use your hardware in the way that is most efficient and effective for you, which is really the whole point of inclusive design. But how do we get to keyboard accessibility for touch interfaces?

  9. Three common accessibility pitfalls for developers: text alternatives

    Written by on February 4, 2016 in Development

    What accessibility issues did we encounter most frequently last year? In this three-post series, Julie shares what she discovered. We start with the third most common pitfall: text alternatives for non-text content.

  10. The accessibility stack: making a better layer cake

    Written by on January 21, 2016 in Development, Examples, Understanding accessibility

    One way to prevent avoidable issues is to approach building for accessibility the way you build a web or native app from the ground up, in a stack of technologies, where each one has its role to play. Just like you carefully consider what backend language (if any), framework language, and additional libraries you might want to use for your app before you start building, the same should be done for accessibility.