W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2011

Re: approches of canvas accessibility

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Mon, 8 Aug 2011 08:32:24 -0500
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Cc: paniz alipour <alipourpaniz@gmail.com>, Charles Pritchard <chuck@jumis.com>, Cynthia Shelly <cyns@microsoft.com>, david.bolter@gmail.com, Steve Faulkner <faulkner.steve@gmail.com>, Canvas <public-canvas-api@w3.org>, public-canvas-api-request@w3.org
Message-ID: <OF5400CDB8.A72DD63D-ON862578E6.004A494E-862578E6.004A60B8@us.ibm.com>

Yes, it achieves the same result (providing an accessibility object tree),
by default, without having to need the attribute.

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
To:	paniz alipour <alipourpaniz@gmail.com>
Cc:	Richard Schwerdtfeger/Austin/IBM@IBMUS, Charles Pritchard
            <chuck@jumis.com>, Canvas <public-canvas-api@w3.org>,
            public-canvas-api-request@w3.org, Cynthia Shelly
            <cyns@microsoft.com>, Steve Faulkner
            <faulkner.steve@gmail.com>, david.bolter@gmail.com
Date:	08/07/2011 06:19 AM
Subject:	Re: approches of canvas accessibility



On Sun, Aug 7, 2011 at 6:34 AM, paniz alipour <alipourpaniz@gmail.com>
wrote:
> I want to know about adom
> attribute:
http://lists.w3.org/Archives/Public/public-canvas-api/2010JanMar/0185.html
> that you were researching about it ,finally what has happened to it?

The proposal was rejected in favour of always using including the
content of the <canvas>  element in the accessibility tree.

--
Benjamin Hawkes-Lewis


graycol.gif
(image/gif attachment: graycol.gif)

Received on Monday, 8 August 2011 13:33:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:32 UTC