0 Replies Latest reply on Dec 10, 2008 10:29 AM by Juan Ignacio Sánchez Lara

    Accesibility (turning scripting, javascript, off)

    Juan Ignacio Sánchez Lara Apprentice

      I'm really worried about accesibility. I have to choose the main technologies at my enterprise, and I was sure Seam was the best for us.

      My problem is that I must follow WCAG 1.0 guidelines, and there's a huge problem:
      6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. (Priority 1)
          For example, ensure that links that trigger scripts work when scripts are turned off or not supported (e.g., do not use javascript: as the link target). If it is not possible to make the page usable without scripts, provide a text equivalent with the NOSCRIPT element, or use a server-side script instead of a client-side script, or provide an alternative accessible page as per checkpoint 11.4. Refer also to guideline 1.

      As far as I know, every JSF button needs javascript to work, among other issues. Is there a way I can do a Seam application and manage to make it work with javascript turned off? Of course I won't be able to use all the fancy stuff of RichFaces, but I want to know if there's a way to offer an accesible alternative.