Items no longer have to be W3C validated?

wpCanyonThemes said
@Ivor can you confirm what @wizylabs said? Do themes have to be W3C valid?

Themes and templates have to follow W3C ’s standards, there’s some exception thought.

Unacceptable

• Duplicated ID’s
• Typos in tags
• Tags not closed
• Improperly nesting tags
• Capitalizing tags
• Not encoding special characters (& timthumb for example)
• Missing alt tag in images
• Head content must be within the head
• Improper use of form tags

Acceptable

• Video embeding
• Some jQuery plugins can create validation errors

Also dont forget that TinyMCE in wordpress, sometimes does not close p tags! which is not valid

That covers like 50% of the themes

@landon – There isn’t a p attribute, but that’s what it says

wpCanyonThemes said
Not encoding special characters (& timthumb for example)

That covers like 50% of the themes

@landon – There isn’t a p attribute, but that’s what it says

We don’t reject for that single reason in a quick note I’ll tell the author to fix it, is not a big deal.

Ivor said

wpCanyonThemes said
Not encoding special characters (& timthumb for example)

That covers like 50% of the themes

@landon – There isn’t a p attribute, but that’s what it says

We don’t reject for that single reason in a quick note I’ll tell the author to fix it, is not a big deal.

Notified him to fix it, didn’t want to tell you which theme, thought you might delete the item

landonw said
I think he meant element – I don’t believe there is a p attribute.

Same here but that is what it said.

document type does not allow element “input” here; missing one of “p”, “h1”, “h2”, “h3”, “h4”, “h5”, “h6”, “div”, “pre”, “address”, “fieldset”, “ins”, “del” start-tag

This fired in a simple form tag with a correct input tag.

Just wrap the input with a block element if you don’t want to use fieldset

wpCanyonThemes said
Just wrap the input with a block element if you don’t want to use fieldset

Done

Validates now?