E-mail List Archives
Re: Associating Errors From Wave Plug-in to the HTML Source
From: Kelly Ford
Date: Dec 30, 2018 9:10AM
- Next message: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message: Patrick H. Lauke: "Re: The ITIC updated VPATs"
- Next message in Thread: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message in Thread: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- View all messages in this Thread
Hi,
Here is what I'm hoping in some fashion will be possible.
1. I start reading through the waved-marked view of the web page with the
JAWS VPC mode on or the equivalent mode in NVDA, Narrator, VoiceOver or
other screen readers. To be clear, this is the text of the web page, not
the source.
2. I encounter indication of an error. This is where I would like a fast
way to jump to the relevant section of the page source.
I would agree 100% and more that most of the tools in this space are
difficult to use from an accessibility perspective. They require extensive
screen reader gymnastics to me.
One last item, would you consider marking up the source part of the wave
view of a web page with some landmark or other indication. Right now the
fastest way I've found to get to it is to use a screen reader's search
feature and search for the word code. BTW, I'm not sure what the link code
is supposed to do. Each time I activate it, Chrome stops responding.
Kelly
- Next message: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message: Patrick H. Lauke: "Re: The ITIC updated VPATs"
- Next message in Thread: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message in Thread: Jared Smith: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- View all messages in this Thread