Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It's not hard to produce a visually attractive web site, that is W3C compliant, works on most modern browsers*, and is accessible to a wide range of users. You can even produce a nice site that degrades gracefully on the older less standard compliant browsers too.

    All too often people/companies/governments don't. There are many reasons for this: ignorance; obsession with visual impact; lazyness; legacy site/code; lack of usability testing. It can be expensive to convert large complex sites that have evolved over many years to modern efficient sites, and there can be internal politics that hold back sites, but all too often it's a combination of lazyness and ignorance that hold things back.

    He of the Silly Hat [zeldman.com], has produced a facinating book [zeldman.com], which demonstrates that you can have visual impact, you can have ease of access, you can have good usability, you can make it work on most browsers, and best of all, it uses less bandwidth (=saves money), is easy to code (=saves money) and is easier to maintain (=saves money). Overall standard compliant design is a win, win situation....

    * Browsers based on the most recent versions of Mozilla; khtml; Opera; and to the least extent IE.

    --
    -- "It's not magic, it's work..."
    • I agree :)

      A lot of the stuff I have to access has no visual impact---it is HTML 0.9, but they want to use goofy IE javascript to put it in popups or whatever. Those are useless technology add-ons that just make life harder for the weirdos like me.