Difference between revisions of "Accessibility"

From Freephile Wiki
Jump to navigation Jump to search
(Created page with "A11Y (an acronym that stands for Accessibility - especially useful if you forget how to spell it). I still remember when Section 508 Guidelines were federally mandated way bac...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
A11Y (an acronym that stands for Accessibility - especially useful if you forget how to spell it). I still remember when Section 508 Guidelines were federally mandated way back in ?? early 2000? I have a promotional copy of Robert Yonaitis' book Understanding Accessibility from 2002 [[ISBN:1-930616-03-1]]
+
A11Y (an acronym that stands for Accessibility - especially useful if you forget how to spell it). I still remember when Section 508 Guidelines were federally mandated way back in 1998<ref>In 1998, Congress amended the Rehabilitation Act of 1973 to require federal agencies to make their electronic and information technology (EIT) accessible to people with disabilities.</ref> On my bookshelf, I have a copy of Robert Yonaitis' book Understanding Accessibility from 2002 [[Special:BookSources/1-930616-03-1|ISBN:1-930616-03-1]]
  
 
See the [https://www.a11yproject.com/checklist/ A11Y checklist] for a generic reference providing a quick implementation of WCAG  
 
See the [https://www.a11yproject.com/checklist/ A11Y checklist] for a generic reference providing a quick implementation of WCAG  
  
==Accessibility in MediaWiki ==
+
==Accessibility in MediaWiki==
  
 
*[https://design.wikimedia.org/style-guide/design-principles_accessibility.html Accessibility as a design principle]
 
*[https://design.wikimedia.org/style-guide/design-principles_accessibility.html Accessibility as a design principle]
Line 19: Line 19:
 
[[mw:Accessibility guide for developers]] describes techniques, guidelines and some tools '''for developers'''.  
 
[[mw:Accessibility guide for developers]] describes techniques, guidelines and some tools '''for developers'''.  
  
== Tools ==
+
==Tools==
* https://addons.mozilla.org/en-US/firefox/addon/wave-accessibility-tool/
+
 
* https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/
+
*https://addons.mozilla.org/en-US/firefox/addon/wave-accessibility-tool/
* https://firefox-source-docs.mozilla.org/devtools-user/accessibility_inspector/
+
*https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/
 +
*https://firefox-source-docs.mozilla.org/devtools-user/accessibility_inspector/
  
 
Guidance boils down to "Open the WAVE extension or your [https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Accessibility Firefox Accessibility Inspector] to confirm WCAG 2.1 level AA compliance".
 
Guidance boils down to "Open the WAVE extension or your [https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Accessibility Firefox Accessibility Inspector] to confirm WCAG 2.1 level AA compliance".
  
 
[[Category:Web Development]]
 
[[Category:Web Development]]

Latest revision as of 22:39, 5 February 2024

A11Y (an acronym that stands for Accessibility - especially useful if you forget how to spell it). I still remember when Section 508 Guidelines were federally mandated way back in 1998[1] On my bookshelf, I have a copy of Robert Yonaitis' book Understanding Accessibility from 2002 ISBN:1-930616-03-1

See the A11Y checklist for a generic reference providing a quick implementation of WCAG

Accessibility in MediaWiki[edit | edit source]

In the Codex Design system, the README states "Web accessibility compliant (Web Content Accessibility Guidelines 2.1 level AA)"

The project sources (docs) at packages/codex-docs/docs/style-guide/accessibility.md gives greater detail on the goals, and accessibility focus of the project.

There is a long-standing tradition of accessibility in WikiMedia projects, expressed in the wikipedia:Wikipedia:Manual_of_Style/Accessibility Wikipedia's Manual of Style (emphasis on Content Accessibility)

mw:Accessibility guide for developers describes techniques, guidelines and some tools for developers.

Tools[edit | edit source]

Guidance boils down to "Open the WAVE extension or your Firefox Accessibility Inspector to confirm WCAG 2.1 level AA compliance".

  1. In 1998, Congress amended the Rehabilitation Act of 1973 to require federal agencies to make their electronic and information technology (EIT) accessible to people with disabilities.