W3C home > Mailing lists > Public > public-html-a11y@w3.org > June 2010

Re: Fw: Draft Revisions to Canvas 2D Context API to drive magnification

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 3 Jun 2010 13:06:14 -0600
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: david.bolter@gmail.com, Frank Olivier <franko@microsoft.com>, Janina Sajka <janina@rednote.net>, Maciej Stachowiak <mjs@apple.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, public-html-a11y@w3.org
Message-ID: <OF26C7AD14.578B7692-ON86257737.0068D0C2-86257737.0068F088@us.ibm.com>


You grabbed an old copy of the document:

Please review:

(See attached file: 2dcontext10-May-26.html)

Rich Schwerdtfeger
CTO Accessibility Software Group

             Steven Faulkner                                               
             mail.com>                                                  To 
             06/01/2010 12:55          Schwerdtfeger/Austin/IBM@IBMUS      
             PM                                                         cc 
                                       Maciej Stachowiak <mjs@apple.com>,  
                                       Frank Olivier                       
                                       <franko@microsoft.com>, Janina      
                                       Sajka <janina@rednote.net>,         
                                       Re: Fw: Draft Revisions to Canvas   
                                       2D Context API to drive            

hi rich,
editorial: remove second 'is'

"If the drawCustomRing argument is true, then the author is wishes to draw
a custom focus ring around the element in which case the user agent will
only draw the focus ring if the user has specifally configured the
operating sytem to draw focus rings in a particular manner in which case
the author would not be approved to draw a custom focus ring. (For example,
high contrast focus rings.) "

the rest looks good to me.

On 29 April 2010 22:25, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:
  Hi Maciej,

  I have not heard back from Apple on this proposal. Please take a look at
  the proposal (attached HTML file) and let me know if this will work for
  the Mac. I think I addressed your issues and would like your feedback.

  We have an MSAA API call on Windows which we can call to set the Caret
  Position so that a magnifier can can follow it which can be used by IE
  and FF.

  I don't know if you have a similar API for the Mac where the selection
  position could drive the magnifier.



  Rich Schwerdtfeger
  CTO Accessibility Software Group
  ----- Forwarded by Richard Schwerdtfeger/Austin/IBM on 04/29/2010 04:17
  PM -----
 Sent by:                                                                  
 public-canvas-api-reques                                               To 
                                 Frank Olivier <franko@microsoft.com>,     
                                 Janina Sajka <janina@rednote.net>, "      
 04/11/2010 06:49 PM             public-canvas-api@w3.org" <               
                                 public-canvas-api@w3.org>, Steven         
                                 Faulkner <faulkner.steve@gmail.com>,      
                                 Draft Revisions to Canvas 2D Context API  

  Sorry it took so long for me to get this draft out. Too much traveling
  going on. Please take a look and provide feedback.

  The edits reflect:

  - Separate caret/selection from drawFocusRing
  http://lists.w3.org/Archives/Public/public-html/2010Mar/0502.html. The
  Mac does not support caret tracking during selection so this needed to be
  allotted for.
  - Expose the caret blink rate via 2D canvas API. Frank indicated Windows
  has a 500 millisecond defult blink rate a. Carl Carlson (Apple) indicated
  a default blink rate of 560 milliseconds. I provided information for
  authors regarding average default blink rates should the value returned
  be negative 1.
  - Change the name of canDrawCustom and clean up its definiton which
  according to Maciej is "want to draw custom unless Special Focus Ring
  Setting is in Effect"

  David Bolter: From the Firefox perspective we still need to see that the
  caret/selection location can be properly mapped to the accessibility API
  as is. Currently, the caret position is a logical one in IA2 and I
  believe the caret pixel position is calculated from the character font
  offset and the bounding rectangle of the text. We may need to move the
  system caret. I am trying to find the old Windows API for that.

  Frank: Please see if we can map the pixel position accurately, when
  provided, from the accessibility API. Windows used to have an MSAA
  notification for driving a magnifier based on screen position. I don't
  know if this is still used when using UIA Express.

  Maciej or James: Same question for Mac regarding the caret/selection

  (See attached file: 2dcontext10-Apr-11.html)

  Rich Schwerdtfeger
  CTO Accessibility Software Group(See attached file:

with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -

(image/gif attachment: graycol.gif)

(image/gif attachment: pic08280.gif)

(image/gif attachment: ecblank.gif)

Received on Thursday, 3 June 2010 19:07:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:40 UTC