- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Wed, 6 Nov 2013 11:08:14 -0600
- To: "Charles McCathie Nevile" <chaals@yandex-team.ru>
- Cc: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
- Message-ID: <OF4860C6BB.AA641638-ON86257C1B.005DDFC9-86257C1B.005E2384@us.ibm.com>
+1 We have drawSystemFocusRing() almost done on FF 28 nightly Windows and Mac. There is one small bug I identified and Rik Cabanier has agreed to fix. We will be testing drawCustomFocusRing as well but it has been implemented in FF 28. Both are fully working in Chrome Canary for Windows and Mac OSX. Implementation will not be a problem. Rich Rich Schwerdtfeger From: "Charles McCathie Nevile" <chaals@yandex-team.ru> To: "public-html-a11y@w3.org" <public-html-a11y@w3.org> Date: 11/05/2013 01:23 AM Subject: Call for Consensus: Canvas 2d spec Hi folks, this is a call for consensus on the following two propositions: The HTML Accessibility Task Force accepts that path objects and relevant methods operating on them, hit regions, text metrics other than width, and ellipses could be moved to Canvas2d level 2 - i.e. a later verion of the specification. The HTML Accessibility Task Force accepts that the drawSystemFocusRing and drawCustomFocusRing methods on elements in the "canvas shadow DOM" are "at risk" in Canvas2D - and that without implementation, the Canvas2D specification could drop them to move to Recommendation. For more background to these questions, please see http://www.w3.org/2013/10/31-html-a11y-minutes.html#item03 Silence will be considered assent, but positive answers for each of the two propositions are preferred. Responses will be accepted until Midnight Hawaiian time on Wednesday November 13, and should be made in this email thread. for the facilitators Chaals -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex chaals@yandex-team.ru Find more at http://yandex.com
Attachments
- image/gif attachment: graycol.gif
Received on Wednesday, 6 November 2013 17:10:00 UTC