This comes from a client request for accessibility reasons...

Currently if JS is not enabled, there's no indication to the user that they're missing anything. If a field has been edited using a WYSIWYG editor the markup in the field is going to be fugly (guaranteed), but the user will have no inkling as to why. They're not seeing what they're supposed to because the Javascript is missing. The standard practice in this case is to add a <noscript> tag to the page that displays only when JS is not enabled, telling a user all of the fun they're missing by not having Javascript enabled. :-)

I suppose ideally this text should be configurable (probably per editor, not per-field), and placed immediately before the textarea in question (not after, as it should appear before the field to a non-visual user). A normal JS-using user would never see it, which is as it should be.

Is this a feature request that would be entertained? :-)

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Sure... if it helps. #field_prefix should do it, I guess.

I'm not sure whether anyone is going to enable JS just because of this message though...

Crell’s picture

Crell commented

Probably not, but our client saw it as a way to explain to users why they're seeing lots of confusing HTML instead of simple text. Even if they don't enable JS, at least they know why their life will be miserable. :-)

mgifford’s picture

mgifford
he/him
Primary language English
commented

Screenreaders used to have problems with Javascript, but all modern ones work on the DOM, so it's not really an accessibility barrier any more for any practical purposes.

There are probably still lots of organizations though that need it for policy reasons though. I think it might still be part of Section 508 (written back in 1998).