title-trigger: Difference between revisions
Jump to navigation
Jump to search
AndyMabbett (talk | contribs) mNo edit summary |
AndyMabbett (talk | contribs) m (fmt) |
||
| Line 9: | Line 9: | ||
==Proposal== | ==Proposal== | ||
Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of that element's <code>title</code> attribute. | Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of that element's <code>title</code> attribute. e.g. | ||
<pre> | |||
<nowiki> | |||
<span | |||
class="dtstart ufusetitle" | |||
title="2007-08-16" | |||
> | |||
16th August this year | |||
</span> | |||
</nowiki> | |||
</pre> | |||
===Conversion=== | ===Conversion=== | ||
Revision as of 23:45, 16 August 2007
Title trigger
An alternative to the abbr-design-pattern, to address that pattern's accessibility issues.
Contributors
- Author: Andy Mabbett
- Original idea: Patrick Lauke
Proposal
Use a class name; say "ufusetitle" (for "microformat, use title") or something equally unlikely to otherwise occur in the wild, on any element, to trigger the use of that element's title attribute. e.g.
<span
class="dtstart ufusetitle"
title="2007-08-16"
>
16th August this year
</span>
Conversion
All existing and new microformats should use this pattern; abbr-design-pattern should be deprecated, but parsers should still be required to recognise it on legacy pages (perhaps for a period of, say, three years)
Class names
Other potential class names include:
- hsource
- hvalue
- uftitletrigger
- ...
Advantages
- Simple
- Works on any element
- Usable on CMSs (e.g. MediaWiki) which do not allow use of
abbr - Easy to learn
- Ease of authoring
- Easy for parsers to adapt
Disadvantages
- ???