Struts Javascript Validator Accessibility Issues??

Discussion in 'Java' started by Dom, Aug 31, 2004.

  1. Dom

    Dom Guest

    Hi,

    does the struts validator use client-side or server-side javascript?

    If it uses client-side validation then will there be accessibility
    issues as outlined by W3C ( http://www.w3.org/TR/WAI-WEBCONTENT/ ).

    Many thanks for any replies!

    Dom
     
    Dom, Aug 31, 2004
    #1
    1. Advertising

  2. Dom

    Sudsy Guest

    Dom wrote:
    > Hi,
    >
    > does the struts validator use client-side or server-side javascript?
    >
    > If it uses client-side validation then will there be accessibility
    > issues as outlined by W3C ( http://www.w3.org/TR/WAI-WEBCONTENT/ ).


    It uses server-side validation with the option for creating JavaScript
    for the client-side. Since you don't control the client, you still need
    to perform validation on the server.
    Accessibility is an entirely different consideration.
     
    Sudsy, Aug 31, 2004
    #2
    1. Advertising

  3. On Tue, 31 Aug 2004 08:31:27 -0400, Sudsy wrote:
    > Dom wrote:

    ...
    >> If it uses client-side validation then will there be accessibility
    >> issues as outlined by W3C ( http://www.w3.org/TR/WAI-WEBCONTENT/ ).

    >
    > It uses server-side validation with the option for creating JavaScript
    > for the client-side. Since you don't control the client, you still need
    > to perform validation on the server.
    > Accessibility is an entirely different consideration.


    I understand the OP's question though.

    Too many JS based apps. *require* JS
    or you do not see the GUI, whereas
    Struts JS validation simply adds a
    layer of DHTML (validation), over a
    completely functional HTML (the form).

    --
    Andrew Thompson
    http://www.PhySci.org/ Open-source software suite
    http://www.PhySci.org/codes/ Web & IT Help
    http://www.1point1C.org/ Science & Technology
     
    Andrew Thompson, Aug 31, 2004
    #3
  4. Dom

    Dom Guest

    Andrew Thompson <> wrote in message news:<3hlaw1ttzlq4$.7jrzsc6ao0n1$>...
    > On Tue, 31 Aug 2004 08:31:27 -0400, Sudsy wrote:
    > > Dom wrote:

    > ..
    > >> If it uses client-side validation then will there be accessibility
    > >> issues as outlined by W3C ( http://www.w3.org/TR/WAI-WEBCONTENT/ ).

    > >
    > > It uses server-side validation with the option for creating JavaScript
    > > for the client-side. Since you don't control the client, you still need
    > > to perform validation on the server.
    > > Accessibility is an entirely different consideration.

    >
    > I understand the OP's question though.
    >
    > Too many JS based apps. *require* JS
    > or you do not see the GUI, whereas
    > Struts JS validation simply adds a
    > layer of DHTML (validation), over a
    > completely functional HTML (the form).



    Great! The fact that its server-side saves me a lot of hassle.

    Currently all my forms extend ValidatorForm. Implementing the validate
    method on my form would have been a pain (but not difficult) to do
    through out all my forms......espcially when I thought I've finished!

    My thinking was that Struts somehow forced its JS (in
    validator-rules.xml) down to the browser and got the browser to
    execute the JS.....which would have caused accessibility
    issues.......which is all WRONG.

    Many thanks for you replies guys!
    Dom
     
    Dom, Sep 1, 2004
    #4
  5. On 1 Sep 2004 06:37:04 -0700, Dom wrote:

    > My thinking was that Struts somehow forced its JS (in
    > validator-rules.xml) down to the browser and got the browser to
    > execute the JS.....


    No. The way it works is more like this,
    when the UA (read browser) sees.. a tring like
    <script type='text/javascript' src='common.js'></script>

    It requests and downloads the file if and when
    it damn well feels like it.

    If it does not understand JS it will
    ignore it and save the bytes.

    > ..which would have caused accessibility
    > issues.......which is all WRONG.


    No. The point is that the JS (that arrives
    or not, and is exectued or not) simply enhances
    the existing form and provides faster form
    validation feedback than is possible with the
    round trip to the server.

    If it is a well designed web-app., even with
    JS, there is no question of accessibility issues.

    --
    Andrew Thompson
    http://www.PhySci.org/ Open-source software suite
    http://www.PhySci.org/codes/ Web & IT Help
    http://www.1point1C.org/ Science & Technology
     
    Andrew Thompson, Sep 1, 2004
    #5
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Replies:
    4
    Views:
    936
    Richter~9.6
    Feb 13, 2007
  2. krishnakant Mane

    python and accessibility issues.

    krishnakant Mane, Nov 16, 2006, in forum: Python
    Replies:
    1
    Views:
    406
    Paddy
    Nov 17, 2006
  3. Dylan Parry
    Replies:
    25
    Views:
    783
    andrew
    Aug 9, 2007
  4. Mike Logan

    Javascript disabled Menu control Accessibility

    Mike Logan, Aug 31, 2006, in forum: ASP .Net Web Controls
    Replies:
    4
    Views:
    144
    Walter Wang [MSFT]
    Sep 4, 2006
  5. Jim Ley

    Javascript Accessibility Techniques

    Jim Ley, Jun 12, 2004, in forum: Javascript
    Replies:
    2
    Views:
    84
    Jim Ley
    Jun 13, 2004
Loading...

Share This Page