Hi all! Ok This sounds like a good thing to me! If those of you who can use this to help dev's and they respond this only can be good! And like someone already said it's better than fix it! :] Colin
I'm far too bad for Heaven! The Devil is afraid I'll take his place! On 8 Mar 2011, at 14:10, Bryan Jones wrote: > Hello Yuma, > > Just to clarify -- Are you saying that if we have the xcode tools on our Mac > we can plug any App from the App Store into the Accessibility Verifier and > get this sort of report? I would have thought this would only work with the > raw code and not with compiled Apps as purchased from the App Store. If this > is indeed possible, this will be a great addition to the information we can > submit to Developers when discussing the accessibility of their Apps. > Everybody with a Mac has access to the IOS developer tools by registering as > an Apple Developer and purchasing the IOS Development kit, which is currently > US $99.00. > > Thank you, > Bryan > > On Mar 8, 2011, at 4:53 AM, Yuma Decaux wrote: >> I've looked into the accessibility tools available in xcode, and there's an >> interesting one which is the accessibility verifier which tests >> accessibility defaults with the standard apple api and breaks down every >> element of a given application, checks whether ax attributes have been >> placed and what errors or warnings come out of each. >> >> For instance, i have tried opening an inaccessible synth called the >> swarmatron and it warns of a lack of a focus on the main window, looking >> down into it, i see all standard close minimise etc windows have ax >> attributes and the main window has none. Maybe digging deeper into the >> structures of more accessible applications, one can actually provide the >> classes used by the standard api and send a schematic view with relevant >> classes to be inputted to the developers, screenshots included? >> >> I have recently been working with a drum synth developer in rendering his >> application totally accessible and we are going through the initial steps of >> testing custom accessibility for image maps for example, and he acknowledged >> the fact that his own hierarchy of elements is much clearer with >> accessibility plugged in as it allows for a very concise view of his >> application, cross links and class hierarchies. >> >> Maybe this is something to look into further and perhaps crowd source some >> form of reference material beyond what apple offers to give a boost to some >> of the more reticent developers? >> >> I am talking mainly about sound application devvers whose interfaces are >> commonly image maps with custom elements, however them being coded in >> standard apple fashion. >> >> The instance of the drum synth devver being able to quickly make custom >> elements, and i echo his words "adding accessibility is not a difficult task >> nor is it a slow process" means that provided a concise explanation or >> mini-manual of the concepts of accessibility, with a section on the actual >> advantages of having this structure added to one application, meaning >> elegant universal code, this might break some grounds in multiplying or >> standardising accessibility on the mac ecosystem. >> >> Going back to the workbench >> >> >> Best regards, >> >> Yuma >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To post to this group, send email to macvisionaries@googlegroups.com. >> To unsubscribe from this group, send email to >> macvisionaries+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/macvisionaries?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionaries@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
