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

What I think we need

From: Jay Munro <jaymunro@microsoft.com>
Date: Fri, 5 Sep 2014 00:29:56 +0000
To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "Rik Cabanier (cabanier@adobe.com)" <cabanier@adobe.com>, "Mark Sadecki (mark.sadecki@gmail.com)" <mark.sadecki@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
Message-ID: <5e79f096faa045a4b635908cdd134a93@DM2PR03MB527.namprd03.prod.outlook.com>
Here's where I see things with the testing, gleaned from our discussions previously. 

 What am I missing? 

1. There are some tests for drawFocusIfNeeded in the canvas collection. According to Philippe, they seem to be up-to-date. Are they enough?
2. Mark wrote some tests for Hit Regions, but mentioned that he needed to update them. Those aren't in the collection. We need hitRegions, clearHitRegions, addHitRegion, and removeHitRegion. 
2. Rich posted a link to the test harness they use for WAI-ARIA - http://www.w3.org/WAI/PF/testharness/ and Michael Cooper added that it has public read access, but write access is restricted to members of the PFWG (I'm not sure what PF is). Can this harness be used to test? 
3. Rich gave a set of details for testing the features:
	- Covering multiple hit regions
	- Covering fallback content that uses a standard basic HTML5 control (I would choose a button), a link, and an aria enabled button or control. We then validate the regions map to the bounds 	on the accessibility API
	- Make we can see the bounds drawn as we move focus using the drawFocusIfNeeded function to render the visible focus. 
	- Make sure a magnifier can follow the keyboard focus location on the screen
	- Test it with a screen reader
	- Test it with an inspection tool. 
	- test to make sure the id of the object in the hit matches the element you are hovering over. 
	- Move the browser window or scroll the window to make sure that the new location on the screen reflects the new bounds location. 

4. We'll need to figure out: 
	a. Who can write or update the tests. Sounds like Rich and Mark have this pretty much under control. 
	b. Someone to run the tests (more than one). Determine if the drawFocusIfNeeded tests are current, and run any others. It's still open to whether these tests can be automated. 
	c. Define where the results get reported.
	d. A summary.  



Jay Munro  Content Developer 2 Internet Explorer     85/2275    425-703-2242 
Received on Friday, 5 September 2014 00:30:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:57 UTC