WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Bypass blocks for a small website

for

From: Mallory
Date: Oct 6, 2020 10:29AM

Let me fix that please:
"Let's point out, what can be done to improve UX for SCREEN READERS: Headings
and regions."

not everyone has admin privileges to install rando extensions/plugins that take things like headings and landmark regions and lets keyboarders or switch control users or whoever to ALSO use those to move focus.

On Tue, Oct 6, 2020, at 12:28 PM, <EMAIL REMOVED> wrote:
> A plead for usability awareness:
>
> I couldn't find out, what OCD stands for, but I know the abbreviation UX.
>
> 2.4.1 has purely usability in mind. 11 keyboard strokes don't make a webpage
> inaccessible stricte dictum. They make it just annoying.
>
> So let's not only reflect the "skip links" to satisfy the required effort to
> pass 2.4.1. Let's point out, what can be done to improve UX for AT: Headings
> and regions.
>
> "Although this Success Criterion deals with blocks of content that are
> repeated on multiple pages, we also strongly promote structural markup on
> individual pages as per Success Criteria 1.3.1. "
> (https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html)
>
> Besides: An accordion mechanism would fit too, to pass SC 2.4.1. Correct?
>
> Wolfgang
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen
> walker
> Sent: Monday, October 5, 2020 6:55 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Bypass blocks for a small website
>
> I was going to say (almost) the same thing as Birkir. 2.4.1 just says a
> "mechanism" is available to bypass blocks. If your mechanism is to
> autofocus to main, that technically passes.
>
> Whether that's a good idea from a UX perspective is a different discussion.
>
> However, regarding landmarks, I'm a bit OCD when it comes to normative vs
> non-normative. Birkir said ARIA *required* landmarks. Where is that
> stated? We all know the first rule of ARIA is to not use ARIA (
> https://www.w3.org/TR/aria-in-html/#rule1) and that ARIA "is intended to
> provide missing semantics so that the intent of the author may be conveyed
> to assistive technologies" (https://www.w3.org/TR/wai-aria-1.1/#ua-support).
> If we focus on using native HTML instead of ARIA, then it seems like the
> <main> element would be a required element, but it's not. I get a little
> nervous when we use the term "required" unless I can find the reference in a
> normative doc.
>
> Feel free to slap me down, Birkir, if I missed something regarding the
> requirement of landmarks. That's what's great about this WebAIM forum, I'm
> always learning something new no matter how long I've been doing it.
> > > http://webaim.org/discussion/archives
> >
> > > > >