E-mail List Archives
Thread: labeling sections
Number of posts in this thread: 7 (In chronological order)
From: Angela French
Date: Wed, Feb 14 2018 10:14AM
Subject: labeling sections
No previous message | Next message →
Hello,
I have two <section> element on a web page. I am getting an accessibility validation error for "Non-distinguishable landmarks". Not sure quite how to distinguish them, I tried a name attribute which resulted in an error. Then I tried an aria-label attribute which also resulted in an error. What is the proper way to distinguish <sections>?
Thank you
Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > * o: 360-704-4316 * f: 360-704-4414
sbctc.edu<https://www.sbctc.edu/> * Twitter: @SBCTCWashington<https://twitter.com/SBCTCWashington> * Facebook: @WASBCTC<https://www.facebook.com/wasbctc/>
From: Steve Faulkner
Date: Wed, Feb 14 2018 10:48AM
Subject: Re: labeling sections
← Previous message | Next message →
>
> I have two <section> element on a web page. I am getting an accessibility
> validation error for "Non-distinguishable landmarks". Not sure quite how
> to distinguish them
This is an error in the tool you are using. They are only exposed as
regions if they have an accessible name via aria-label or aria-labelledby,
otherwise they are akin to <div> elements. I would suggest you ignore the
error.
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
On 14 February 2018 at 17:14, Angela French < = EMAIL ADDRESS REMOVED = > wrote:
> Hello,
> I have two <section> element on a web page. I am getting an accessibility
> validation error for "Non-distinguishable landmarks". Not sure quite how
> to distinguish them, I tried a name attribute which resulted in an error.
> Then I tried an aria-label attribute which also resulted in an error. What
> is the proper way to distinguish <sections>?
>
> Thank you
>
>
>
> Angela French
> Internet/Intranet Specialist
> Washington State Board for Community and Technical Colleges
> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > * o: 360-704-4316 * f:
> 360-704-4414
> sbctc.edu<https://www.sbctc.edu/> * Twitter: @SBCTCWashington<https://
> twitter.com/SBCTCWashington> * Facebook: @WASBCTC<https://www.facebook.
> com/wasbctc/>
>
> > > > >
From: Angela French
Date: Wed, Feb 14 2018 11:02AM
Subject: Re: labeling sections
← Previous message | Next message →
Thank you. I will talk with my vendor about it.
From: Birkir R. Gunnarsson
Date: Wed, Feb 14 2018 7:51PM
Subject: Re: labeling sections
← Previous message | Next message →
Were you using siteimprove?
I don't mean to knock that tool specifically, lots of great ideas, but
I've found they call a heck of a lot of false positives, especially
regarding ARIA and HTML5.
Whatever the tool, help the vendor by filing bugs.
On 2/14/18, Angela French < = EMAIL ADDRESS REMOVED = > wrote:
> Thank you. I will talk with my vendor about it.
>
>
From: Angela French
Date: Thu, Feb 15 2018 12:30PM
Subject: Re: labeling sections
← Previous message | Next message →
Yes, it was flagged in Siteimprove.
From: Carly Gerard
Date: Thu, Feb 15 2018 1:46PM
Subject: Re: labeling sections
← Previous message | Next message →
Our institution is using SiteImprove as well, and finding that is also our biggest error are these false positives of <section> not having an accessible name--even though there's a <main> tag one or two two elements up. I'm glad this discussion came up and feel a little better about addressing that.
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > on behalf of Angela French < = EMAIL ADDRESS REMOVED = >
Sent: Thursday, February 15, 2018 11:30:16 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] labeling sections
Yes, it was flagged in Siteimprove.
From: Steve Faulkner
Date: Fri, Feb 16 2018 12:50AM
Subject: Re: labeling sections
← Previous message | No next message
Hi all, here is a reference for how <section> is mapped in browser
accessibility APIs
region <https://w3c.github.io/core-aam/#role-map-region> role if the section
> <http://www.w3.org/TR/html5/sections.html#the-section-element> element
> has an accessible name
> <https://w3c.github.io/html-aam/#dfn-accessible-name>. Otherwise, no
> corresponding role.
https://w3c.github.io/html-aam/#el-section
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
On 15 February 2018 at 20:46, Carly Gerard < = EMAIL ADDRESS REMOVED = > wrote:
> Our institution is using SiteImprove as well, and finding that is also our
> biggest error are these false positives of <section> not having an
> accessible name--even though there's a <main> tag one or two two elements
> up. I'm glad this discussion came up and feel a little better about
> addressing that.
>
> > From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > on behalf of
> Angela French < = EMAIL ADDRESS REMOVED = >
> Sent: Thursday, February 15, 2018 11:30:16 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] labeling sections
>
> Yes, it was flagged in Siteimprove.
>
>