Skip to content
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.

Section 2.2.2 - Testing functionality (Hanno Lans) #37

Closed
darthcav opened this issue Aug 20, 2014 · 2 comments
Closed

Section 2.2.2 - Testing functionality (Hanno Lans) #37

darthcav opened this issue Aug 20, 2014 · 2 comments

Comments

@darthcav
Copy link

Reference

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

Original Comment

"Some tools do not declare that they only perform automatic testing. Since it is a known fact that automatic tests only cover a small set of accessibility issues, full accessibility conformance can only be ensured by supporting developers and accessibility experts while testing in manual and semiautomatic mode." At the other hand tools exists that are not doing full-automatic testing, but only giving feedback for manual evaluation (like inline suggestions). These tools give a lot of possible errors, but are not good in detecting failures. It would be great that a user knows how many tests are done automatically, and how many tests are 'selectors' for detecting possible errors.

@darthcav darthcav added generic and removed generic labels Aug 20, 2014
@nitedog nitedog changed the title Section 2.2.2 (Hanno Lans): Testing functionality Section 2.2.2 - Testing functionality (Hanno Lans) Sep 1, 2014
@nitedog
Copy link
Contributor

nitedog commented Sep 1, 2014

Resolution

Partial - the terms in section 2.2.2 will be better explained through issue #54. Issue #45 will further elaborate on the scope of automatable checks.

@ysmartin
Copy link
Contributor

ysmartin commented Sep 3, 2014

Related to #2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants