AW: "Bypass Blocks" Question

Hi Mandana, Jamie,

Here a very short answer:

1.      It is important to bring in the structure using either HTML5 or ARIA content blocks, but

2.     People who do not use screen readers have yet no possibility to use the confort of jumping from one block to another, because the browsers build currently no dynamic navigation using author’s content structure.

3.     To help all people including also visual keyboard-only users it is still necessary to offer internal links to the top of the blocs or, at least, single jump-over links at the top of blocs with plenty of links within. The best practice is to make them visible always, but that is the question of design. It is sufficient to make these links visible on focus, when the user tabs in.
Ciao     Mario

Von: Jamie Rau [mailto:jamie.rau@gmail.com]
Gesendet: Samstag, 18. Juli 2015 02:07
An: w3c-wai-ig@w3.org
Cc: <w3c-wai-ig@w3.org>
Betreff: Re: "Bypass Blocks" Question

unsubscribe

On Wed, Jul 8, 2015 at 5:41 AM, Mandana Eibegger <mandana@schoener.at<mailto:mandana@schoener.at>> wrote:
Hello,

i have a question concerning the Success Criterion 2.4.1 "Bypass Blocks".

For this SC there is the Sufficient Technique
"ARIA11: Using ARIA landmarks to identify regions of a page (ARIA)"

And an Advisory Technique
"Using accessibility supported technologies which allow structured navigation by user agents and assistive technologies (future link) "

Does HTML5 count as an "accessibility supported technology" in the meantime?
So, would using <main><header> etc be sufficient to support bypassing of blocks?

And what about users, not using AT (just tabbing in the browser)?
Wouldn't it still be necessary to implement skip-links and access-keys to make a webpage accessible?

Thank you,
Mandana