Blacklight Plugin

Accessibility

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.2
  • Fix Version/s: 2.1
  • Component/s: None
  • Description:
    Blacklight needs to be at least as accessible as Stanford's VuFind

Activity

Hide
Bess Sadler added a comment - 19/Mar/09 6:40 PM
Does this really refer to the plugin?
Show
Bess Sadler added a comment - 19/Mar/09 6:40 PM Does this really refer to the plugin?
Hide
Jennifer Vine added a comment - 01/May/09 12:18 PM
Changes to HTML to address accessibility and usability issues:

Corrections to technically invalid HTML so all pages will validate via http://validator.w3.org - specifically, unclosed tags and the "row" div that was wrapping the <dt><dd> pairs in the results list.

Rationalized the headings so each page has an <h1>, meaningful sections of the page have <h2>, and there are no skipped levels between headings. (Not all the headings are visible, but they're in the document for screen readers to use.)

Adjusted some of the colours in the stylesheet to pass colour contrast tests (I use the Juicy Studios colour contrast analyser browser addon - http://juicystudio.com/article/colour-contrast-analyser-firefox-extension.php)

Added labels to all <form> elements to pass section 508 tests via http://www.cynthiasays.com.

Made the clickable target area larger for the pagination links.

Grouped the "previous" and "next" links together - uh, because our accessibility guy said to (has to do with both scanning through links in a screen reader and target placement for mobility-impaired users).

Moved the "results per page" control out of the search form, and placed it only on the results page - it's not actually "part of the search" and has been proving distracting to users in that context.
Show
Jennifer Vine added a comment - 01/May/09 12:18 PM Changes to HTML to address accessibility and usability issues: Corrections to technically invalid HTML so all pages will validate via http://validator.w3.org - specifically, unclosed tags and the "row" div that was wrapping the <dt><dd> pairs in the results list. Rationalized the headings so each page has an <h1>, meaningful sections of the page have <h2>, and there are no skipped levels between headings. (Not all the headings are visible, but they're in the document for screen readers to use.) Adjusted some of the colours in the stylesheet to pass colour contrast tests (I use the Juicy Studios colour contrast analyser browser addon - http://juicystudio.com/article/colour-contrast-analyser-firefox-extension.php) Added labels to all <form> elements to pass section 508 tests via http://www.cynthiasays.com. Made the clickable target area larger for the pagination links. Grouped the "previous" and "next" links together - uh, because our accessibility guy said to (has to do with both scanning through links in a screen reader and target placement for mobility-impaired users). Moved the "results per page" control out of the search form, and placed it only on the results page - it's not actually "part of the search" and has been proving distracting to users in that context.

People

Dates

  • Created:
    05/Feb/09 3:13 PM
    Updated:
    01/May/09 12:18 PM
    Resolved:
    01/May/09 12:18 PM