E-mail List Archives
Re: what to do when <section> flags as accessibility error
From: Beranek, Nicholas
Date: Dec 2, 2016 12:34PM
- Next message: Jonathan Avila: "Re: what to do when
flags as accessibility error" - Previous message: Angela French: "Re: what to do when
flags as accessibility error" - Next message in Thread: Jonathan Avila: "Re: what to do when
flags as accessibility error" - Previous message in Thread: Angela French: "Re: what to do when
flags as accessibility error" - View all messages in this Thread
I agree with Mike. If you don't have multiple regions or landmarks of the same name on the page, then there is little value in adding an aria-label/labelledby to provide an accessible name. I would just add a heading to the region (if necessary) and move on.
Is it calling out SC 1.3.1 Info and Relationships and/or SC 2.4.1 Bypass Blocks? I assume it's referencing the following sufficient technique for each: https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA11
One concern: The <section> maps to the region role, but regions are not considered landmarks per the WAI-ARIA spec. I would check other issues to ensure it's not calling out false positives or ones that are just plain wrong.
Nick
- Next message: Jonathan Avila: "Re: what to do when
flags as accessibility error" - Previous message: Angela French: "Re: what to do when
flags as accessibility error" - Next message in Thread: Jonathan Avila: "Re: what to do when
flags as accessibility error" - Previous message in Thread: Angela French: "Re: what to do when
flags as accessibility error" - View all messages in this Thread