Yup. That has been an ongoing fight for years going back to the Web
Standard Project and Jeffry Zeldman.
http://en.wikipedia.org/wiki/Web_Standards_Project
http://en.wikipedia.org/wiki/Jeffrey_Zeldman
I use the canary and future proofing arguments with developers all the
time to try and convin
You make some good points that I can't disagree with. If we could just
have developed standards and have them used, that would take us down
the best route I think.
On 11/26/12, Chris Blouch wrote:
> There are a couple difficulties with the secret repair approach:
>
> 1. It enables developers to c
There are a couple difficulties with the secret repair approach:
1. It enables developers to continue with bad habits which they will
apply to more and more pages over time. At some point they need to learn
to stop doing bad things. Often time the bad behavior also conflicts
with web standards
I would say if the screen reader can "fix" bad code and make it work
the way it should have, please do it! There are more than plenty of
instances where you will never get the developer to fix it or even
begin to care. If you do then there are advantages to that, but who
knows how many weeks, month
Got it. That's really interesting. I like this way of philosophie. But on the
other hand for a "simple" user the most important seems to be that the screen
reader just works. The "average" user is probably not interested in technical
back ground stuff but in just working with a web side as easil
One problem with Jaws is that it will attempt to 'repair' bad HTML under
the hood. For testing this masks errors in a site from developers such
that Jaws might work ok but other screen readers are not as tolerant of
bad code in a particular setup. VoiceOver on Mac and NVDA on Windows do
not att
That happens here as well. Apple probably will tell you that it depends how the
side is built.
I recently discribed to them the issue that VO quite often doesn't interact
with a web page despite the fact that it's checked in the
Am 20.11.2012 um 18:53 schrieb Alex Hall :
> Hi all,
> Every so o
That happens here as well. Apple probably will tell you that it depends how the
side is built.
I recently discribed to them the issue that VO quite often doesn't interact
with a web page, despite the fact that it's checked in the the VO settings.
They told me it depends on the web side not on V
Hi all,
Every so often, when I load or reload a page, vo will restart. I will hear
"Voiceover on" after several seconds of intense activity from the hard drive,
and things will proceed normally from there. Why would vo be crashing, and are
there logs I could use to pinpoint the problem or at lea
