WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: jaws adding or changing a page

for

From: Lucy Greco
Date: Oct 11, 2012 3:40PM

thanks for all this grate information. has any one filed this as a bug
with fs.? as well the second part of my problem i think is more
Critical have any of you ever seen the ARIA that is not there being
created by jaws i really think its bad for a screen reader to add
elements that are not there.

On 10/11/12, Ryan E. Benson < <EMAIL REMOVED> > wrote:
> Thanks for the information.
>
> --
> Ryan E. Benson
>
>
> On Tue, Oct 9, 2012 at 2:05 AM, Jason Kiss < <EMAIL REMOVED> >
> wrote:
>> Hi Ryan,
>>
>> I agree the new outline algorithm is complicated. This, in part at least,
>> is why it is listed as one of the at-risk items for inclusion in the HTML5
>> spec: http://www.w3.org/html/wg/wiki/HTML5.0AtRiskFeatures
>>
>> H1-H6 have been retained for backwards compatibility.
>>
>> If one wants to use sectioning elements, the best advice, I think, is to
>> continue using H1-H6 as appropriate given the content's hierarchy, while
>> taking extra care with the use of sectioning elements, e.g., not using
>> <section> for wrapping the page's main content. JAWS will still mess up
>> how it reports the level of other headings in sectioning elements, but
>> this is a bug that Freedom Scientific needs to address as a priority. The
>> only other option would be to not use the sectioning elements, which may
>> be a less arduous accommodation where <section> and <article> are
>> concerned, but <nav> and <aside> come with some useful semantics already
>> implemented by some browsers and screen readers. It comes down to what one
>> is willing to do or forego when faced with nasty bugs in user agents.
>>
>> Jason
>>
>>
>> On 9/10/2012, at 6:46 PM, "Ryan E. Benson" < <EMAIL REMOVED> > wrote:
>>
>>> Thanks for the links Jason. While I understand what the two articles
>>> are saying, my biggest concern is trying to explain this to non-savvy
>>> people. My first impression is if W3C is advocating using h1's all
>>> over, why didn't they just get rid of H1-6, and just make a heading
>>> element? There would be the draw back of when would it be an h3 versus
>>> an h2, which ultimately would lead to section-itous vs div-itous.
>>>
>>> --
>>> Ryan E. Benson
>>>
>>>
>>> On Tue, Oct 9, 2012 at 12:47 AM, Jason Kiss < <EMAIL REMOVED> >
>>> wrote:
>>>> Hi Lucy,
>>>>
>>>> Regarding the headings issues, is the H1 nested in an HTML5 sectioning
>>>> element, e.g., <section>, <article>, <nav>, or <aside>? If so, and you
>>>> are using JAWS12/13/14 in IE, that would explain it. JAWS implements
>>>> (albeit incorrectly) the HTML5 outlining algorithm. This will have an
>>>> effect on how heading level is reported for headings nested in
>>>> sectioning elements. See
>>>> http://www.accessibleculture.org/articles/2011/10/jaws-ie-and-headings-in-html5/
>>>> for more info.
>>>>
>>>> Checking out
>>>> http://www.456bereastreet.com/archive/201103/html5_sectioning_elements_headings_and_document_outlines/
>>>> might also be of use.
>>>>
>>>> Hope this helps,
>>>>
>>>> Jason
>>>>
>>>>
>>>> On 9/10/2012, at 5:35 PM, Lucy Greco < <EMAIL REMOVED> > wrote:
>>>>
>>>>> hello:
>>>>> i have been doing some web testing and have come across a very
>>>>> strange behavior. if i run the page thru NVDA and voice over the page
>>>>> shows an h1 in the right place and where it should be. however jaws
>>>>> shows the same heading as an h2. we have checked the source code and
>>>>> it is definitely a h1.
>>>>>
>>>>> as well, on the same page jaws has turned all the lists on the page to
>>>>> navigation landmarks. has any one seen this before?
>>>>>
>>>>> the designer is using the modernizr javascript library and i suspect
>>>>> this may have something to do with it but i can't tell for sure.
>>>>> before you ask i can't share the link or code sorry
>>>>>
>>>>> lucy
>>>>>
>>>>> Lucia Greco
>>>>> Web Access Analyst
>>>>> IST-Campus Technology Services
>>>>> University of California, Berkeley
>>>>> (510) 289-6008
>>>>> http://webaccess.berkeley.edu
>>>>> >>>>> >>>>> >>>>
>>>> >>>> >>>> >>> >>> >>> >>
>> >> >> > > > >


--
Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008
http://webaccess.berkeley.edu