Re: [orca-list] VoiceOver vs. Orca - An ignorant question

[Jeffery Mewtamer <mewtamer gmail com>]

I use Orca exclusively for web browsing, and some websites are a royal
pain to work with, but as far as I'm concerned, the problem is with
the web sites having bad web design, not Orca lacking a workaround for
every bit of bad web design out there.

Granted, it feels like most of Orca's development is someone reporting
a website that gives Orca trouble and the dev then patching in a
workaround for that website that hopefully doesn't break anything, but
still, if the web designers didn't do something unusual, the
workaround wouldn't be needed... and honestly, testing that their
forms can be filled out without taking one's hands off the keyboard
would avoid most of the problems, testing with NVDA would catch most
of the problems a keyboard test would miss, and not trying to reinvent
the wheel by doing something fancy with JavaScript that can be
accomplished with vanilla HTML would avoid many problems... and any
truly complicated website probably has a larger staff, and going the
extra mile to test their website Voice over in Safari on both OSX and
iOS, Orca in both Firefox and Chromium, Narrator, JAWS, and NVDA in
Firefox, Chrome, and whatever Microsoft is calling their browser these
days, and Talkback in both Chrome and Firefox would still be less work
for the web designers than testing Orca on every website on our end.

Don't get me wrong, it's great Orca tries to workaround problems as
they are reported, but still, I think the responsibility to make a
product or service accessible should fall on the one providing that
product or service, not the one providing tools to help out when they
fail.