W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > September 2011

Terminology: critical

From: Samuel Sirois <ssirois@accessibiliteweb.com>
Date: Thu, 15 Sep 2011 11:17:12 -0400
To: public-wai-evaltf@w3.org
Message-id: <1316099832.2467.26.camel@sirois>
Hi Eval TF,

I do believe that we should find a "critical" definition in the
terminology definition.

For me, associating that with "path", "process", "work-flow" or else
doesn't really matters if I can't know what is indeed "critical".

What is critical? I won't pretend I am able to formulate a definition,
but I may suggest what I do believe is critical to start the

I basically see three things as being critical regarding accessibility.

      * Contact page, so that if anything goes wrong, the user is able
        to obtain information on how to communicate with the website's
      * Accessibility page, so that if there is any hints on how to
        improve the experience on the website, the user is able to
        access that information.
      * The main goal of the website as seen by the owners. If the
        owners want to sell items from a boutique, then the items
        catalogue and the payment process should be conform to WCAG 2.0.
        If the owners want to offer the users a place to exchange ideas
        on a specific subject, then whatever the tool used (forum, blog,
        mailing list) should be conform to WCAG 2.0.

I believe it is less critical (and less frustrating) for users if the
"historical page" is not fully conform to WCAG 2.0 if the user can still
complete and use whatever the website has to offer.

When I am sampling for an evaluation, that's what I have in mind when I
think about something "critical".

Is that any close to what others had in mind?


Received on Thursday, 15 September 2011 16:06:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:18 UTC