I dono...
I guess I have mixed feelings. I agree with you on the one hand, but I also
agree with Mike. October? Really?
OK, look at it this way, no, the newer technology wouldn't necessarily be
implemented this way nor be totally up to date par, but! why couldn't pace
give us two options, since they're so insistant on making this new platform.
It seems logical to me, why not put the web interface manager back like it
was a few years ago when things worked flawlessly? Put that back with those
A P I's, but then, also support a newer A P I which would let them build for
the current, and more updated software. This way, if you are sighted and
want to use the software, more power to! ya! But, if you're blind as most
of us! are, then you would have a fallback method which we still could use.
I understand completely that eventually, that old web based A P I needs to
be eventually rolled completely out, OK, I totally totally get that. You
might not think I do, but actually, yes. I do. Trust me with this. But,
does it not seem feezible to you all, that in the mingtime until they do!
come up with a way to get the new software working with good accessibility,
they at least! temporarily could re-enable the web interface as a fallback
for people like ourselves? Look at things like the Sendspace wizard. Now,
you're probably going and this has to do with the tea in China, how? LOL!
Hear me out on this though, as I really am trying to present a legitimate
argument here.
The Sendspace wizard on the mac, by default is not very accessible at all.
If you've not tried it, trust me. It's a living nightmare! However, there
is an option in the menu bar which enables accessibility mode. Once done,
it works... well... I'd not say perfectly, but I'd say almost! perfectly.
What about Tapin Radio on the Windows side of things. For the longest time,
they had an option when installing that you could check if you were a screen
reader user. If you check it, bam! Tapin is now accessible. If you don't,
then, good? freaking, luck! You'll be sorry you didn't check it, believe
me!
My point is, they were able to keep the inaccessible interface whilst
hooking seperet A P I's to allow an option to give accessibility mode. If
this is the case, then surely you could also do the same by having multiple
A P I's with the ILok manager. Maybe it's not that easy, and I by far am
definitely! not a programmer at heart, so really, honestly, in all fairness,
who am I to make such assumptions? I do think though that if Pace really
truely did! want to fix things, though I'm not complaining as much as being
very realistic here, I truely think they could figure some alternative out.
Even if it was only temporary.
What I don't understand is why one minute, the guy in his letter from Pace
states maybe in the mingtime, they could look at redoing some of the older A
P I's to regain some accessibility. But then, he says later on in the
letter that the 2.0 update will not have accessibility. He flat out admits
it! Then said maybe by October, with version 3.0 they'd look into it. OK,
so, are they going to give us back some A P I's, or not! Make up their
mind. It's like being pregnant. Either they are! going to, or, they're
not! going to. They can't go both ways, that I know of.
I know I'm probably gonna get the F*** tiched outta me for this message, so
go ahead. I can take the heat. I'm voicing my true not so humble opinion.
If people have a problem with me doing so, then, frankly, with all due
respect, tough shit. LOL! I mean, really, I'm sorry to be so harshly blunt
saying that, but I tell it as I see it.
Chris.
----- Original Message -----
From: "TheOreoMonster" <monkeypushe...@gmail.com>
To: <ptaccess@googlegroups.com>
Sent: Saturday, January 31, 2015 9:49 AM
Subject: Re: Letter Update from Pace Anti-piracy
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.
