WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Re-order page content

for

From: Sandy Feldman
Date: Jun 2, 2017 3:59PM

I've been using role="region". I just double-checked and realized it's
in the works and not one of the accepted terms. Should I cut that out?
Or carry on on the theory it doesn't do any harm?

https://www.w3.org/WAI/GL/wiki/Using_the_region_role_to_identify_a_region_of_the_page

Sandy


On 2017-06-02 4:38 PM, John Foliot wrote:
> Hi Sandy,
>
> If you are talking about ARIA landmark regions
> (https://www.w3.org/TR/wai-aria/roles#landmark_roles), there is only a
> fixed taxonomy of region terms:
>
> * application
> * banner
> * complementary
> * contentinfo
> * form
> * main
> * navigation
> * search
>
> While it would be perhaps interesting to allow for an expansion of
> those landmarks (or the ability to create custom ones), we really
> can't do that today.
>
> > Would headings with those names be better?
>
> Yes,
> absolutely.
>
> However dealing with the "which should come first"
> question remains: First-time users should (MUST?) get the
> instructions first, but by your 58th log-in I suspect getting those
> instructions would be, at a minimum, useless, and at a maximum
> outright frustrating (with I suspect a majority being "annoyed"). Not
> that non-sighted users couldn't "deal" with always getting
> instructions first (it *is* trivial to jump ahead, and as you note the
> good use of Headings would certainly facilitate page navigation and
> orientation).
>
> JF
>
> On Fri, Jun 2, 2017 at 1:08 PM, Sandy Feldman < <EMAIL REMOVED>
> <mailto: <EMAIL REMOVED> >> wrote:
>
> Would creating ARIA regions be useful here? Would it be easier to
> skip the instructions and login if instructions were in a region
> labelled "login instructions" and the login wasin a region
> labelled "login"? Would headings with those names be better?
>
> Sandy
>
> On 2017-06-02 9:41 AM, John Foliot wrote:
>> Specific to Joseph's question:
>>
>> Not seeing the actual design in question, I still will suggest that for
>> maximum usability (including sighted keyboard-only users) putting the
>> repeat action (Log-In) ahead of the (presumably) one-time, or limited-time
>> use of "Instructions" actually makes sense over the aggregate: non-sighted
>> users won't need to hear the instructions**every** time they arrive at that
>> page, only the first time (or perhaps the first few times - but the log-in
>> process will be, and become, a rote activity over time).
>>
>> (Think of this in terms similar to "skip-nav"... skipping over repeated or
>> non-needed content to get to the "meat" of the page in question - here, to
>> log-in.
>
>
>
>
> --
> John Foliot
> Principal Accessibility Strategist
> Deque Systems Inc.
> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>
> Advancing the mission of digital accessibility and inclusion