Difference between revisions of "Accessibility Guide"

From WeBWorK_wiki
Jump to navigation Jump to search
Line 1: Line 1:
−
= Accessibility Project =
  
  +
  +
=== Status of the WeBWorK Accessibility Project ===
  +
  +
Thanks to the help of the [http://actcenter.missouri.edu/ Adaptive Computing Technology Center (ACT)] at the University of Missouri, we have access to the [http://www.hisoftware.com/ HiSoftware Compliance Sheriff] scanning software, and have begun using this software to assess the extent to which WeBWorK meets both Section 508 accessibility regulations, and also more broad recommendations for enhancing the usability of WeBWorK for users accessing the application with assistive technology. This began with an initial consultation with the ACT on February 11, 2011, and our notes from that meeting are below. We have followed up by performing additional, deeper accessibility scans on WeBWorK, and enabled support for screen readers in all mathematics displayed in WeBWorK via the MathJax display mode. To summarize, currently,
  +
  +
* WeBWorK is not fully Section 508 compliant, but just barely. We plan to bring WeBWorK into full Section 508 compliance during Summer 2011.
  +
* The core content of WeBWorK, the mathematics, can be made fully accessible to screen readers by enabling the MathJax display mode.
  +
  +
Instructions for using screen readers in WeBWorK with MathJax are given below, as well as our notes from the initial Feb. 11 consultation with the ACT.
  +
  +
=== How you can help ===
  +
  +
This is a high priority project for WeBWorK, and we would welcome help! We are looking for
  +
* people who have expertise in this area and can offer advice or programming skills,
  +
* people who use or are familiar with using assistive devices on the web and can report to us on the experience of using those tools with WeBWorK,
  +
* people who have access to additional scanning tools,
  +
* people who are just interested in moving this project forward!
  +
  +
Interested parties can contact us at webwork@maa.org.
  +
  +
=== Enabling accessible mathematics with MathJax ===
  +
  +
=== Report ===
   
 
We have received excellent advice from the folks at the University of Missouri who do accessibility testing. (Contact through Jason Aubrey [[User:aubreyja]]) They are willing to continue consultation/collaboration.
  
We have received excellent advice from the folks at the University of Missouri who do accessibility testing. (Contact through Jason Aubrey [[User:aubreyja]]) They are willing to continue consultation/collaboration.

Revision as of 12:02, 3 May 2011

Status of the WeBWorK Accessibility Project

Thanks to the help of the Adaptive Computing Technology Center (ACT) at the University of Missouri, we have access to the HiSoftware Compliance Sheriff scanning software, and have begun using this software to assess the extent to which WeBWorK meets both Section 508 accessibility regulations, and also more broad recommendations for enhancing the usability of WeBWorK for users accessing the application with assistive technology. This began with an initial consultation with the ACT on February 11, 2011, and our notes from that meeting are below. We have followed up by performing additional, deeper accessibility scans on WeBWorK, and enabled support for screen readers in all mathematics displayed in WeBWorK via the MathJax display mode. To summarize, currently,

  • WeBWorK is not fully Section 508 compliant, but just barely. We plan to bring WeBWorK into full Section 508 compliance during Summer 2011.
  • The core content of WeBWorK, the mathematics, can be made fully accessible to screen readers by enabling the MathJax display mode.

Instructions for using screen readers in WeBWorK with MathJax are given below, as well as our notes from the initial Feb. 11 consultation with the ACT.

How you can help

This is a high priority project for WeBWorK, and we would welcome help! We are looking for

  • people who have expertise in this area and can offer advice or programming skills,
  • people who use or are familiar with using assistive devices on the web and can report to us on the experience of using those tools with WeBWorK,
  • people who have access to additional scanning tools,
  • people who are just interested in moving this project forward!

Interested parties can contact us at webwork@maa.org.

Enabling accessible mathematics with MathJax

Report

We have received excellent advice from the folks at the University of Missouri who do accessibility testing. (Contact through Jason Aubrey User:aubreyja) They are willing to continue consultation/collaboration.

  • One can make significant progress quickly in meeting 508 requirements, but really improving usability is a sizable project. Student manpower would be helpful.
  • Establishing a good protocol for AltText in images would be a good start
  • Implementing <label> tags for attaching labels to input entities would be useful.
    • It's somewhat preferable to adding label attributes to HTML entities.
  • One would think that the equations and problems would be the chief barrier, but in fact there are substantial (and perhaps more important) barriers on the first pages. For example:
    • The front page which lists the courses
      • The every underscore is "pronounced" by the JAWS reader -- this makes many course names difficult to recognize.
      • The bullets are read (and they are not really necessary) -- there is some means to suppress this?
        • Fix?: Replace all underscores with spaces when printing to HTML pages. (John Jones has already done this in some locations.)
      • The masthead and links in the picture have too much prominence. The "not logged in" logo in the upper right hand corner is confusing (it is read before the login input)
    • The login page doesn't identify what to do with the User: and Password: input boxes. Should have a <label>?
    • The Course home page has "Sel." for select -- what does that mean? The download Hardcopy button comes after the selection of radio buttons -- so no clue why one would select anything until one "scans" down to there.
    • In general the Login, Course home pages were written using HTML for styling
      • This should be replaced by using HTML for hierarchical organization and CSS for styling.
        • For example the top "Main page" is an H3 because that gives the right size -- but it should be H1?
        • Practicing navigating the page using VoiceOver or JAWS gives some idea of what one is up against.







Web Accessibility Tools and Resources

Introduction to Web Accessibility

Laws, Standards and Guidelines

Free Online Web Accessibility Checkers

Firefox Add-ons

Colorblind Checkers

Manual Web Accessibility Testing Guides

Webinars/Online Trainings

Mobile Devices

WebAIM Articles

More tools

Retrieved from "https://webwork.maa.org/mediawiki_new/index.php?title=Accessibility_Guide&oldid=9710"