accessibility issues closed

This page is for archiving closed accessibility issues about microformats. See:

• accessibility-issues-resolved for resolved issues that have pending actions.
• accessibility-issues for currently open issues.

closed issues

Closed issues that have no further actions to take.

closed 2006

Closed issues that were raised in 2006.

• closed issue 2006-10-06 raised by John Foliot in w3c-wai-ig

  1. What we don't need (IMHO) is a web where everything is simply a <div> with some extraneous Microformats style association added to it.

  • I'm not sure what the issue is here? the use of div elements is NOT an accessibility issue in itself, and microformats always advocate to use the most semantic element in the first place. The following email in that thread 2006-10-06 Frances Berriman answers the issue. brian 14:02, 13 Aug 2007 (UTC)
  • ACCEPTED. microformats only add to existing semantics, and this is documented as such. If this issue is re-raised independently we can make it an FAQ. - Tantek

• closed issue 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. Colors 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)

• 1. • Now resolved. Thanks to all who helped. Andy Mabbett 10:30, 11 Dec 2006 (PST)

• closed issue 2006-12-11 raised by Andy Mabbett - hCalendar specific accessibility issue separated from the hCalendar issues in general so that it is not lost among other non-accessibility related issues.
  1. The image in hcalendar-brainstorming#Photos and other attachments has inappropriate alt text, being just the file name. Andy Mabbett 15:23, 6 Mar 2007 (PST)
     • ACCEPTED RESOLVED. The alt text now summarizes the subject of the photo in a manner that works inline in the text. - Tantek

closed 2007

Closed issues that were raised in 2007.

• closed issue 2007-01-20 raised by Andy Mabbett - hCalendar specific accessibility issue separated from the hCalendar issues in general so that it is not lost among other non-accessibility related issues.
  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.
     • ACCEPTED as the dtend-issue. This disparity has been shown to cause authoring errors over the years, so much so that it a separate issue was raised and discussed with various options for resolution.
     • RESOLVED the dtend property has been errata'd (~2009-2010) to treat whole dates as inclusive as this is more reflective of existing authored/published content. - Tantek

see also

• accessibility-issues
• accessibility-issues-resolved