Ticket #949 (new defect)

Opened 3 months ago

Last modified 3 months ago

Nonsemantic markup in required form fields

Reported by: mdawaffe Assigned to:
Priority: normal Milestone: 1.0-beta & XML-RPC
Component: Administration Version: 1.0-beta (trunk)
Severity: normal Keywords: semantic
Cc:

Description

We currently output <sup class="required">*</sup> for required form inputs. I'm unclear if this is decent semantic markup, and, when it is outputted by template functions, is not very nice to theme authors.

Attached replaces the markup with generated content from CSS.

I'm not that worried about it not working in IE. Theme authors can use the CSS classes to change background colors or whatever if they're interested.

Thoughts?

Attachments

949.diff (3.8 kB) - added by mdawaffe on 08/27/08 03:42:56.

Change History

08/27/08 03:42:56 changed by mdawaffe

  • attachment 949.diff added.

09/09/08 08:16:06 changed by sambauers

Having forms in tables isn't semantically correct to start with :)

I'm not sure about using <sup> as we do, but I don't think CSS generated content is particularly friendly to assisted access devices (I could be *completely* wrong though).

If we are going to change the structure of our forms I think we should be complete about it.