Section 2.1.9 - New crawler features (Hanno Lans)

[darthcav]

Reference

http://lists.w3.org/Archives/Public/public-wai-ert-tools/2014Aug/0004

Original Comment

In Just Accessible we split the crawling mechanism and the testing mechanism. So in fact, a page is first crawled for the URLS, and after the sampling mechanism tested on WCAG2 in an emulated webbrowser (headless browser). At the moment I don't see the mechanism mentioned for the kind of test environment the tool has. There are possibly four test environments:

• downloading the raw resources and analyse those files.
• render the URL in an headless browser and analyse the DOM
• render the URL in a real browser and analyse the DOM
• render the URL in a set of browsers (for example a mobile emulator) and analyse the DOM's

In Just Accessible we choose the third option and are using phantomjs with webkit. But this has drawbacks as the HTML5 media API is not working

[nitedog]

Proposed Resolution

No change - Section 2.1 and 2.2 separate between "fetching and rendering" and "testing". We do not see that this document excludes any of the outlined mechanisms.

[ysmartin]

I don't think it is a matter of having excluded any mechanism, but a matter of not having considered them. There are different alternatives to build the DOM, which could be considered a feature. Maybe it could fit within the platform feature proposed at #32

[darthcav]

Resolution

Partial - Section 2.1.5 has been changed to explain the aspect of testing before and after rendering more clearly