accessibility-issues-resolved: Difference between revisions
Jump to navigation
Jump to search
(drafted with outstanding resolved issues) |
m (Replace <entry-title> with {{DISPLAYTITLE:}}) |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:accessibility resolved issues}} | |||
== resolved issues == | == resolved issues == | ||
Accessibility <span id="Resolved_Issues">issues that are resolved but may have outstanding [[to-do]] items.</span> | Accessibility <span id="Resolved_Issues">issues that are resolved but may have outstanding [[to-do]] items.</span> | ||
Latest revision as of 16:20, 18 July 2020
resolved issues
Accessibility issues that are resolved but may have outstanding to-do items.
As issues are resolved, they will be moved from the accessibility issues list to this section.
As actions are taken according to the resolutions noted in the issues, they are moved to accessibility-issues-closed.
resolved 2006
Resolved issues that were raised in 2006.
- resolved issue 2006-09-20 raised by Andy Mabbett in accessifyforum abbr-design-pattern related issue.
- Use of 'abbr' in microformats
- Resolved: Previously accessibility-harmful uses of the abbr-design-pattern should now use the value-class-pattern. to-do document accordingly on abbr-design-pattern page in a section warning about potentially accessibility-harmful uses and accessible techniques to use instead. - Tantek
- Use of 'abbr' in microformats
resolved 2007
Resolved issues that were raised in 2007.
- resolved issue 2007-04-27 raised by JamesCraig, BruceLawson. abbr-design-pattern related issue.
- Web Standards Project ATF article and discussion about why some instances of the abbr-design-pattern are bad for accessibility.'
- Resolved: Previously accessibility-harmful uses of the abbr-design-pattern should now use the value-class-pattern. to-do document accordingly on abbr-design-pattern
- Web Standards Project ATF article and discussion about why some instances of the abbr-design-pattern are bad for accessibility.'
--BenWard 22:44, 15 May 2009 (UTC)
- resolved issue 2007-04-28 raised by PatrickLauke
- although nominally empty, hyperlink includes still present in tab cycle of major browsers, proving to be a problem for keyboard users (including users of screen readers)
- JAWS 7.0 testing not conclusive to ascertain compatibility in other major screen readers.
- ACCEPTED. to-do: document as a known issue with the include-pattern.
- RESOLVED. to-do: deprecate include-pattern in microformats-2 accordingly in preference for using the
itemrefattribute. - Tantek
resolved 2008
Resolved issues that were raised in 2008.
- resolved issue 2008-05-21 raised by Charles Belov. abbr-design-pattern related issue.
- 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:
- ISO dates are not conceptually friendly to non-technical persons creating a web page manually.
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)
- ISSUE ACCEPTED, ALTERNATE REJECTED.: Previously accessibility-harmful uses of the abbr-design-pattern should now use the value-class-pattern. --BenWard 22:44, 15 May 2009 (UTC)
- to-do document accordingly on abbr-design-pattern.