- From: John Foliot <john.foliot@deque.com>
- Date: Thu, 18 Jun 2015 14:19:01 -0700
- To: "'James Craig'" <jcraig@apple.com>, "'Joseph Scheuhammer'" <clown@alum.mit.edu>
- Cc: "'WAI Protocols & Formats'" <public-pfwg@w3.org>, "'Dominic Mazzoni'" <dmazzoni@google.com>, "'Alexander Surkov'" <surkov.alexander@gmail.com>, "'David Bolter'" <dbolter@mozilla.com>, "'Cynthia Shelly'" <cyns@microsoft.com>
+1, I have previously suggested that this is the better response (holy cow
James, we're going 2 for 2 :-) ).
Leonie did some very quick real-time testing during our call, and (she will
correct me if I am wrong) she noted that in Firefox with NVDA (?) when the
level was not specified, it defaulted to "level 2" (which I think is a wrong
decision). Not sure where that decision is happening however, but suspect
it's in the screen reader.
JF
> -----Original Message-----
> From: James Craig [mailto:jcraig@apple.com]
> Sent: Thursday, June 18, 2015 2:14 PM
> To: Joseph Scheuhammer
> Cc: WAI Protocols & Formats; Dominic Mazzoni; Alexander Surkov; David
Bolter;
> Cynthia Shelly
> Subject: Re: aria-level a required property for role="heading" or a
supported
> property with an RFC SHOULD for authors
>
> VoiceOver used to speak "Heading Level 0, text content" but we fixed that
a few
> years ago. It now speaks "Heading, text content"
>
> James
>
> > On Jun 18, 2015, at 2:04 PM, Joseph Scheuhammer <clown@alum.mit.edu>
> wrote:
> >
> > On 2015-06-18 3:06 PM, Bryan Garaventa wrote:
> >> Just to simplify my view, if heading levels are optional, ATs and
browsers will
> never provide consistent UIs, because they will always do something
different by
> guessing.
> >
> > Tangent: What do Chrome, FF, IE, and Safari, do, in fact, when faced
with
> "heading", but no aria-level? For example,
> >
> > <div role="heading>...</div>
> >
> > How is the level property mapped?
> >
> > --
> > ;;;;joseph.
> >
> > 'Array(16).join("wat" - 1) + " Batman!"'
> > - G. Bernhardt -
> >
>
Received on Thursday, 18 June 2015 21:19:32 UTC