canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
The table element has a long explanation about how to explain the structure of
The example isn't the best, because we should be using more meaningful
examples, where the explanation would be more beneficial. However, this would
require a larger table, and more space.
A better approach would be to remove this section, entirely. This section
should be included in an HTML5 Primer.
What the section should have is a demonstration of the structure of one table,
with explanation of each element in the table, and hopefully demonstrating by
what is meant by a data table -- not a table for illustration purposes, or a
table for layout.
More text will not make tables any clearer, or ensure people use the element in
the proper way. What's needed is a good, clean, succinct example, with a clear
explanation of each element of the table, including the summary attribute.
A good explanation of how to use summary properly would do wonders for the
table's accessibility. A meandering description of how people can use anything
_but_ summary, is only going to cause conflict with previous versions of the
markup, with existing screenreader implementations, and runs counter to the
expressed interest and wishes of every accessibility person on the HTML WG team
-- and beyond.
Add notes (no markup allowed, URIs get automatically hyperlinked):
[rubys]: same situation for this issue