Re: Action-1640

Sorry, I am still dealing with the backlog from before vacation.

WebDriver is *not* Windows specific and it works on the Mac:
http://docs.seleniumhq.org/about/platforms.jsp

Selenium webdriver also runs using different programming platforms:
http://docs.seleniumhq.org/about/platforms.jsp

Joanie was doing work with python.

We also need to test more than role mappings. That said, I agree we need to
push more on computedRole and other DOM interfaces. However, that is only
the tip of the iceberg. There are a whole litany of issues involving CSS,
and web components that will make going through the DOM problematic on its
own.  We also need to test platforms that don't resolve to a role attribute
mapping like Android.

I want to avoid the manual testing that we had to do in ARIA 1.0 and the
best way to get there for a 1.1 time frame is through Selenium and
automated testing.

Rich


Rich Schwerdtfeger



From:	James Craig <jcraig@apple.com>
To:	Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc:	PF <public-pfwg@w3.org>, WAI XTech <wai-xtech@w3.org>
Date:	05/21/2015 12:29 PM
Subject:	Re: Action-1640




> On May 21, 2015, at 6:42 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:
> We are doing that James but we need a layer that works with web driver

WebDriver is a Windows-specific tool. Perhaps even specific to Internet
Explorer, is it not?

> and Selenium that talks to the API exposed by webkit. We are doing this
to test the accessibility API mapping on all the platforms.

That sounds a lot like the old AIA project. Have any other UA implementors
expressed an interest in this?

Seems like the better approach is to push harder for Element.computedRole()
and other related DOM interfaces so these can be standard tests in
JavaScript through any number of platform-specific tools, including but not
limited to WebDriver, Selenium, etc.

James

> Rich Schwerdtfeger
>
> From:		 James Craig <jcraig@apple.com>
> To:		 Richard Schwerdtfeger/Austin/IBM@IBMUS
> Cc:		 PF <public-pfwg@w3.org>, WAI XTech <wai-xtech@w3.org>
> Date:		 05/20/2015 02:31 AM
> Subject:		 Re: Action-1640
>
>
>> I'm sorry, no. I can't commit anyone's time to this at the moment.
>>
>> I'd encourage you to take the TTWF approach [1] as much as possible.
Writing web standard tests using JavaScript that work in any browser will
be much more effective in the long run than writing platform-specific
wrappers introducing fragility.
>>
>> 1. http://testthewebforward.org
>>
>> On May 19, 2015, at 12:52 PM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:
>>
>>> Hi James,
>>>
>>> Do you have someone who can work with the aapi task force, that Joseph
chairs, to write web driver code to do automated testing of Safari for ARIA
1.1? We are working plans to do more automated testing for ARIA 1.1 and are
currently working out plans to do automated testing for IE, Chrome,Firefox
on Windows, and Firefox,Webkit on Linux.
>>>
>>> Rich
>>>
>>>
>>> Rich Schwerdtfeger
>>>
>