The key principle, to me, is to fail gracefully. Use all the bells and whistles you like, but make sure your core functionality is accessible to users without all that. Say the low income blind person(1) or the curmudgeonly old-school geek using Lynx. Or the security-conscious user with all client-side scripting disabled.

It's a little more design effort, but it's not that hard. If you can't implement a particular function without the extra stuff, perhaps you need to re-think that feature. ("Do X in one click" is not, for purposes of this argument, a feature. "Do X" is.)

(1) There are screen readers that work with GUIs. They're expensive.

In reply to Re: Re: Re: Re: Re: A problem use CGI.pm by menolly
in thread A problem use CGI.pm by lgjut

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.