accessibility-issues

From Microformats Wiki
accessibility-issues /
Revision as of 00:29, 2 May 2007 by JamesCraig (talk | contribs) (→‎abbr-design-pattern: clarification)
Jump to navigation Jump to 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.

IMPORTANT: Please read the accessibility FAQ before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

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.

Issues

hCalendar

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.

  • open issue! 2007-01-20 raised by Andy Mabbett
    1. Where DTEND is a date, and not a date-time, it is required to be the day after the end of the event, thus: <abbr class="dtend" title="2007-04-30">29 April 2007</abbr>. However, "29 April 2007" is not an abbreviation of 2007-04-30; it is an abbreviation of 2007-04-29. The markup as shown is semantically incorrect and likely to cause problems for users and user-agents which read the title attribute, and not the text value, of the abbr element.

abbr-design-pattern

include-design-pattern

Accessibility of this wiki

  • open issue! 2006-11-26 raised by Andy Mabbett
    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] Andy Mabbett 14:33, 26 Nov 2006 (PST)

Template

Please use this format (copy and paste this to the beginning of the list to add your issues):

  • open issue! YYYY-MM-DD raised by YOURNAME.
    1. Issue 1: Here is the first issue I have.
    2. Issue 2: Here is the second issue I have.

Resolved Issues

Issues that are resolved but may have outstanding To Do items.

  • ...

Closed Issues

Resolved issues that have no further actions to take.

  • 2006-11-26 raised by Andy Mabbett
    1. Using emboldening and italics to differentiate types on, e.g. the cheatsheet pages hCard cheatsheet, is unhelpful to users of assistive technologies, text-only devices, etc. A number, letter or symbol should additionally be used. Andy Mabbett 14:33, 26 Nov 2006 (PST)
      • I think the emboldening is fine as it marks up the required properties. The italics are a bit of a problem but keep it simple at the moment. Additional characters can’t be used as they would break the class="property" template. Colours would be a way but are inaccessible to some users, so there is no real solution to that problem for now. Julian Stahnke 22:55, 26 Nov 2006 (GMT)
        • "I think the emboldening is fine" - how would you understand emboldening in a text-only browser like Lynx, or in an aural browser? Andy Mabbett 15:17, 26 Nov 2006 (PST)
          • Ups, I just assumed that it would use strong and em tags. Yeah, well, let’s think about it. Julian Stahnke 23:22, 26 Nov 2006 (GMT)
      • Of course, one could add that stuff after the class="property" thing. That might look a little cluttered though. I’ll consider that for the next revision/next cheat sheet I do. Julian Stahnke 22:57, 26 Nov 2006 (GMT)
        • All that's needed is:
* class="vcard" (1)
instead of:
* class="vcard"
Andy Mabbett 15:24, 26 Nov 2006 (PST)
      • Now resolved. Thanks to all who helped. Andy Mabbett 10:30, 11 Dec 2006 (PST)

See Also