I just got into the studio and confirmed the issue with trying to write 
automation using only VoiceOver. Over the years where we've had no less than 10 
VoiceOver users beta test Pro Tools, not once has anybody reported this issue. 
That, of course, is not surprising since most of the users have control 
surfaces and would never dream of writing automation using only VoiceOver. 
Those testers without a surface clearly never got around to testing this 
specific aspect. From an accessibility standpoint, the knee-jerk reaction is to 
look at things that are unlabeled or invisible, etc. Functionality such as this 
is taking it a step further and so it's not inconceivable how this could be the 
case. I've confirmed the behavior in both version 11 and 12 and I doubt it was 
any different going back to version 8.

Anyway, as I said earlier, this won't get fixed in the upcoming release but 
I'll submit a bug report for the future.

Slau

-- 
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.

Reply via email to