Oh, i forgot to mention in the previous thread, on the labels. The reason why we read button1 everywhere in a lot of flash when using jaws is because of the instanciation of a button, which then aren't properly named, so the default button1 residing in the main library is called. There will not ever be a workaround in this, unless adobe does something such as force the devver to label each of his/her buttons instances.
Two hurdles then for VO users to adress: 1-Drawing methods used in the flash portion of safari, core animation instead of other methods, coco instead of carbon. 2-standardization of labels from all flash devvers. The first seems to be coming up with flash 10.1, meaning we will have the same level of accessibility as jaws or window eyes users. The second is not as evident, as myself used to, though being meticulous, omit a lot of the labelling chores. At any rate, if flash can use the core animation API, it means that, just like skype, there will be access to at least the upper-layers of the flash code via coco, therfore via scripting native to the mac. THis is going to be good :) Yuma Decaux Light has no value without darkness Skype: shainobi1 blog: www.theblindsamurai.com twitter: www.twitter.com/triple7 Tel: +85513623378 -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
