incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Francis Buhler <davidbuh...@gmail.com>
Subject Re: Pushing Flex components thorough the GPU
Date Fri, 27 Jan 2012 01:53:59 GMT
Listening to the screen reader's robotic voice reading the same content
over and over for 100s of hours while testing accessibility....now,
that...is a nightmare.
On Jan 26, 2012 8:25 PM, "Rick Winscot" <rick.winscot@gmail.com> wrote:

> What would be great for 508 is to implement first class mechanisms for
> accessibility ... creating new components that are accessible (the Flash
> way) is a nightmare.
>  On Jan 26, 2012 5:53 PM, "Michael Jordan" <mijordan@adobe.com> wrote:
>
> >
> > On 1/26/12 1:54 PM, "Alex Harui" <aharui@adobe.com> wrote:
> >
> > >> -----Original Message-----
> > >> From: David Francis Buhler [mailto:davidbuhler@gmail.com]
> > >> Sent: Thursday, January 26, 2012 10:48 AM
> > >> To: flex-dev@incubator.apache.org
> > >> Subject: RE: Pushing Flex components thorough the GPU
> > >>
> > >> Windows, Jaws, jaws scripts, and IE. :)
> > >> On Jan 26, 2012 1:29 PM, "Alex Harui" <aharui@adobe.com> wrote:
> > >>
> > >I'm not the expert, but one of our Adobe PPMC members is (Michael, are
> > >you out there?), but I believe we work with more than just Jaws and IE.
> > >
> > >
> > >Alex Harui
> > >Flex SDK Developer
> > >Adobe Systems Inc.
> > >Blog: http://blogs.adobe.com/aharui
> > >
> > >
> >
> >
> > That's correct, Alex.
> >
> > Screen reader support for the Flash Player is available on Windows in IE
> > and Firefox for swfs embedded with wmode="window."
> >
> > JAWS, Window-Eyes, and the open source NVDA screen readers can read Flash
> > content, but to date JAWS has the most comprehensive support for Flex.
> > This is because JAWS has scripts that work around limitations with the
> way
> > that the Flash Player is able to describe content through its
> > accessibility API.
> >
> > The Flash Player's accessibility support was implemented back in 2002,
> > around the time that the term "rich internet application" was coined. To
> > limit the performance impact of maintaining, updating, and communicating
> > role, state, and value information on a deep hierarchy of accessibility
> > objects, the decision was made to only expose one level of hierarchy and
> > allow an accessibility object like a list to maintain a single array of
> > children with no decedents. This is unlike the behavior of desktop
> > applications which are able to expose the full hierarchy of a tree,
> panel,
> > or data grid with nested children. JAWS scripts improve the way the
> screen
> > reader user interacts with more complex controls like the TreeView and
> > ComboBox in IE.
> >
> >
> > Michael Jordan  |  Accessibility Engineer  |  Adobe
> >
> >
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message