WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Double encoding of elements

for

From: Sailesh Panchang
Date: Oct 26, 2015 8:57AM


<header roleºnner> ...</header> or <main role="main"> ...</main>
<h3 role="heading" aria-level="2">This is an h3 heading, that we want
to map to an h2 in the accessibility tree</h3>
will all generate validator warnings.
The roleºnner or role=main examples above may be justified in order
to support older browser - assistive technology combos.
With regard to the above <h3> example, it is better to place the
role=heading and the heading text in a span within the h3.
With default styling , visually, the h3 heading is exposed as a level
3 heading; so tricking screen readers to interpret it as an h2 may
misrepresent structure. It is best to use the h2 tag in place of the
h3.
Best regards,
Sailesh Panchang


On 10/26/15, Moore,Michael (Accessibility) (HHSC)
< <EMAIL REMOVED> > wrote:
> Actually for the specific example that you have given I think that it is
> fine. There may be more than one legitimate use of the <header> element
> within the page (for example the header for an article) but there will only
> be one banner region.
>
> Mike Moore
> Accessibility Coordinator
> Texas Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Mark Guisinger via WebAIM-Forum
> Sent: Monday, October 26, 2015 7:38 AM
> To: WebAIM Discussion List
> Subject: [WebAIM] Double encoding of elements
>
> What do people think about double encoding of elements with aria roles
> (i.e.<header role="banner">). Is there an advantage with older screen
> readers or browsers?
> Thanks,Mark Guisinger
> > > http://webaim.org/discussion/archives
> > > > > >