hi

i don't like to have more suxxx discussions with module maintainers about - if a module must create valid HTML or not. i need a reference now. i think everything must validate with tidy and W3C.

Why does for e.g. table not force a summary attibute? I thought Drupal does only produce valid XHTML and is using XHTML 1.0 Transition or higher. I was told drupal core does not create valid code (i don't know where this come from). I think it is on the maintainers to add the attribute "summary" with a helpfull value if they create a table in HTML, but if they don't do - is this a bug or not?

What is the position of the drupal core maintainers about valid HTML code for e.g. in tables that helps handicaped people with screenreaders?

Regards
Marc

Comments

magico’s picture

Version: 4.7.3 » 6.x-dev
Category: bug » feature

i think everything must validate with tidy and W3C

Agree.

Why does for e.g. table not force a summary attibute?

Because it is optional according to http://www.w3.org/TR/html4/struct/tables.html#adef-summary

I thought Drupal does only produce valid XHTML and is using XHTML 1.0 Transition or higher.

Yes, Drupal uses XHTML 1.0 Transitional and it does not fully validate (www.drupal.org) as stated within the HTML. Anyway I successfully developed themes that are fully validated under the XHTML 1.0 Strict. OTOH, the new Garland theme is XHTML 1.0 Strict and fully validates.

I was told drupal core does not create valid code

It does.

"summary" with a helpfull value if they create a table in HTML

Yes it would, and there are more issues in the queue to make a more accessibility aware Drupal.

Note to myself: I wish a fully http://www.w3.org/WAI/ and http://www.w3.org/TR/WAI-WEBCONTENT/ Drupal 6.0

pasqualle’s picture

Version: 6.x-dev » 7.x-dev
Category: feature » bug
mgifford’s picture

Issue tags: +Accessibility

So now we're looking at Drupal 7 & WCAG 2.0, see http://www.w3.org/TR/WCAG20-TECHS/H73.html

We are now pretty much table free within Drupal core though. Not sure though what mechanisms within core affect summaries within tables though.

Might be good to raise this point here - http://groups.drupal.org/accessibility

Drupal Core 6 & 7 Validate xHTML Strict throughout I think. We're working on raising the bar too.

Everett Zufelt’s picture

Looking at this issue I'm not sure that I am clear on the requested deliverable. If there is a table within Drupal that would benefit from the optional summary attribute then perhaps an issue should be filed against that module / theme.

As far as I can tell this issue can be closed.

Everett Zufelt’s picture

Status: Active » Closed (won't fix)

Setting status to won't fix. The table summary attribute is optional in xhtml and wcag 2.0. If there is a particular table in Drupal which would benefit from the summary attribute an issue should be filed against that module / theme.