accessibility issues

(Difference between revisions)

Jump to: navigation, search
(Resolved Issues: Documented resolved abbr issues.)
Current revision (23:41, 26 October 2011) (view source)
(entry-title, auto-toc, closed/resolved a few past issues that have long been resolved, moved to separate pages)
 
(2 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1>accessibility issues</h1>
+
<entry-title>accessibility issues</entry-title>
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.  
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|accessibility FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. -->
+
<!-- (UNCOMMENT WHEN accessibility-faq IS CREATED) '''IMPORTANT''': Please read the [[accessibility-faq|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. — [http://tantek.com/ Tantek]
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. — [http://tantek.com/ Tantek]
Line 9: Line 9:
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.
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.
-
__TOC__
+
== Closed Issues ==
 +
Resolved issues that have no further actions to take.
 +
* See [[accessibility-issues-closed]].
 +
 
 +
== Resolved Issues ==
 +
Resolved issues that have outstanding [[to-do]] items.
 +
* See <span id="abbr-design-pattern">[[accessibility-issues-resolved]]</span>.
== Issues ==
== Issues ==
-
===hCalendar===
 
-
hCalendar specific accessibility issues.  These are separated from the [[hcalendar-issues|hCalendar issues]] in general so that they are not lost among other non-accessibility related issues.
 
-
 
-
* {{OpenIssue}} 2007-01-20 raised by [[User:AndyMabbett|Andy Mabbett]]
 
-
*# ''Where <code>DTEND</code> is a date, and not a date-time, it is required to be the day after the end of the event, thus: <code><nowiki>
 
-
<abbr class="dtend" title="2007-04-30">29 April 2007</abbr></nowiki></code>. 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 <code>abbr</code> element.''
 
-
 
-
*{{OpenIssue}} 2006-12-11 raised by Andy Mabbett
 
-
*# ''The image in [[hcalendar-brainstorming#Photos and other attachments]] has inappropriate alt text, being just the file mname. [[User:AndyMabbett|Andy Mabbett]] 15:23, 6 Mar 2007 (PST)''
 
-
 
-
=== include-design-pattern ===
 
-
*{{OpenIssue}} 2007-04-28 raised by [[User:PatrickLauke|PatrickLauke]]
 
-
*# although nominally empty, [http://microformats.org/wiki/include-pattern-feedback#Hyperlink_Include_-_issues_for_keyboard_users_.28including_Screen_Reader_users.29 hyperlink includes still present in tab cycle of major browsers], proving to be a problem for keyboard users (including users of screen readers)
 
-
*# [http://microformats.org/wiki/include-pattern-feedback#Test_Results:_JAWS_7.0_with_Firefox_1.5.2FWin JAWS 7.0] testing not conclusive to ascertain compatibility in other major screen readers.
 
===Accessibility of this wiki===
===Accessibility of this wiki===
-
 
<div class="vevent">
<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2006-11-26</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span>
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2006-11-26</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span>
<div class="description">
<div class="description">
*# Large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [http://www.intranet.man.ac.uk/accessibility/Disabilities/dyslexia.html], [https://tritonlink.ucsd.edu/portal/site/tritonlink-preview/menuitem.b4448692267a11256ec5e210514b01ca?storyID=20896]. [http://accessites.org/], [http://tlt.psu.edu/suggestions/accessibility/font.html], [http://www.wd4a.co.uk/Guidelines.htm]  
*# Large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [http://www.intranet.man.ac.uk/accessibility/Disabilities/dyslexia.html], [https://tritonlink.ucsd.edu/portal/site/tritonlink-preview/menuitem.b4448692267a11256ec5e210514b01ca?storyID=20896]. [http://accessites.org/], [http://tlt.psu.edu/suggestions/accessibility/font.html], [http://www.wd4a.co.uk/Guidelines.htm]  
 +
*#* ACCEPTED. Awaiting a list of pages that need improving and suggested patterns for improvement so we can recommend alternatives to large blocks of italic text in the future. - [[User:Tantek|Tantek]]
</div>
</div>
</div>
</div>
Line 40: Line 32:
<div class="description">
<div class="description">
*# [http://microformats.org/wiki?title=page-summary-formats&diff=11222&oldid=11214 Duplicating link text] breaches [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-meaningful-links WAI-WCAG 1 guideline 13.1 Clearly identify the target of each link] and is unhelpful to users of assistive technologies and other agents, which provide links in a stand-alone, out-of-context list.
*# [http://microformats.org/wiki?title=page-summary-formats&diff=11222&oldid=11214 Duplicating link text] breaches [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-meaningful-links WAI-WCAG 1 guideline 13.1 Clearly identify the target of each link] and is unhelpful to users of assistive technologies and other agents, which provide links in a stand-alone, out-of-context list.
 +
*#* UNCLEAR. Awaiting documentation of specific pages and tools that demonstrate said problem. - [[User:Tantek|Tantek]]
</div>
</div>
</div>
</div>
Line 46: Line 39:
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-14</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span>
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-14</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span>
<div class="description">
<div class="description">
-
*# Inappropriate alt text, using file name as default, on images conveying information (e.g. [http://microformats.org/wiki?title=hcard-supporting-user-profiles&diff=next&oldid=24589]). Can editors specify alt text?</div>
+
*# Inappropriate alt text, using file name as default, on images conveying information (e.g. [http://microformats.org/wiki?title=hcard-supporting-user-profiles&diff=next&oldid=24589]). Can editors specify alt text?
 +
*#* ACCEPTED. Awaiting suggested fix for MediaWiki installs. - [[User:Tantek|Tantek]]
</div>
</div>
Line 53: Line 47:
<div class="description">
<div class="description">
*# The [http://microformats.org/wiki?title=hcard&diff=0&oldid=25600 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".
*# The [http://microformats.org/wiki?title=hcard&diff=0&oldid=25600 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".
 +
*#* ACCEPTED. Awaiting suggested fix for MediaWiki installs. - [[User:Tantek|Tantek]]
</div>
</div>
</div>
</div>
Line 58: Line 53:
== Template ==
== Template ==
{{issues-format}}
{{issues-format}}
-
 
-
== Resolved Issues ==
 
-
Issues that are resolved but may have outstanding [[to-do]] items.
 
-
 
-
===abbr-design-pattern related issues:
 
-
 
-
These 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====
 
-
<div class='discussion issues'>
 
-
*# 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:
 
-
<pre>Monday, May 16, 2008, 2:31pm&lt;abbr class="dtstart"
 
-
style="display:none" title="2008-05-16T14:31:00-0700"&gt;&lt;/abbr&gt;</pre>
 
-
[[User:CharlesBelov|Charles Belov]] 13:35, 21 May 2008 (PDT)
 
-
** '''Resolved''': Previously accessibility-harmful uses of the [[abbr-design-pattern]] should now use the [[value-class-pattern]]. --[[User:BenWard|BenWard]] 22:44, 15 May 2009 (UTC)
 
-
</div>
 
-
 
-
====2007-04-27 raised by JamesCraig, BruceLawson.====
 
-
<div class='discussion issues'>
 
-
* ''Web Standards Project ATF article and discussion about why some instances of the [http://www.webstandards.org/2007/04/27/haccessibility/ abbr-design-pattern are bad for accessibility].'
 
-
** '''Resolved''': Previously accessibility-harmful uses of the [[abbr-design-pattern]] should now use the [[value-class-pattern]].
 
-
--[[User:BenWard|BenWard]] 22:44, 15 May 2009 (UTC)
 
-
</div>
 
-
 
-
====[http://www.accessifyforum.com/viewtopic.php?t=6167&postdays=0&postorder=asc&start=0 2006-09-20 raised by Andy Mabbett in accessifyforum]====
 
-
<div class='discussion issues'>
 
-
*# ''Use of 'abbr' in microformats''
 
-
** '''Resolved''': Previously accessibility-harmful uses of the [[abbr-design-pattern]] should now use the [[value-class-pattern]].
 
-
</div>
 
-
 
-
== Closed Issues ==
 
-
Resolved issues that have no further actions to take.
 
-
 
-
*[http://lists.w3.org/Archives/Public/w3c-wai-ig/2006OctDec/0022.html 2006-10-06 raised by John Foliot in w3c-wai-ig]
 
-
*# ''<blockquote><p>What we don't need (IMHO) is a web where everything is simply a &lt;div&gt; with some extraneous Microformats style association added to it. </p></blockquote>''
 
-
** 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 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2006OctDec/0033.html 2006-10-06 Frances Berriman] answers the issue. [[User:Brian|brian]] 14:02, 13 Aug 2007 (UTC)
 
-
 
-
 
-
*2006-11-26 raised by Andy Mabbett
 
-
*# ''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. [[User:AndyMabbett|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. [[User:JulianStahnke|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? [[User:AndyMabbett|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. [[User:JulianStahnke|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. [[User:JulianStahnke|Julian Stahnke]] 22:57, 26 Nov 2006 (GMT)
 
-
*#**All that's needed is:
 
-
::::<nowiki>* class="vcard" (1)</nowiki>
 
-
::instead of:
 
-
::::<nowiki>* class="vcard"</nowiki>
 
-
:::[[User:AndyMabbett|Andy Mabbett]] 15:24, 26 Nov 2006 (PST)
 
-
*#*'''Now resolved'''. Thanks to all who helped. [[User:AndyMabbett|Andy Mabbett]] 10:30, 11 Dec 2006 (PST)
 
== See Also ==
== See Also ==

Current revision


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.

Contents

Closed Issues

Resolved issues that have no further actions to take.

Resolved Issues

Resolved issues that have outstanding to-do items.

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]
      • ACCEPTED. Awaiting a list of pages that need improving and suggested patterns for improvement so we can recommend alternatives to large blocks of italic text in the future. - Tantek
    1. Inappropriate alt text, using file name as default, on images conveying information (e.g. [6]). Can editors specify alt text?
      • ACCEPTED. Awaiting suggested fix for MediaWiki installs. - Tantek
    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".
      • ACCEPTED. Awaiting suggested fix for MediaWiki installs. - Tantek

Template

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">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</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
</div>
</div>

See Also

accessibility issues was last modified: Wednesday, October 26th, 2011

Views