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

AInspector and Landmark Roles

From: Michael A. Peters <mpeters@domblogger.net>
Date: Fri, 10 Nov 2017 14:20:57 -0800
To: W3C WAI-IG <w3c-wai-ig@w3.org>
Message-ID: <21d0b17e-bfa6-f5ce-5c00-86911eea1a0e@domblogger.net>
Hello List,

I'm not an accessibility guru, I'm financially poor and education / 
workshops on such topics are not free, but I try my best to make sure 
every website I work on is as accessible as I can make it.

I did not know about AInspector until the post warning people to switch 
to ESR which I can't do because I have to test features that often are 
not supported in ESR releases of FireFox.

So I installed it to use it while I still can.

It looks like it is a fantastic tool, and it alerted me to some issues I 
am having trouble comprehending how to fix.

I use XHTML5 sent with XML mime type.


Issue 1 - I have two nav elements, one right after the other. The first 
is always present, second is normally hidden and is an extended menu 
that most people do not need.

First has a button as very last element that toggles whether the hidden 
nav is visible.

When the second is toggled to be visible, AInspector gives a violation 
stating that landmark elements must be uniquely identifiable.

They have different ID attributes, but I'm not understanding how to make 
them uniquely identifiable.

Since one nav directly follow the other in code, I could change both nav 
elements into div elements inside a single parent nav so there is only 
one nav but I'm not sure that is best, it would solve the problem but it 
may make it harder for the user of a screen reader to switch between the 
always there menu and the extended menu.


Issue 2 - At top of page I have a banner advertisement. At bottom of 
page - below the footer - I have what I like to call my propaganda div, 
a place where I have a few links of importance to my users but not to 
the site (link to why https is so important, link to Privacy Badger, 
link to a relatively anonymous VPN service)

Both have role="complementary"

Same issue, AInterest says they are not uniquely identifiable.


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 Friday, 10 November 2017 22:21:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:11 UTC