Explore >> Select a destination
|
You are here 
|
www.jakerobins.com | ||
| | | | |
alistapart.com
|
|
| | | | | As an extension to our From URL to Interactive series, designer and front-end developer Melanie Richards takes a deep dive into how our content is accessed by a wide array of screen readers, which are highly customizable to users. Understanding the nuances of accessibility APIs, thorough testing approaches, and the wealth of resources available, site | |
| | | | |
www.24a11y.com
|
|
| | | | | Manuel Matuzovic shares how he ditched his mouse, going keyboard-only. He shares the results of his research and the issues that impact keyboard-only users. | |
| | | | |
www.smashingmagazine.com
|
|
| | | | | Many of us are taught to make sure our sites can be used via keyboard. Why is that, and what is it like in practice? Chris Ashton did an experiment to find out. He hopes to raise the profile of difficulties faced by real people, which are avoidable if we design and develop in a way that is sympathetic to their needs. Chris used the web for a day without JavaScript. Today, he forces himself to navigate the web using just his keyboard. | |
| | | | |
www.miriamsuzanne.com
|
|
| | | A path forward, with single-axis containment | ||
