assistive-technology-abbr-results

(Difference between revisions)

Jump to: navigation, search
(Valid HTML4: span with data prefix)
Current revision (18:28, 4 June 2009) (view source)
m (abbr-design-pattern-alternatives moved to assistive-technology-abbr-results over redirect: better reflects the purpose and function of the page)
 
(2 intermediate revisions not shown.)
Line 42: Line 42:
* SPAN element with title attribute (with or without [[title-trigger]] as it behaves no differently in any known screen reader).
* SPAN element with title attribute (with or without [[title-trigger]] as it behaves no differently in any known screen reader).
* SPAN element with "data " (or similar) prefix, as above.
* SPAN element with "data " (or similar) prefix, as above.
 +
** Proposed in [http://microformats.org/discuss/mail/microformats-discuss/2007-December/011173.html microformats-discuss/2007-December/011173.html]
 +
** Has advantage of allowing plain-language title also; see [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011583.html microformats-discuss/2008-February/011583.html]
* [[dfn-design-pattern|DFN element with title attribute.]]
* [[dfn-design-pattern|DFN element with title attribute.]]
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
* Non-linked anchor element with title attribute. (<code><nowiki><a class="dtstart" title="20070713">13th</a></nowiki></code>)
Line 49: Line 51:
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Empty INS element with DATETIME attr (<code><nowiki><span class="dtstart">13th<ins datetime="20070713"></ins></span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
* Rarely used event handler. e.g. (<code><nowiki><span class="dtstart" onchange="void(20070713)">13th</span></nowiki></code>)
-
* Hidden INPUT element (undesirable as it requires FORM)
+
* Hidden INPUT element  
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)
* Empty ABBR element (<code><nowiki><span class="dtstart">13th<abbr title="20070713"></abbr></span></nowiki></code>)

Current revision

abbr-design-pattern alternatives

This page is for document the precise results of using assistive-technology with real world examples in the wild of the abbr design pattern, as nearly always used by hCalendar (e.g. dtstart, dtend), often by hReview (e.g. dtreviewed, rating) and sometimes by hCard (e.g. bday, type subproperty) and by Geo.

Contents


Each assistive-technology listed here should link to a precise description of the tool/service on the assistive-technology page, including version number, when published, etc. Each test result listed for each assistive technology should link to the example that was tested.

Test Cases

The WaSP Accessibility Task Force has developed a set of (extended test cases]) that cover the following data formats and markup formats.

Data Formats

Rejected Data formats

Dates without punctuation as they have proved unusable. Proof is premise for [hAccessibility] article on the Web Standards Project Buzz blog. Window Eyes and JAWS read un-punctuated dates as single number. [JAWS 8 on IE7 citation (MP3 Audio)] of "twenty million seventy-thousand three-hundred twelve" is reason enough for rejection.

Markup Possibilities

Valid HTML4

Invalid HTML4

Markup possibilities that are invalid in HTML4/XHTML1 are noted here to be clear that they were considered and rejected. Since microformats build on posh, any technique that is invalid semantic (X)HTML is unacceptable for a microformats solution. There is no need to bother testing these.

Markup Rejections

Screenreader Language Pronunciations

Localization is not the job of Microformats, so multiple human languages (English, Spanish, etc.) is irrelevant.

Verbosity settings

Screenreaders

Results

Please provide hyperlinks to examples in the wild for each case that is to be tested. Test cases with example in the wild URLs merit more testing than those without. The purpose of these test cases is to find the best solution, whether or not it is currently being used.

Results to be determined.

See Also

assistive-technology-abbr-results was last modified: Thursday, June 4th, 2009

Views