Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of davidbuhler@gmail.com
 designates 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADzDP+L2tO-mSEntdSU6bek_p8s=14ua5RZ-U4tJxG87oSQO5Q@mail.gmail.com>
References: 
 <CADzDP++MGY+r5wpb67K1Byne58KZpBLtixdy2zvsrngbYB7hcQ@mail.gmail.com>
	<CB43B044.3AD7F%aharui@adobe.com>
	<CADzDP+KOMacKPYFLfFwb3KwJ1gzwTttRH4RYZ9Z-6Db-3=LHoA@mail.gmail.com>
	<CAAgciqrFx8eV+VFnt8tehJ5jca3UgVKsaBT7rntMRzrOEKp13Q@mail.gmail.com>
	<CADzDP+J+hdXJjHYJTDPZeoXti13TKqB0HAojVu7crc0tEeaoYA@mail.gmail.com>
	<CAAgciqoFKrxzA7kD1-SzAA46XZsJgOLc5qw8X9dH3K-OkOvWPQ@mail.gmail.com>
	<DUB110-DS27537134F416EB7C3F96AAA38B0@phx.gbl>
	<CAAgciqp_bQ8E0YcnMs=iAiwwOpdb61TdJ_1ki7EQgJQBVNcfNw@mail.gmail.com>
	<DUB110-DS27DD3A237CA6D97423AEC9A38B0@phx.gbl>
	<CADzDP+LVrYF_r7cKGTsjnENdPzth-2zOdfTFAmFM8acjpgfwtw@mail.gmail.com>
	<CA+ckY6uV3zCXnX-P1zSHeGjP=DdAGydEVYcEFY92-B=phfFmQQ@mail.gmail.com>
	<4F1F2FD4.4010308@brentarnold.com>
	<CADzDP+L2tO-mSEntdSU6bek_p8s=14ua5RZ-U4tJxG87oSQO5Q@mail.gmail.com>
Date: Tue, 24 Jan 2012 18:57:31 -0500
Message-ID: 
 <CAH12+xOX0nDrC+s2nh8SmPehJM-bdCEYa8bS1eoanUJx9kMDmg@mail.gmail.com>
Subject: Re: Pushing Flex components thorough the GPU
From: David Buhler <davidbuhler@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=14dae934042d01246904b74ee9fc

--14dae934042d01246904b74ee9fc
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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=92s type. Examples ar=
e
   =93Add=94 or =93Play.=94
   -

   *Traits*. A combination of one or more individual traits, each of which
   describes a single aspect of an element=92s state, behavior, or usage. F=
or
   example, an element that behaves like a keyboard key and that is current=
ly
   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 =93Adds a title=94 or =93Opens the sh=
opping
   list.=94
   -

   *Frame*. The frame of the element in screen coordinates, which is given
   by the CGRect structure that specifies an element=92s screen location an=
d
   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
   =93Speed,=94 but its current value might be =9350%.=94"

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 <lostirc@gmail.com> wrote:

> I'm really interested in how this carries over to mobile, does anyone hav=
e
> 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 platfor=
m.
>
>
>
>
> On Tue, Jan 24, 2012 at 5:25 PM, Brent Arnold <brent@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 transfe=
rs
> >>> over to a mobile environment?
> >>>
> >>>  Don't think this ever got addressed. For mobile is this stuff even a=
n
> >> issue? I have no idea how this works. Are there screen readers that re=
ad
> >> the UI elements of an iOS app?
> >>
> >>
>
>
> --
> Francis Altomare,
>

--14dae934042d01246904b74ee9fc--