Revision as of 11:09, 5 August 2009 by Tantek (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)

Jump to: navigation, search

accessibility issues

These are externally raised issues about accessibility with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek

Please add new issues to the top of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.




hCalendar specific accessibility issues. These are separated from the hCalendar issues in general so that they are not lost among other non-accessibility related issues.


Accessibility of this wiki

    1. Large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [1], [2]. [3], [4], [5]
    1. Inappropriate alt text, using file name as default, on images conveying information (e.g. [6]). Can editors specify alt text?
    1. The use of "font-size:smaller" on superscript notes is an accessibility barrier. Superscript is already smaller than the user's default preferred text size, and such links present a too-small target for people with visual disabilities and/ or motor-coordination problems to hit, even if they can read them. The Joe Clarke article cited in support of this change is not applicable; it refers to default font size for a page, and does not excuse making text smaller than that default. Even at default text size, single-character links are often too small for such users to "hit".


Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2

Resolved Issues

Issues that are resolved but may have outstanding to-do items.


abbr-design-pattern related issues. The issues are resolved at a specification level following the completion of the value-class-pattern. It is necessary now that examples across all impact microformat specifications be updated to reflect the new pattern where appropriate.

2008-05-21 raised by Charles Belov

  • ISO dates are not conceptually friendly to non-technical persons creating a web page manually.
    • An alternate encoding which I believe would be accessible would be as follows:
Monday, May 16, 2008, 2:31pm<abbr class="dtstart"
style="display:none" title="2008-05-16T14:31:00-0700"></abbr>

Charles Belov 13:35, 21 May 2008 (PDT)

2007-04-27 raised by JamesCraig, BruceLawson.

--BenWard 22:44, 15 May 2009 (UTC)

2006-09-20 raised by Andy Mabbett in accessifyforum

Closed Issues

Resolved issues that have no further actions to take.

* class="vcard" (1)
instead of:
* class="vcard"
Andy Mabbett 15:24, 26 Nov 2006 (PST)

See Also

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