Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C547E969A for ; Tue, 24 Jan 2012 23:18:00 +0000 (UTC) Received: (qmail 26757 invoked by uid 500); 24 Jan 2012 23:18:00 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 26687 invoked by uid 500); 24 Jan 2012 23:17:59 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 26679 invoked by uid 99); 24 Jan 2012 23:17:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jan 2012 23:17:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lostirc@gmail.com designates 209.85.216.54 as permitted sender) Received: from [209.85.216.54] (HELO mail-qw0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jan 2012 23:17:54 +0000 Received: by qaea17 with SMTP id a17so2809148qae.6 for ; Tue, 24 Jan 2012 15:17:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Q5effDxUYJ0mkGOILN9TsVXjMEaTpUDv3eAKN0zeecQ=; b=x+i0ct3wBrVwTSTjAfMSDv9b1PJjJmSEonczpVTAWiA7hcMM8R9w8th5O58nb5/UPl qDPhhVhM1KbR5jfT/gbY4NZEpbfKDsY8EI48Dzoli403sf9h7Uc+eb8gHT+iKt0hplPm zlRxjsmJsWSf58ZAfQf5Ul3gndZmTKUFLDG8A= Received: by 10.224.185.16 with SMTP id cm16mr17812272qab.0.1327447053140; Tue, 24 Jan 2012 15:17:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.90.14 with HTTP; Tue, 24 Jan 2012 15:16:52 -0800 (PST) In-Reply-To: <4F1F2FD4.4010308@brentarnold.com> References: <4F1F2FD4.4010308@brentarnold.com> From: Frank Altomare Date: Tue, 24 Jan 2012 18:16:52 -0500 Message-ID: Subject: Re: Pushing Flex components thorough the GPU To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf302ef84a0f814704b74e5ace --20cf302ef84a0f814704b74e5ace Content-Type: text/plain; charset=ISO-8859-1 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 wrote: > Apple has it's own implementation of accessibility. > 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, --20cf302ef84a0f814704b74e5ace--