E-mail List Archives
Re: Bypass Blocks for Keyboard users
From: Jared Smith
Date: Jul 17, 2015 11:14AM
- Next message: Bryan Garaventa: "Re: Screen Readers as a Development Tool for Web Developers"
- Previous message: Lynn Holdsworth: "Re: Interactive Elements on Older Technologies - ARIA vs Screen Reader Text"
- Next message in Thread: deborah.kaplan@suberic.net: "Re: Bypass Blocks for Keyboard users"
- Previous message in Thread: Paul Bohman: "Re: Bypass Blocks for Keyboard users"
- View all messages in this Thread
Paul Bohman wrote:
> there is some deep-seated resistance to doing that, even among
> accessibility advocates and blind programmers at these companies.
> I really don't get it.
Likewise. Perhaps we could gain support by not presenting it as only
an accessibility solution. I don't have a motor disability, but would
LOVE to have the ability to navigate through landmarks natively in my
browser. It would be amazing to hit M to jump to the main content, S
to search, N to cycle through navigation elements, etc.
I've been saying for many years that the most significant thing that
could happen right now that would have the biggest immediate impact on
end user accessibility would be for common browsers to support heading
and landmark/region keyboard navigation. And once supported, "skip"
links could go away - and good riddance to them.
Jared
- Next message: Bryan Garaventa: "Re: Screen Readers as a Development Tool for Web Developers"
- Previous message: Lynn Holdsworth: "Re: Interactive Elements on Older Technologies - ARIA vs Screen Reader Text"
- Next message in Thread: deborah.kaplan@suberic.net: "Re: Bypass Blocks for Keyboard users"
- Previous message in Thread: Paul Bohman: "Re: Bypass Blocks for Keyboard users"
- View all messages in this Thread