title-trigger: Difference between revisions
Jump to navigation
Jump to search
AndyMabbett (talk | contribs) m (/) |
AndyMabbett (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
=Title trigger= | =Title trigger= | ||
An alternative to the [[abbr-design-pattern]], to address that pattern's [[accessibility-issues#abbr-design-pattern|accessibility issues]]. | |||
==Contributors== | ==Contributors== | ||
| Line 6: | Line 8: | ||
==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 the <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 the <code>title</code> attribute. | ||
Revision as of 23:27, 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 the 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)
Advantages
- Works on any element
- Usable on CMSs (e.g. MediaWiki) which do not allow use of
abbr - Easy for parsers to adapt
Disadvantages
- ???