You? thanking me? I'm humbled! Frankly, if anyone in this should be
thanked, it's you! You have gone out of your way! to make this software
easy for us to use. I'd just like to apologize for the verbal attack I put
on Apple the other day regarding them not being committed to accessibility.
I do still feel that sometimes they get in over their heads, and probably
procrastinate doing certain things, but, that doesn't excuse the public
comments that I made. With that said, I genuinely ask that you accept my
apology.
Thank you kindly,
Christopher-Mark Gilland.
Founder of CLG Productions
Blog:
http://www.clgproductions.org
Podcast:
http://clgproductions.podhoster.com
E-mail:
[email protected]
IMessage/Facetime:
[email protected]
Windows Live Messenger:
[email protected]
Twitter:
@gilland_chris
Facebook:
http://www.facebook.com/christopher.gilland
Skype:
twinklesfriend2007
Send me a fax from any standard fax machine:
704-697-2069
Google Voice: (Please use sparingly):
980-272-8570
----- Original Message -----
From: "Slau Halatyn" <[email protected]>
To: <[email protected]>
Sent: Wednesday, November 14, 2012 3:26 PM
Subject: Re: This is wonderful! Fw: Problem with accessibility in Mountain
Lion
thanks for your persistence, Chris.
Cheers,
Slau
On Nov 14, 2012, at 3:25 PM, Christopher-Mark Gilland wrote:
Guys,
This is excellent! Look at this reply from Apple. Looks like maybe we're
finally getting somewhere, hopefully.
----- Original Message ----- From: <[email protected]>
To: <[email protected]>
Sent: Wednesday, November 14, 2012 2:23 PM
Subject: Re: Problem with accessibility in Mountain Lion
Hello,
Thank you for your email. We've passed this on to the appropriate people
for their investigation.
Apple Accessibility
Follow-up: 238800260
With all do respect, I have to completely disagree with what you're
saying.
It worked fine in both Snow Leopard and in Lion, so there is absolutely
no
excuse for it not working in Mountain Lion.
Before you fire me back a canned response reidderating what you already
said, I encourage all of you at accessibility to first have a look at
this
for more information before jumping the gun saying it's Avid's issue, not
you all's.
http://avid.force.com/pkb/articles/en_US/Download/Pro-Tools-10-3-2-Downloads
