accessibility

(Difference between revisions)

Jump to: navigation, search
m (Reverted edits by AceltRvars (Talk) to last version by RyanKing)
(Disadvantages: Annotations to include-pattern and abbr-pattern accessibility disadvantages.)
Line 22: Line 22:
===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.
 +
** Previous misuses of the abbreviation pattern should now use the [[value-class-pattern]] instead. The abbreviation pattern remains suitable and correct for human readable expansions.
===anchor-include-pattern===
===anchor-include-pattern===
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.
*As mentioned on [[accessibility-issues]], the anchor-include-pattern is in violation of WCAG1 and WCAG2, and has potentially harmful accessibility side effects due to the missing link text.
 +
** The include pattern now strong advises against using empty anchor elements.
==External testimonials==
==External testimonials==

Revision as of 22:35, 15 May 2009

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

Challenges

See also

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

Views