It appears as though a Mobile Form Factor takes into consideration screen-coordinates for controls. The remaining properties are common accessibility approaches on a Desktop/Browser application.
"Hints" is similar to the Flex Frameworks's "accessibility.description". Apple's VoiceOver documentation has the concept of a 'frame', or 'coordinates'. The UI Accessibility programming interface defines the following attributes: - *Label*. A short, localized word or phrase that succinctly describes the control or view, but does not identify the element’s type. Examples are “Add” or “Play.” - *Traits*. A combination of one or more individual traits, each of which describes a single aspect of an element’s state, behavior, or usage. For example, an element that behaves like a keyboard key and that is currently selected can be characterized by the combination of the Keyboard Key and Selected traits. - *Hint*. A brief, localized phrase that describes the results of an action on an element. Examples are “Adds a title” or “Opens the shopping list.” - *Frame*. The frame of the element in screen coordinates, which is given by the CGRect structure that specifies an element’s screen location and size. - *Value*. The current value of an element, when the value is not represented by the label. For example, the label for a slider might be “Speed,” but its current value might be “50%.”" Note: I would assume the smaller component set of a Mobile Form Factor makes a mobile device easier to build accessible components for (fewer components to make). I wonder if one can write an ANE to communicate between AIR and VoiceOver on iOS? On Tue, Jan 24, 2012 at 6:16 PM, Frank Altomare <lost...@gmail.com> wrote: > I'm really interested in how this carries over to mobile, does anyone have > some information on the state of accessibility on mobile devices? This > seems like an interesting topic in it's own right. > > I really think GPU UI components would be best utilized on mobile. This > feature would also really make Flex shine as a mobile development platform. > > > > > On Tue, Jan 24, 2012 at 5:25 PM, Brent Arnold <br...@brentarnold.com> > wrote: > > > Apple has it's own implementation of accessibility. > > http://developer.apple.com/**technologies/ios/**accessibility.html< > http://developer.apple.com/technologies/ios/accessibility.html> > > > > But it doesn't do much with AIR apps. > > > > > > On 1/24/12 3:14 PM, Doug McCune wrote: > > > >> While on the topic of accessibility, does anyone know how this transfers > >>> over to a mobile environment? > >>> > >>> Don't think this ever got addressed. For mobile is this stuff even an > >> issue? I have no idea how this works. Are there screen readers that read > >> the UI elements of an iOS app? > >> > >> > > > -- > Francis Altomare, >
