accessibility

(Difference between revisions)

Jump to: navigation, search
(Advantages: benefit of CSS, not uF)
Current revision (16:46, 3 September 2010) (view source)
m (Revised advisement from WCAG 1, Priority 2, to WCAG2, Level AA)
 
(6 intermediate revisions not shown.)
Line 3: Line 3:
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.
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 [http://www.w3.org/TR/WCAG10/ W3C's Web Content Accessibility Guidelines 1.0], to at least level 2. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].
+
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 [http://www.w3.org/TR/WCAG20/ W3C's Web Content Accessibility Guidelines 2.0], to at least Level AA. Further advice is available on the [http://www.accessifyforum.com/ Accessify Forums].
__TOC__
__TOC__
Line 14: Line 14:
**Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - [[User:JamesCraig|James Craig]]
**Note: This is not an advantage to Microformats. It is a CSS best practice and can be used with or without hCard. This should probably be moved to a [[css-best-practices|CSS Best Practices]] page. - [[User:JamesCraig|James Craig]]
***It is an advantage ''of'' microformats - [[User:AndyMabbett|Andy Mabbett]]
***It is an advantage ''of'' microformats - [[User:AndyMabbett|Andy Mabbett]]
-
***It is not an advantage of microformats; it is just CSS that can be used on any class, whether or not it happens to be ''tel''. There is no documented AT implementation that recognizes Microformats classes automatically. This is just a benefit of CSS, with or without uF. [[User:JamesCraig|James Craig]]
+
****It is not an advantage of microformats; it is just CSS that can be used on any class, whether or not it happens to be ''tel''. There is no documented AT implementation that recognizes Microformats classes automatically. This is just a benefit of CSS, with or without uF. [[User:JamesCraig|James Craig]]
 +
*****It is '''an advantage of microformats'''; because using "tel" in hCard requites people to mark up telephone numbers semantically, where they otherwise might not. No claim about AT implementations is being made. [[User:AndyMabbett|Andy Mabbett]] 01:04, 28 Jan 2008 (PST)
==Disadvantages==
==Disadvantages==
Line 21: 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==

Current revision

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 2.0, to at least Level AA. 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: Friday, September 3rd, 2010

Views