Non-functioning menu options

[patrickhlauke]

Currently (2015-05-20) not functioning/returning errors:

Check > HTML Validation quick check (returns error 501)
Check > W3C HTML Validator > all sub-options (return error 500)
Check > Functional Accessibility Evaluator (site changed, does not automatically check, though still usable)

Tables > Juicy Studio Table Inspector (reports that no tables are present, even when there are tables)

Doc Info > DOM Viewer (opens a new window, but doesn't seem to show anything)

Refs > Standards and specs > HTML5 Web Developer Edition (404)
Refs > Standards and specs > ATAG 1.0 (404)
Refs > Standards and specs > Section 508 (references to refresh and the various 508.1194...) (404)

[patrickhlauke]

Example of what currently happens with the "quick check"

[stevefaulkner]

Check > HTML Validation quick check (returns error 501)

suggest remove

Check > W3C HTML Validator > all sub-options (return error 500)

suggest remove

Check > Functional Accessibility Evaluator (site changed, does not automatically check, though still usable)

will look into this

Tables > Juicy Studio Table Inspector (reports that no tables are present, even when there are tables)

probably needs to be pulled unlees anyone wants to fix

Doc Info > DOM Viewer (opens a new window, but doesn't seem to show anything)

suggest remove.

[patrickhlauke]

re FAE see #95 - i'd say leave it as is, not much we can do at our end

[stevefaulkner]

@patrickhlauke re FAE

below is form code from the FAE site, the fae.ws needs updating to send same info

<form action="/run/anonymous/" method="post" name="fae20_run">
    <input name="csrfmiddlewaretoken" value="aFtMxdBbbJxrodXwbGv0KDLkrVGE4F1M" type="hidden">

    <div class="input">
        <label for="id_url">URL</label>
        <div class="error">
        <input id="id_url" name="url" required="" value="http://" size="60" title="Example: http://somewhere.org"> 

        </div>        
    </div>

    <fieldset>


        <legend>Ruleset</legend>



        <div class="fae20_radio">
            <input id="ruleset_1" name="ruleset" value="ARIA_STRICT" checked="checked" type="radio">
            <label for="ruleset_1" title="WCAG 2.0 Level A and AA requirements using ARIA and HTML5 accessibility features.">HTML5 and ARIA Techniques</label>
        </div>

        <div class="fae20_radio">
            <input id="ruleset_2" name="ruleset" value="ARIA_TRANS" type="radio">
            <label for="ruleset_2" title="WCAG 2.0 Level A and AA requirements using legacy HTML4 features, but allowing the use of ARIA and HTML5 accessibility features.">HTML4 Legacy Techniques</label>
        </div>

    </fieldset>

<!--        
   <p>Evaluation services temporarily disabled</p>
-->
    <input name="submit" value="Evaluate" style="margin-top: 2em" type="submit">
</form>

[patrickhlauke]

<input name="csrfmiddlewaretoken" value="aFtMxdBbbJxrodXwbGv0KDLkrVGE4F1M" type="hidden">

smells a lot like a constantly changing token (time limited?) to avoid automated submissions of the form. as such, i'm doubting that it would work to "spoof" a form submission

[stevefaulkner]

i will ping jon gunderson

[patrickhlauke]

indeed when I just visited it, the token value was uaOhYTTLtDmACTB8ObsuhIvgfzylsmte ... so this changes all the time

[patrickhlauke]

and manually changing the hidden value and trying to submit the form with an invalid token brings back a 403 forbidden

[patrickhlauke]

I'd suggest leaving the FAE one as is, simply pointing to their front-end page. it's only a minor inconvenience having to actually copy/paste the url into their form. Or, to be blunt, it wouldn't be a big loss if FAE was removed.

[stevefaulkner]

Or, to be blunt, it wouldn't be a big loss if FAE was removed.

it probably makes sense to do a major cull of the toolbar features for future maintenance purpose, be good to figure out what is useful and what not.

[matatk]

Funny thing is, I don't get the 5xx errors when running the ("old") HTML Validator; I wonder why.