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

Checking against whole WCAG / S508 no longer works #268

Open
mlewand opened this issue Aug 21, 2014 · 0 comments
Open

Checking against whole WCAG / S508 no longer works #268

mlewand opened this issue Aug 21, 2014 · 0 comments

Comments

@mlewand
Copy link
Member

mlewand commented Aug 21, 2014

Checking against whole WCAG / S508 no longer works

Previously (at least at version 2.1.1) I was able to do a full checking against WCAG / Section 508 with following call:

$( checkedContainer ).quail({
    guideline : 'wcag',
    jsonPath: 'dist',

    complete: function() {
        // Further actions...
    }
});

After updating Quail with bower (to 2.2.6) this approach no longer works. Is there anything that I'm missing?

Steps to reproduce:

  1. Install Quail using Bower

    mkdir quail
    cd quail
    bower install quail
    
  2. Now lets build Quail

    cd bower_components/quail/
    npm install
    grunt build
    
  3. Create a new file !sample.html in Quail directory, so in the same that dist dir has been created. Set it to following content:

    <!DOCTYPE html>
    <html>
    <head>
        <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
        <title></title>
    </head>
    
    <body>
        <div id="test">
            <h5>foo</h5>
            <h5>bar</h5>
            <p>baz</p>
            <img src="examples/common/kogepan.png">
        </div>
    
        <script src="lib/jquery/jquery.js"></script>
        <script src="dist/quail.jquery.js"></script>
        <script>
    $(document).ready(function() {
        $('#test').quail({
            guideline : 'wcag',
            jsonPath: 'dist',
    
            testFailed: function(event) {
                console.log( 'testFailed callback called' );
            },
            complete: function() {
                console.log( 'complete callback called' );
            }
        });
    });
        </script>
    </body>
    </html>
  4. Open created page in web browser.

  5. Check develoepr console.

Expected result:

It should report some errors, and should finish with

complete callback called

entry at the very end.

Actual result:

Both testFailed and complete are not called.

What's more, preserved samples does not work either. But I guess it's already reported as #264.

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

No branches or pull requests

1 participant