The word "feature" and "accessibility" in the same sentence always
makes me uneasy. No, I wouldn't expect Avid to have a VO guru on hand
to figure out the most efficient workflow for me to get something
done, just like I don't expect every support techie to have the
knowledge to instantly switch off the "drag and drop" terminology in
his script every time I call Apple, but if a task isn't achievable via
the keyboard or isn't achievable with VO due to elements not being
exposed or being incorrectly defined etc, surely it's not unreasonable
to expect acknowledgement and response to that. In most cases it would
after all, be an issue that could be fixed with no specialist
knowledge of anything more than Apple's developer guidelines. I
suppose what I'm getting at is this. VO support not being publicly
stated (even the current partial VO support puts them ahead of the
game compared to Apple themselves) makes me uneasy that we're not
going to be publicly acknowledged as a userbase either. So, if that's
the case, what happens about new features or interface tweaks from
here on in? As I said, I totally agree that Avid implementing Apple's
accessibility guidelines is the most that we could expect from them,
and I am grateful for what's been implemented so far, but consistency
is key to this being a viable product for VO users to be able to rely
upon it professionally. I have to wonder whether implementing those
guidelines and ensuring that new features aren't going to be totally
beyond users of accessibility will be considered as part of the
development cycle, or whether the best we can expect is playing catch
up every few years.

I'm not intending to knock Avid. It's just this whole notion of
accessibility as a feature really, really bugs me.

On 6/30/10, Slau Halatyn <[email protected]> wrote:
> I'm preparing an update for the web site at ProToolsPetition.org. For what
> it's worth, I'll post it here first because it probably won't post to the
> web site for another day or two.
>
> Update Summer 2010
>
> It seems that the fruits of many people's labor are finally beginning to
> show. After years of interfacing with Digidesign, now known as Avid
> Technologies, we're seeing the results of our efforts to gain access to Pro
> Tools. Changes to the code base of Pro Tools that make it easier to navigate
> the user interface with VoiceOver in OS X were implemented in version 8.0.4.
> In early June, the HD version was released with the LE and M-Powered
> versions to follow soon.
>
> While there was a great amount of work done to help make Pro Tools useable
> with VoiceOver, it is by no means a completed project but rather a work in
> progress. While major aspects of the application are accessible, there
> remains some areas that will need to be addressed in future versions. We
> always knew that the issue of accessibility to Pro Tools would need a
> long-term solution. We hope to see improvements to be rolled out over
> several releases in the coming years.
>
> Although Avid Technologies has made changes to Pro Tools to specifically
> work better with VoiceOver, it has no plans to announce it as an official
> feature, per se. Regarding it as a feature would imply thorough testing and
> full customer support from the perspective of usability with VoiceOver.
> Naturally, one wouldn't expect Avid to troubleshoot issues regarding
> accessibility and the use of a screen reader. Essentially, what Avid has
> done is they've begun to label UI elements according to Apple's programming
> guidelines. The rest of the user experience has more to do with how
> VoiceOver works and best practices as blind users of the operating system
> and application software.
>
> Again, since this project is still a work in progress, it's still somewhat
> experimental as we discover what works and what doesn't. Although Pro Tools
> is not yet 100% accessible in all of it's areas, I'm glad that the work done
> thus far was included in the 8.0.4 release. It will allow blind users to
> begin learning the Pro Tools environment and workflow with plenty of
> features to explore and master. In the mean time, Avid is aware of the
> PTAccess email list at GoogleGroups.com and will direct any inquiries from
> blind users to the growing community of users in the group. Any issues of
> accessibility can be discussed there and any bugs or feature requests will
> be aggregated for future submission to Avid.
>
> I'll continue to post any major updates here but for the latest information
> go to
> http://www.googlegroups.com/group/ptaccess
>
> Slau Halatyn

Reply via email to