accessibility: Difference between revisions
m (previous revert was to undo undesired change of heading / scope. please keep issues on the accessibility-issues page.) |
JamesCraig (talk | contribs) (→Disdvantages: adding section) |
||
| Line 8: | Line 8: | ||
==Advantages== | ==Advantages== | ||
Some microformats have potential accessibility advantages. | |||
===hCard=== | ===hCard=== | ||
*<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two". | *<code>tel</code> in [[hcard|hCard]]: use <code>style="speak-numeral:digits"</code>, so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two". | ||
==Disadvantages== | |||
Some microformats have potential accessibility disadvantages. | |||
===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. | |||
===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. | |||
==External testimonials== | ==External testimonials== | ||
Revision as of 00:50, 2 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.
Advantages
Some microformats have potential accessibility advantages.
hCard
telin hCard: usestyle="speak-numeral:digits", so that telephone numbers are read by aural browsers as, for example, "five-five-five one-two-three-four" and not "five-hundred and fifty-five, one-thousand, two-hundred and thirty-two".
Disadvantages
Some microformats have potential accessibility disadvantages.
abbr-design-pattern
- As mentioned on external sites (see:accessibility-issues) and on the microformats-discuss list, the abbr-design-pattern (used in hCard, hCalendar, 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.
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.
External testimonials
- hCard and hCalendar Formats - 2006-08-03 in w3c-wai-ig. e.g.
I think Microformats.org is doing rather well on it's own, and it isn't particularly something that the W3C would or should get involved in until it's settled down. (And then it would just be a ratification kind of thing.)
...
In fact, it is likely to be good for accessibility, as the tools for consuming microformats often require valid code.
See also
- accessibility-issues - note external criticisms on the accesibility issues page
- internationalization
- assistive-technology