accessibility-issues: Difference between revisions
m (Reverted edits by Racc4Tcnam (Talk) to last version by AmeerDawood) |
m (Replace <entry-title> with {{DISPLAYTITLE:}}) |
||
(7 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{DISPLAYTITLE: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. | 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. | ||
== 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 == | ||
===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 54: | 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 60: | 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? | *# 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 67: | 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 72: | Line 53: | ||
== Template == | == Template == | ||
{{issues-format}} | {{issues-format}} | ||
== See Also == | == See Also == |
Latest revision as of 16:20, 18 July 2020
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.
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
- open issue! 2006-11-26 raised by Andy Mabbett
- 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
- Large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [1], [2]. [3], [4], [5]
- open issue! 2006-12-11 raised by Andy Mabbett
- Duplicating link text breaches 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. - Tantek
- Duplicating link text breaches 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.
- open issue! 2008-01-14 raised by Andy Mabbett
- open issue! 2008-02-07 raised by Andy Mabbett
- 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
- 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".
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>