[
https://issues.apache.org/jira/browse/MYFACES-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559003#action_12559003
]
Simon Kitching commented on MYFACES-1803:
-----------------------------------------
I think we need central utility methods to start and end a script section.
One thing that central method could do is ensure CDATA is used to wrap the
script. And another is this noscript stuff.
However I'm not sure that <noscript> should be output by default. That's a lot
of extra text that many apps will not want, particularly as it doesn't actually
make the app usable for users without javascript.
And outputting a noscript section that does not actually make the app run might
shut some tools up, but it really "lies" about WAI support; I would not like
that to be the default.
Maybe a webapp config option called NOSCRIPT_TEXT could be used to enable
<noscript> output inside script tags; when present the <noscript> is generated
using the provided string as the message?
> <noscript> elements should be rendered for better WAI support
> -------------------------------------------------------------
>
> Key: MYFACES-1803
> URL: https://issues.apache.org/jira/browse/MYFACES-1803
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General
> Affects Versions: 1.1.5, 1.2.0
> Reporter: Manfred Geiler
> Assignee: Manfred Geiler
> Priority: Minor
>
> According to the "Web Accessibility Initiative (WAI)" guidelines
> (http://www.w3.org/WAI/) for every <script> element there should also be a
> <noscript> element.
> Although standard JSF apps won't function without Javascript, it is possibly
> to write accessible apps if the developer provides alternative paths
> (outputLinks instead of commandLinks, etc.) through the application.
> Automated web accessibility check tools signal missing <noscript> elements as
> errors.
> For most <script> elements we render in the JSF core now, it might be
> difficult or even impossible (eg commandLink) to automatically render
> alternative code that would work with scripting disabled. But anyway, we
> should at least render <noscript> elements that tell the user why the app
> does not run in his browser.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
