W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2001

Testing Cold Fusion Code [was Aaargh]

From: Leonard R. Kasday <kasday@acm.org>
Date: Tue, 13 Feb 2001 10:34:45 -0500
Message-Id: <4.3.2.7.2.20010213102948.04e2f940@pop3.concentric.net>
To: "Fitzgerald, Jimmie" <Jimmie.Fitzgerald@jbosc.ksc.nasa.gov>, w3c-wai-er-ig@w3.org, w3c-wai-ig@w3.org
Jim,

Do you have any tips on testing cold fusion code for accessibility? I'm 
talking about the source that the server sees, not the pages the user sees 
after processing by the server.

For example, do we just strip out the CF?  Or is there something better?

Len

Jim wrote

It would appear that you were looking at a dynamically created page.
Specifically, a Cold Fusion created page.  There are three very easy ways to
tell when you hit Cold Fusion pages:

1) The file name in the url (if present) will end in .cfm
2) The source code will (probably) contain a lot of blank lines which is
where the actual CF code is.  Since it is processed on the server, it
outputs a blank line for every line of CF code.  This can be turned off in
CF administrator.
3) Any error messages displaying anything in pound signs is CF code.

So, while I don't doubt the source code is bad, a bunch of blank lines is
not a stupid trick to hide source code as you have postulated.

As for the errors, it sounds like they need a little help with their CF
code.
--
Leonard R. Kasday, Ph.D.
Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple 
University
(215) 204-2247 (voice)                 (800) 750-7428 (TTY)
http://astro.temple.edu/~kasday         mailto:kasday@acm.org

Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group
http://www.w3.org/WAI/ER/IG/

The WAVE web page accessibility evaluation assistant: 
http://www.temple.edu/inst_disabilities/piat/wave/
Received on Tuesday, 13 February 2001 10:34:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:53 GMT