Level 6, 341 George St (Atlassian)
“a11y”… that’s a – eleven – y, is the shorthand for “accessibility”. We should say it a lot, so yeah, finding efficiencies make ssense. But which one is correct?
If you're casually talking about accessibility, as you should, then a11y is right in the money.
If you're talking about the community focused on accessibility, or the values it promotes, then you're probably straying into proper noun territory, so I'd opt for A11y.
If you're declaring just how important Big A or Little a accessibility is, then feel free to go All Caps and A11Y.
Really, it's not too important how you write it out, the important thing is that you adopt it as part of everyday practice.
So come and join Isabel Brison as she leads the next SydJS takeover, and find out just how you can do that!
A look at the bits of content accessibility that can't be automatically built or tested.
In this talk we'll look into the capabilities of screen readers -- the interface between visually-impaired users and computers.
We'll be investigating the following questions:
- What are the shortcuts that these users are capable of?
- How do they navigate, and how do they perceive your content?
Exploring these questions is the first step toward creating accessible sites and apps.
Lessons learned when flying blindly into developing for accessibility for the first time. An exercise in challenging our own biases to create usable services for all.
An expanded look at the accessibility of privacy, how to help your open source project to be more inclusive and the large ramifications of tabs vs spaces.