Difference between revisions of "Accessibility Guide"

From WeBWorK_wiki
Jump to navigation Jump to search
Line 15: Line 15:
 
** The login page doesn't identify what to do with the User: and Password: input boxes. Should have a <label>?
 
** 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.
 
** 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
+
** 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.
+
*** 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?
+
**** 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.
+
**** Practicing navigating the page using VoiceOver or JAWS gives some idea of what one is up against.
   
   

Revision as of 09:35, 15 February 2011

Accessibility Project

We have received a good deal of advice from the folks at the University of Missouri who do accessibility testing. (Contact through Jason Aubrey User:aubreyja)

  • 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 boxes would be good
    • 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