On a mission to make valid XHTML...

This puts the problem in the hands of the modules that are creating tables. It is also a minor bug fix for the table attributes: if not specified, the variable was null instead of an empty array. From now on, people can use my example for checking attributes for tables.

I almost think this should be moved to a function outside of theme_table(). Thoughts? Suggestions?

CommentFileSizeAuthor
theme_table_patch.txt682 bytesTheLibrarian

Comments

dries’s picture

dries commented

AFAIK, XHTML does not require the use of the 'summary'-attribute (though accessibility standards do).

I'm not convinced this is the proper way to enforce the use of a 'summary'-attribute: we don't do so for any other attribute, and validating a page using a validator is a breeze.

TheLibrarian’s picture

TheLibrarian commented

This patch was mainly a push for module developers to fix their code so that they are fully compliant with accessibility standards (yes, yes, I know it's not required in the XHTML specification). It was also meant to demonstrate how people can check attributes. In retrospect, a demo theme would probably be a better place to do this.

killes@www.drop.org’s picture

killes@www.drop.org commented
Component: theme system » module system

I think this patch shouldn't make it into core. You should rather provide patches for modules that need such a summary field.

dries’s picture

dries commented