[Athen] webpage coding question

[Teresa Haven]

Will do, thanks.
Teresa

From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On Behalf Of Greg Kraus
Sent: Tuesday, May 12, 2015 10:54 AM
To: Access Technology Higher Education Network
Subject: Re: [Athen] webpage coding question

Look to see if there is a role="application" somewhere, or role= anything as an attribute on an element. Or like Sean said, aria-hidden.

Greg


On Tue, May 12, 2015 at 1:47 PM, Teresa Haven <Teresa.Haven at nau.edu<mailto:Teresa.Haven at nau.edu>> wrote:
Thanks, Greg. Sorry, I should have been more extensive in my list – NVDA with Firefox is in the mix, and I’m getting yet another different incomplete list of headers with it. And when I try to use JAWS with Firefox in this app, my command to request a list of headers just gets “This command is only available in a virtual document, like a webpage.”
Any other suggestions are welcome before I pull my hair out. ☺
Teresa
From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu<mailto:athen-list-bounces at mailman13.u.washington.edu>] On Behalf Of Greg Kraus
Sent: Tuesday, May 12, 2015 10:34 AM
To: Access Technology Higher Education Network
Subject: Re: [Athen] webpage coding question

Sorry, just saw that you were using Firefox. Definitely try NVDA in the mix though.

Greg


On Tue, May 12, 2015 at 1:32 PM, Greg Kraus <gdkraus at ncsu.edu<mailto:gdkraus at ncsu.edu>> wrote:
Hi Teresa,

I would first check if the combinations of JAWS with Firefox and NVDA with Firefox give you the same results. Depending on the version of JAWS and IE and the particular elements that might be parent elements of the headings, that might be the source of the problem. If both JAWS and NVDA work with Firefox, then you can start looking at potential JAWS-IE conflicts.

Greg

On Tue, May 12, 2015 at 1:28 PM, Samantha Johns <samanj at pdx.edu<mailto:samanj at pdx.edu>> wrote:
Perhaps these need element tags - ARIA tags


[https://dl.dropboxusercontent.com/u/329486/OAI_SigPic.png]<http://www.pdx.edu/oai/>

Samantha Johns

Accessibility & Course Support Specialist

Portland State University
1825 SW Broadway
Smith Memorial Student Union, Mezzanine 209
Portland OR 97201
503/725-2754




On Tue, May 12, 2015 at 10:18 AM, Teresa Haven <Teresa.Haven at nau.edu<mailto:Teresa.Haven at nau.edu>> wrote:
I’ve had a strange situation arise with a new web app that my institution is attempting to develop. We are still in the beta stage so the site isn’t public, but we’ve noticed that even though the developer has included appropriate H tags for structure, they aren’t all being perceived by either AT or various A11y checking tools.  When I have JAWS present me with a list of headers on the page, I get one lonely H5 tag.  When I have WAVE check the outline, I am told I have one H1, a small handful of H3s, and one H4. In the code for the page from the user agent perspective we can see one H1, a couple of H2s, a LOT of H3s, and a couple each of H4 and H5 – which is what the developer used in the design. We are using JAWS 14 and 15 for testing, IE11 with JAWS, and Firefox 36 with WAVE. The app is not using HTML5, although it is using some Angular. Does anyone have any ideas for why our AT and tools aren’t perceiving the H tags that we are seeing in the code?

Thanks for any troubleshooting suggestions you might have,
Teresa

Teresa Haven, Ph.D.
Accessibility Analyst, Northern Arizona University


_______________________________________________
athen-list mailing list
athen-list at mailman13.u.washington.edu<mailto:athen-list at mailman13.u.washington.edu>
http://mailman13.u.washington.edu/mailman/listinfo/athen-list


_______________________________________________
athen-list mailing list
athen-list at mailman13.u.washington.edu<mailto:athen-list at mailman13.u.washington.edu>
http://mailman13.u.washington.edu/mailman/listinfo/athen-list



_______________________________________________
athen-list mailing list
athen-list at mailman13.u.washington.edu<mailto:athen-list at mailman13.u.washington.edu>
http://mailman13.u.washington.edu/mailman/listinfo/athen-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20150512/bf10e82c/attachment.html>