W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2017

Re: AInspector and Landmark Roles

From: Michael A. Peters <mpeters@domblogger.net>
Date: Sun, 12 Nov 2017 18:23:32 -0800
To: "Gunderson, Jon R" <jongund@illinois.edu>, ALAN SMITH <alands289@gmail.com>, W3C WAI-IG <w3c-wai-ig@w3.org>
Message-ID: <e5fd99d9-db66-b509-773e-739b58900cf4@domblogger.net>
Thank you! Found a tidbit I had not seen before:

``Do not use the landmark role as part of the label. For example, a 
navigation landmark with a label "Site Navigation" will be announced by 
a screen reader as "Site Navigation Navigation". The label should simply 
be "Site".''

As I don't have access to a screen reader (Linux), I didn't realize they 
did that.

For now I think I solved the problem - I use DOMDocument to make pages 
and my aside within an artivle always has a heading so for now before I 
serve pages, I just have a server-side script that ads "role=region" and 
creates an aria-label attribute of "aside: [content of heading]" to the 
aside before the document is served.

That should avoid screen readers that don't like complementary roles 
within other landmarks while also letting the user know it is an aside 
to the parent region it is a child of.

Now I have to go back and fix my aria-label generation because I know my 
navigation landmarks make the label mistake your link points out.

On 11/12/2017 06:01 PM, Gunderson, Jon R wrote:
> Here is a link to ARIA Authoring Practices information on Landmarks:
> http://w3c.github.io/aria-practices/#aria_landmark
>
> Here is an example of Landmarks in use:
> http://w3c.github.io/aria-practices/examples/landmarks/index.html
>
> Jon
>
>
> On 11/10/17, 6:54 PM, "Michael A. Peters" <mpeters@domblogger.net> wrote:
>
>     An aside as I understand it is for content not directly related to the
>     main content but may be of interest to the reader.
>
>     For example in an article on math, in a section about Euler's Law, a
>     very brief biography about Euler would go in an aside element. It isn't
>     pertinent to Euler's law itself but is beneficial to the reader.
>
>     In such a case, the aside should be a child of the section on Euler's
>     Law rather than at the same level as the main element, should it not?
>
>     I'm not defining a role to the aside, just using the aside tag as an
>     aside tag but the landmark role of complementary seems to be implicit.
>
>     On 11/10/2017 04:27 PM, ALAN SMITH wrote:
>     > Michael,
>     >
>     >
>     >
>     > Regions and Landmarks are designed to give structure to the page for
>     > screen reader users.
>     >
>     >
>     >
>     > You do not need to embed landmarks within landmarks. Just use only one
>     > that describes the most obvious and logical function of the area and or
>     > content.
>     >
>     >
>     >
>     > Perhaps something like this image will help?
>     >
>     >
>     >
>     >
>     >
>     > Alan Smith
>     >
>     >
>     >
>     > *From: *Michael A. Peters <mailto:mpeters@domblogger.net>
>     > *Sent: *Friday, November 10, 2017 5:51 PM
>     > *To: *W3C WAI-IG <mailto:w3c-wai-ig@w3.org>
>     > *Subject: *Re: AInspector and Landmark Roles
>     >
>     >
>     >
>     > Okay first two issues I was able to solve via aria-label but I am still
>     >
>     > trying to figure out how to solve the third.
>     >
>     >
>     >
>     > On 11/10/2017 02:20 PM, Michael A. Peters wrote:
>     >
>     >> Hello List,
>     >
>     >>
>     >
>     >
>     >
>     > *snip*
>     >
>     >
>     >
>     >>
>     >
>     >> Issue 3 - on some pages, I use an aside element that is child of a
>     >
>     >> section element that is child or article that is child of main.
>     >
>     >>
>     >
>     >> The use is appropriate for aside, it seems that aside automatically is
>     >
>     >> given a complementary role and then AInspector says complementary role
>     >
>     >> must be top level. But the aside is content related to the section that
>     >
>     >> contains it, so it belongs in the section that contains it.
>     >
>     >>
>     >
>     >> Is there a solution?
>     >
>     >>
>     >
>     >> Thank you for suggestions.
>     >
>     >
>     >
>     >
>     >
>     >
>     >
>
>
>
>
Received on Monday, 13 November 2017 02:23:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 December 2017 16:04:47 UTC