WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Double encoding of elements

for

From: Kevin Prince
Date: Oct 26, 2015 6:39PM

My first thought too - if its an H3 then its an h3 not a different visual interpretation of H2

K
Access1in5
0212220638
039290692
Independent Accessibility and IT Consultancy.



> On 27/10/2015, at 03:57, Sailesh Panchang < <EMAIL REMOVED> > wrote:
>
> <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)
>>
>>