I'm answering this one. How much time is it taking, how much time
does it take to research a problem, write up the solution,.
I don't respond to emails when the solution to the issue is evident.
On Nov 8, 2007, at 8:02 PM, VaShaun Jones wrote:
There is no excuse for not answering e-mails no matter the company or
status, bug fixes or not. If you submit a e-mail that is valid,
understandable and related to a issue, problem or praise. The proper
thing at a minimum is to respond. Trust me that accessibility e-mail
address is not the forum that the developers are reading. Not
responding to e-mails is ridiculous
On Nov 8, 2007, at 5:37 PM, David Poehlman wrote:
If you were sitting in theire seat and had a choice of responding to
messages all day or fixing bugs, what would you do?
On Nov 8, 2007, at 5:16 PM, Dan Keys wrote:
Hello Rich and list,
I'd like to make an obxervation regarding my experiences with
Apple's Accessibility Group.
Never in the numerous times that I've written to
[EMAIL PROTECTED]
have I ever got a responce. It would be better for someone to
respond to email, than to never respond. I know that a few people
have received replies from Apple's Accessibility group, but I sure
never have. It kind of gives the appearance that they don't want
anything to do with the customers who use Apple's products, in
particular, VoiceOver or any other accessibility applications.
On Nov 8, 2007, at 1:53 PM, Rich Caloggero wrote:
I want to file a bug / suggestion with Apple, specifically related to
Safari, VoiceOver, and Webkit. Should I simply send eMail to
[EMAIL PROTECTED], or should I goto the webkit.org site and
use their
bug tracking system?
I guess what I'm really asking is: which software is controling the
behavior
I see with respect to VoiceOver and the web (Safari, Webkit, or
VoiceOver)?
I assume that there is no simple answer to this question, and that
to some
extent all three are involved.
A related question: if I send mail to [EMAIL PROTECTED], are
there
guidelines or a certain form the message must follow, aside from
the usual:
include specific version numbers of all components, provide test
cases, be
clear about what the problem is, and provide clear steps to
reproduce?
Thanx much in advance.
-- Rich
