Really don’t want to get in a back and forth about this, I would
rather we save our energy for the accessibility challenges outside of
this forum.
Also my schedule won’t allow it.
From first hand knowledge ProTools 10, and 11, in Mountain Lion and
Mavericks was unusable.
When I say this was fixed in les than two months, with out going in to
details just know I’m not guessing.
I understand that we all have different motives for wanting to get
things fixed
For some of us it’s our work, for some of us it’s training, and for
some it’s just a hobby, so I understand some may be abit more
aggressive about timing than others.
I’m not interested in a divisive discussion here because I’m a where
of where our focus must be.
So once again for every one no matter the process, who forced Mr.
Cornce to at least respond, thanks again.
On 1/31/15, Mike Lockett <mloc...@gmail.com> wrote:
> On 1/31/15, TheOreoMonster <monkeypushe...@gmail.com> wrote:
>> How quickly we forget. There was a fair amount of work that went into PT
>> regarding modernizing and updating a lot of the code base to get to the
>> point where all that was needed to be done was label elements and
>> buttons.
>> Yes that process went relatively quick once the Program got to a point
>> where
>> that could be done. If memory serves correct it was at least a couple of
>> years in-between when initial processes started to when access labeling
>> began. It appears we are in the same holding pattern with pace at the
>> moment.
>> On Jan 31, 2015, at 9:41 AM, Mike Lockett <mloc...@gmail.com> wrote:
>>
>>> To everyone that sent a letter to the B-B-B or made a call to Pace,
>>> Feel assured you are being heard.
>>> Pace’s CEO E-O Allen Cornce in an email to Slau Halatyn made reference
>>> to a complaint,
>>> Quote, “What I don't agree with is the assertion that accessibility
>>> support is simple and easy. If it was, we would have rolled it out and
>>> been done with it ages ago.””
>>>
>>> Personally I think its HOGWASH!!!
>>> When accessibility is taken seriously and made a priority Avid
>>> Technology is a perfect example things can get fix in an appropriate
>>> time.
>>> In Avid’s case their were a thousand moving parts in the UI of the Ap,
>>> most of the accessibility issues were fixed in les than two months
>>> once it became a priority.
>>> Labeling some elements, and buttons should never take until October…
>>>
>>> We may disagree on how to get this done,
>>> but we agree it must be done…
>>>
>>> If we keep working the back channels we will achieve our desired
>>> results.
>>> In other words lets keep working.
>>> For some of you who may disagree or for other reasons just can’t,
>>> We will respect you.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups "Pro
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
