accessibility

(Difference between revisions)

Jump to: navigation, search
(Disadvantages)
(Disadvantages: reverting content already on (or linked from) accessibility-issues page)
Line 18: Line 18:
===abbr-design-pattern===
===abbr-design-pattern===
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.
*As mentioned on external sites (see:[[accessibility-issues]]) and on the microformats-discuss list, the abbr-design-pattern (used in [[hcard|hCard]], [[hcalendar|hCalendar]], [[geo|GEO]] and others) is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side-effects of reading machine data to screen reader users rendering human content inaccessible.
-
 
-
<pre>
 
-
we have a party in
 
-
<abbr class="dtstart" title="20070312T1700-06">
 
-
March 12, 2007 at 5 PM
 
-
</abbr>
 
-
</pre>
 
-
 
-
would be read by jaws as
 
-
 
-
<pre>
 
-
we have a party at Twenty million seventy-thousand three-hundred twelve tee seventeen-hundred dash zero six.
 
-
</pre>
 
-
 
-
The [http://www.webstandards.org/2007/04/27/haccessibility/  acessibility task force] from web standarsd.org recommends:
 
-
 
-
<pre>
 
-
<span class="dtstart" title="20070312T1700-06">
 
-
March 12, 2007 at 5 PM, Central Standard Time
 
-
</span>
 
-
</pre>
 
-
 
-
or
 
-
 
-
<pre>
 
-
<span class="dtstart">
 
-
March 12, 2007 at 5 PM, Central Standard Time
 
-
<span class="value" title="20070312T1700-06"></span>
 
-
</span>
 
-
</pre>
 
-
 
-
see more at  [[abbr-design-pattern-issues]] and [http://www.webstandards.org/2007/04/27/haccessibility/]
 
===anchor-include-pattern===
===anchor-include-pattern===

Revision as of 19:05, 8 May 2007

Accessibility

This page documents microformats and accessibility in general, in particular advantages that adopting microformats provide for accessibility, and for documenting techniques for making microformats more accessible.

We should all strive to make our published microformats, parser implementations, and this wiki, accessible to all users, regardless of their physical abilities and needs, within the limits of the time and resources of the microformats community. Readers are advised to follow the W3C's Web Content Accessibility Guidelines 1.0, to at least level 2. Further advice is available on the Accessify Forums.

Contents


Advantages

Some microformats have potential accessibility advantages.

hCard

Disadvantages

Some microformats have potential accessibility disadvantages.

abbr-design-pattern

anchor-include-pattern

External testimonials

See also

accessibility was last modified: Wednesday, December 31st, 1969

Views