Required
Best practice
The WebAIM Alt Text page is a good reference for when and how to use alt text.
DUE DATES: All required elements must be in place by 1 August 2021. WAVE tools should indicate no errors in either error category on all publicly available pages by 1 August 2021. All best practices elements should be in place by 15 January 2022.
Required
Best practice
Required
Best practice
Best practice
Best practice
Best practice
DUE DATES: All required elements must be in place by 1 August 2021. WAVE tools should indicate no errors in either error category on all publicly available pages by 1 August 2021. All best practices elements should be in place by 15 January 2022.
Guidance is forthcoming. Expect font size and contrast recommendations.
Alt text recommendations will be further clarified but for navigation images, it should indicate where the image will take you if clicked. For example, "Go to X page." Recommendations for other images that "do something" can be viewed under the first bullet in best practice for images (above box).
For LibGuides, content creators should meet Web Content Accessibility Guidelines (WCAG) WCAG 2.1. Within these 2.1 guidelines, there are three different levels: A, AA, and AAA. The expectation is that our LibGuides will adhere to WCAG 2.1 at the AA level at a minimum. However, content creators should aim for AAA compliance when appropriate and achievable.
Newly published or revised pages should undergo a WAVE tool check. To meet AA levels, content creators must address any items that show up in the Errors or Contrast Errors categories (see green arrows below). Alerts (green box) should also be reviewed; alerts may tag excessively long alt-text, small font sizes, redundant links, suspicious link text (link text that doesn't make sense out of context, e.g., Click here or Search here), underlined text that is not linked, etc.
Should PDFs that describe a Prezi or other images (see infographic as example) be avoided? If so, what is best to use to replace?
Do we need to tell people to either hide or display link or database descriptions. Some indicate that "hover" for db/link description is not good.
If you've imported content from another Hunter Library guide and it's flagged by the WAVE tool or you have ascertained that it does not meet accessibility best practices as put forward here, you should contact the content creator to inform them of the need for a fix. Unresolved errors should be reported to the LibGuides administrator after two weeks. Guides that have Hunter Library as the responsible party should be reported directly to the LibGuides administrator.
If you are importing content from external sources, there may not be much you can do. Contact the LibGuides administrator for guidance.
This guide was built and revised by the following library faculty and staff:
Cara Barker - Research and Instruction Librarian
Scottie Kapel - Scholarly Communications Librarian
Grey Jenkins - Front End Web Developer
Joel Marchesoni - Front End Web Developer*
Adam Olsen - Web Services Librarian*
Krista Schmidt - STEM Librarian
*No longer at WCU