WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Re-order page content

for

From: Jonathan Avila
Date: Jun 4, 2017 2:19PM

[John wrote] @Jon... OK, I quoted the normative ARIA 1.0, and not the Candidate ARIA 1.1, but you are correct. Mea culpa .

ARIA 1.0 allowed the use of role region as well https://www.w3.org/TR/wai-aria/roles#region if there is a more appropriate specific role it should be used instead of region.

Perhaps you are thinking about "section" or other abstract roles. Authors should never use abstract roles that are part of the ontology but not defined for use.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group (soon to be Level Access)
<EMAIL REMOVED>
703.637.8957 (Office)

Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of John Foliot
Sent: Saturday, June 03, 2017 7:21 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Re-order page content

@Jon... OK, I quoted the normative ARIA 1.0, and not the Candidate ARIA 1.1, but you are correct. Mea culpa .

JF

On Fri, Jun 2, 2017 at 5:46 PM, Jonathan Avila < <EMAIL REMOVED> >
wrote:

> > The use of role="region" is non-valid and non-conformant, although
> > in
> practical terms it is benign - today.
>
> John, can you please provide a citation for role of region being
> non-valid and non-conformant?
>
> https://www.w3.org/TR/wai-aria-1.1/#region
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group (soon to be Level Access) <EMAIL REMOVED>
> 703.637.8957 (Office)
>
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney
> privileged and/or confidential information intended for the use of the
> individual or entity named above. If the reader of this message is not
> the intended recipient, you are hereby notified that any use,
> dissemination, distribution or copying of this communication is strictly prohibited.
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of John Foliot
> Sent: Friday, June 02, 2017 6:07 PM
> To: Sandy Feldman
> Cc: WebAIM Discussion List
> Subject: Re: [WebAIM] Re-order page content
>
> The use of role="region" is non-valid and non-conformant, although in
> practical terms it is benign - today.
>
> If you can remove it, do so, but don't stay late on a Friday evening
> to do it - make it a regular maintenance task if you can.
>
> At least, that would be *my* strategy...
>
> JF
>
> On Fri, Jun 2, 2017 at 4:59 PM, Sandy Feldman < <EMAIL REMOVED> >
> wrote:
>
> > 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> >
> > 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 was in 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>
> >
> > Advancing the mission of digital accessibility and inclusion
> >
> >
> >
>
>
> --
> John Foliot
> Principal Accessibility Strategist
> Deque Systems Inc.
> <EMAIL REMOVED>
>
> Advancing the mission of digital accessibility and inclusion
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >



--
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
<EMAIL REMOVED>

Advancing the mission of digital accessibility and inclusion