assistive-technology-abbr-results

(Difference between revisions)

Jump to: navigation, search
m (Markup Possibilities)
(Test Cases: Finalizing)
Line 1: Line 1:
-
<h1>assistive technology abbr results</h1>
+
<h1>abbr-design-pattern alternatives</h1>
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|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty) and by [[geo|Geo]].
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|hCalendar]] (e.g. dtstart, dtend), often by [[hreview|hReview]] (e.g. dtreviewed, rating) and sometimes by [[hcard|hCard]] (e.g. bday, type subproperty) and by [[geo|Geo]].
Line 7: Line 7:
== Test Cases ==
== Test Cases ==
-
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] is working on a set of extended test cases ([http://cookiecrook.com/test/uf/testcases/ work-in-progress]]) that will cover the following data formats and markup formats. Please add to the list so we can create a comprehensive result set.
+
The [http://www.webstandards.org/action/atf/ WaSP Accessibility Task Force] has developed a set of ([http://cookiecrook.com/test/uf/testcases/ extended test cases]]) that cover the following data formats and markup formats.
===Data Formats===
===Data Formats===
-
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. However, the purpose of these test cases is to find the best solution, whether or not it is currently being used.
 
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 date with punctuation (YYYY-MM-DD)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
* ISO 8601 datetime with punctuation (YYYY-MM-DDTHH:MM:SS)
Line 62: Line 61:
===Screenreader Language Pronunciations===
===Screenreader Language Pronunciations===
-
* English
+
Localization is not the job of Microformats, so multiple human languages (English, Spanish, etc.) is irrelevant.
-
* Spanish (need volunteer native Spanish speaker screen reader user)
+
-
* ?
+
===Verbosity settings===
===Verbosity settings===
Line 83: Line 80:
== Results ==
== Results ==
-
To be determined.
+
<s>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.</s> The purpose of these test cases is to find the best solution, whether or not it is currently being used.
 +
 
 +
Results TBD.
== See Also ==
== See Also ==
* [[accessibility]]
* [[accessibility]]
* [[assistive-technology]]
* [[assistive-technology]]

Revision as of 22:20, 9 September 2007

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 TBD.

See Also

assistive-technology-abbr-results was last modified: Wednesday, December 31st, 1969

Views