Accessibility Auditing Shortlist - Revision history

Dkrahmer: /* Assistive Technology User Testing */

2026-05-12T13:27:50Z

Assistive Technology User Testing

← Older revision		Revision as of 09:27, 12 May 2026
Line 100:		Line 100:
	## If you're frequently working on accessibility auditing, it's useful to be a member of such groups as Educause ITAccess, Association on Higher Education and Disability (AHEAD), International Association of Accessibility Professionals (IAAP), DLF Digital Accessibility Working Group (DAWG), and other groups to connect with other professionals who routinely work in accessibility.		## If you're frequently working on accessibility auditing, it's useful to be a member of such groups as Educause ITAccess, Association on Higher Education and Disability (AHEAD), International Association of Accessibility Professionals (IAAP), DLF Digital Accessibility Working Group (DAWG), and other groups to connect with other professionals who routinely work in accessibility.

	==Assistive Technology User Testing==		===Assistive Technology User Testing===
	Above all, it’s necessary to engage with disabled users and their specific needs in testing and evaluating software and websites. Direct experience and feedback are the most important aspect of accessibility testing, as it is difficult to judge something without a real world test. Disabled users are the experts at using their own Assistive Technologies, and can give practical work-arounds that may be missed by other users (especially when they are new to the AT or software, or are stressed out because something isn’t working).		Above all, it’s necessary to engage with disabled users and their specific needs in testing and evaluating software and websites. Direct experience and feedback are the most important aspect of accessibility testing, as it is difficult to judge something without a real world test. Disabled users are the experts at using their own Assistive Technologies, and can give practical work-arounds that may be missed by other users (especially when they are new to the AT or software, or are stressed out because something isn’t working).

Dkrahmer: /* Introduction */

2026-05-12T13:26:23Z

Introduction

← Older revision		Revision as of 09:26, 12 May 2026
Line 4:		Line 4:
	The shortlist is designed to create a simplified guide for beginners to be able to contribute to assessing software and web technologies for accessibility. The goal is to crowdsource accessibility information about a variety of GLAM (Galleries, Libraries, Archives & Museums) technologies that can be shared widely and freely through the [[Digital Accessibility Group\|DLF Digital Accessibility Working Group Wiki]]. It is meant to be a self-directed learning experience where anyone, anywhere, can help us to evaluate commonly used software and websites.		The shortlist is designed to create a simplified guide for beginners to be able to contribute to assessing software and web technologies for accessibility. The goal is to crowdsource accessibility information about a variety of GLAM (Galleries, Libraries, Archives & Museums) technologies that can be shared widely and freely through the [[Digital Accessibility Group\|DLF Digital Accessibility Working Group Wiki]]. It is meant to be a self-directed learning experience where anyone, anywhere, can help us to evaluate commonly used software and websites.

	If you are participating in the initial review of a technology using the shortlist, you can mark what areas you are planning to test on the [https://docs.google.com/document/d/1YVMgN2BSx1xG7wTqUgOtdpG5xOzCaZsN0PP1vqeGOyE/edit~~#heading=h.ignecjocxmlc~~ Accessibility Assessment Template] for that technology. ([[IT_and_Development#Group_Organizers \|Contact the Group Organizers]] for more information.)		If you are participating in the initial review of a technology using the shortlist, you can mark what areas you are planning to test on the [https://docs.google.com/document/d/1YVMgN2BSx1xG7wTqUgOtdpG5xOzCaZsN0PP1vqeGOyE/edit Accessibility Assessment Template] for that technology. ([[IT_and_Development#Group_Organizers \|Contact the Group Organizers]] for more information.)

	This auditing shortlist focuses on the usability of the software, rather than how it meets certain criteria. It is not based on the [https://www.w3.org/WAI/standards-guidelines/wcag/ WCAG standards], but has many parallels. The larger [[Accessibility Auditing Resources]] page includes links to WCAG testing checklists.		This auditing shortlist focuses on the usability of the software, rather than how it meets certain criteria. It is not based on the [https://www.w3.org/WAI/standards-guidelines/wcag/ WCAG standards], but has many parallels. The larger [[Accessibility Auditing Resources]] page includes links to WCAG testing checklists.

Dkrahmer: /* Next Steps */

2026-05-12T13:25:06Z

Next Steps

← Older revision		Revision as of 09:25, 12 May 2026
Line 80:		Line 80:
	# Perform whatever tests you typically perform while doing an accessibility audit and share your results on the working document, such as using the steps above or an advanced accessibility checker like [https://www.deque.com/axe/ AXE] ([https://www.deque.com/axe/devtools/ browser extension]). Record the results.		# Perform whatever tests you typically perform while doing an accessibility audit and share your results on the working document, such as using the steps above or an advanced accessibility checker like [https://www.deque.com/axe/ AXE] ([https://www.deque.com/axe/devtools/ browser extension]). Record the results.
	# If you have knowledge about VPATs, please share your insights about the VPAT for the service if it exists.		# If you have knowledge about VPATs, please share your insights about the VPAT for the service if it exists.
			## Users with a lot of VPAT experience can often identify places where the software or website technically meets WCAG specifications, but also fails in usability. The VPAT should identity what workflows were tested, so please make note if they did not test a workflow you deem as necessary.
	# Does navigation facilitate ease of use?		# Does navigation facilitate ease of use?
	## Consistent layout and design		## Consistent layout and design
Line 97:		Line 98:
	# How does the website look or perform on a mobile device browser? Test both Android and iOS.		# How does the website look or perform on a mobile device browser? Test both Android and iOS.
	# Are there any complaints, evaluations, or discussions around the software on any AT, IT, or Information professional mailing lists or groups?		# Are there any complaints, evaluations, or discussions around the software on any AT, IT, or Information professional mailing lists or groups?
			## If you're frequently working on accessibility auditing, it's useful to be a member of such groups as Educause ITAccess, Association on Higher Education and Disability (AHEAD), International Association of Accessibility Professionals (IAAP), DLF Digital Accessibility Working Group (DAWG), and other groups to connect with other professionals who routinely work in accessibility.

	==Assistive Technology User Testing==		==Assistive Technology User Testing==

Dkrahmer: /* First Steps */

2026-05-12T13:17:25Z

First Steps

← Older revision		Revision as of 09:17, 12 May 2026
Line 71:		Line 71:
	## Rationale: Providing alternate means of accessing audio content is important for individuals who prefer or have to access audio content, visually.		## Rationale: Providing alternate means of accessing audio content is important for individuals who prefer or have to access audio content, visually.
	# Are there any complaints, posts about accessibility issues, or other general discussion around the accessibility of the software or website online? Record this information.		# Are there any complaints, posts about accessibility issues, or other general discussion around the accessibility of the software or website online? Record this information.
			## Rationale: Searching for reddit, GitHub or forum posts where people have talked about the accessibility of a product can be a quick way to identify issues, or to hear personal opinions on the accessibility or usability of a product by an Assistive Technology user in real life. Not all software has a dedicated forum, while some use their forums as the main way to report accessibility issues.
	# Note if there is information, such as support documentation, that is only conveyed through PDFs (especially non-digitally-native scanned PDFs or visually complex PDFs), or complex images (jpg or png) without robust associated text descriptions/captions.		# Note if there is information, such as support documentation, that is only conveyed through PDFs (especially non-digitally-native scanned PDFs or visually complex PDFs), or complex images (jpg or png) without robust associated text descriptions/captions.
	## Rationale: PDFs may introduce inaccessibility for some users, so having vital guidance and support information in PDF form could indicate potential challenges. Certain users will not have access to the information conveyed in complex images designed to convey information (e.g. screenshots of workflows) if they do not have associated descriptive captions or text.Complex images designed to convey information but without associated descriptive captions or text will mean certain users will not have access to the information conveyed in the images (for example, screenshots of workflows).		## Rationale: PDFs may introduce inaccessibility for some users, so having vital guidance and support information in PDF form could indicate potential challenges. Certain users will not have access to the information conveyed in complex images designed to convey information (e.g. screenshots of workflows) if they do not have associated descriptive captions or text. Complex images designed to convey information but without associated descriptive captions or text will mean certain users will not have access to the information conveyed in the images (for example, screenshots of workflows).

	===Next Steps===		===Next Steps===

Dkrahmer: /* First Steps */

2026-05-12T13:12:04Z

First Steps

← Older revision		Revision as of 09:12, 12 May 2026
Line 65:		Line 65:
	# Are the links on the website accessible?		# Are the links on the website accessible?
	## Are the links a different color from the regular text? Are they underlined?		## Are the links a different color from the regular text? Are they underlined?
	### Rationale: Both of these are visual cues that the text is meant to be a link and/or activated in some way. The different colors of the visited/unvisited link should be of enough contrast that it would pass the color blind test. [https://webaim.org/resources/~~contrastchecker~~/ Use the WebAIM Contrast Checker].		### Rationale: Both of these are visual cues that the text is meant to be a link and/or activated in some way. The different colors of the visited/unvisited link should be of enough contrast that it would pass the color blind test. [https://webaim.org/resources/linkcontrastchecker/ Use the WebAIM Link Contrast Checker].
	## Check the actual text of the link--does it say where it goes, or does it just say something generic like “click here”?		## Check the actual text of the link--does it say where it goes, or does it just say something generic like “click here”?
	### Rationale: Links can be activated by Tabbing and then pressing Enter or Spacebar. When navigating a page looking for the Registration link, for example, if all the links say “click here” or “here”, it makes it harder to find the link a user is looking for, especially when they are using alternate means to access the web.		### Rationale: Links can be activated by Tabbing and then pressing Enter or Spacebar. When navigating a page looking for the Registration link, for example, if all the links say “click here” or “here”, it makes it harder to find the link a user is looking for, especially when they are using alternate means to access the web.

Dkrahmer: /* First Steps */

2026-04-28T18:50:05Z

First Steps

← Older revision		Revision as of 14:50, 28 April 2026
Line 56:		Line 56:
	## Rationale: Drag-and-drop is a very complicated move to make without a mouse, fine motor control, or physical control or steadiness.		## Rationale: Drag-and-drop is a very complicated move to make without a mouse, fine motor control, or physical control or steadiness.
	# Does the website use color alone to denote meaning?		# Does the website use color alone to denote meaning?
	## Use the [~~http~~://~~www.~~rgblind.se/~~url~~ RGBlind color blindness simulator] on the website.		## Use the [https://rgblind.com/color-blind-website-checker RGBlind color blindness simulator] on the website.
	## Does being color blind in some way affect a user’s ability to fully use the site? Is there a difference in color between a visited link and a non-visited link?		## Does being color blind in some way affect a user’s ability to fully use the site? Is there a difference in color between a visited link and a non-visited link?
	### Rationale: Using color alone can affect how users who are color blind use the website, because the meaning denoted in the difference in color may not be noticed by folks who are color blind.		### Rationale: Using color alone can affect how users who are color blind use the website, because the meaning denoted in the difference in color may not be noticed by folks who are color blind.

Dkrahmer: /* Next Steps */

2026-04-28T18:39:31Z

Next Steps

← Older revision		Revision as of 14:39, 28 April 2026
Line 87:		Line 87:
	## Is there a “skip to main content” link? Does it go to the most logical “main content?”		## Is there a “skip to main content” link? Does it go to the most logical “main content?”
	# Do images have useful alt text, depending on the context? Do they use a null alt text (alt=””) for decorative images? Refer to the [https://www.w3.org/WAI/tutorials/images/tips/ W3 Image Tutorial Tips and Tricks] for guidance on constructing alt text.		# Do images have useful alt text, depending on the context? Do they use a null alt text (alt=””) for decorative images? Refer to the [https://www.w3.org/WAI/tutorials/images/tips/ W3 Image Tutorial Tips and Tricks] for guidance on constructing alt text.
	# Does the site properly use [https://accessibility.oit.ncsu.edu/using-aria-landmarks-a-demonstration/ ARIA landmarks]?		# Does the site properly use [https://web.archive.org/web/20250122033410/https://accessibility.oit.ncsu.edu/using-aria-landmarks-a-demonstration/ ARIA landmarks] [Web Archive version of the page]?
	# Test the software/website with a screen reader (NVDA, JAWS, VoiceOver, ChromeVox)		# Test the software/website with a screen reader (NVDA, JAWS, VoiceOver, ChromeVox)
	## For guidance on using a screen reader for accessibility testing, [https://www.youtube.com/watch?v=4FOkLRzf5ks view our March 30, 2026 meeting where D Krahmer demonstrates some NVDA screen reader basics] [YouTube].		## For guidance on using a screen reader for accessibility testing, [https://www.youtube.com/watch?v=4FOkLRzf5ks view our March 30, 2026 meeting where D Krahmer demonstrates some NVDA screen reader basics] [YouTube].

Dkrahmer: /* Next Steps */

2026-04-28T18:32:42Z

Next Steps

← Older revision		Revision as of 14:32, 28 April 2026
Line 89:		Line 89:
	# Does the site properly use [https://accessibility.oit.ncsu.edu/using-aria-landmarks-a-demonstration/ ARIA landmarks]?		# Does the site properly use [https://accessibility.oit.ncsu.edu/using-aria-landmarks-a-demonstration/ ARIA landmarks]?
	# Test the software/website with a screen reader (NVDA, JAWS, VoiceOver, ChromeVox)		# Test the software/website with a screen reader (NVDA, JAWS, VoiceOver, ChromeVox)
			## For guidance on using a screen reader for accessibility testing, [https://www.youtube.com/watch?v=4FOkLRzf5ks view our March 30, 2026 meeting where D Krahmer demonstrates some NVDA screen reader basics] [YouTube].
	## What barriers are encountered?		## What barriers are encountered?
	## Are any pop-ups or form fields invisible to the screen reader? Do any pop-ups or menus not work with a keyboard?		## Are any pop-ups or form fields invisible to the screen reader? Do any pop-ups or menus not work with a keyboard?

Dkrahmer: /* Assistive Technology User Testing */

2026-04-28T18:28:39Z

Assistive Technology User Testing

← Older revision		Revision as of 14:28, 28 April 2026
Line 100:		Line 100:

	If you use a specific type of AT yourself, we ask you to join in and share your experience with the GLAM technologies we are examining. Some of our current DAWG IT/Developers members are screen reader users and keyboard-only users, but we welcome anyone’s feedback.		If you use a specific type of AT yourself, we ask you to join in and share your experience with the GLAM technologies we are examining. Some of our current DAWG IT/Developers members are screen reader users and keyboard-only users, but we welcome anyone’s feedback.

	If you are doing testing at your own organization, it is important to compensate disabled users for their time and expertise. Even if the person is an employee at your organization, if it is not part of their regular duties, they should receive extra compensation.		If you are doing testing at your own organization, it is important to compensate disabled users for their time and expertise. Even if the person is an employee at your organization, if it is not part of their regular duties, they should receive extra compensation.

Dkrahmer at 18:25, 8 December 2025

2025-12-08T18:25:12Z

← Older revision		Revision as of 14:25, 8 December 2025
Line 21:		Line 21:
	==Checklist==		==Checklist==
	Accessibility auditing is both a science and an artform. While it is best to engage with an expert, not all information organizations have access to trained auditors. The DLF DAWG team uses these steps and [https://docs.google.com/document/d/1YVMgN2BSx1xG7wTqUgOtdpG5xOzCaZsN0PP1vqeGOyE/edit#heading=h.ignecjocxmlc the accompanying template] for our website reviews. Please consult the full [[Accessibility Auditing Resources]] list for courses, tools, specifications, and guidelines.		Accessibility auditing is both a science and an artform. While it is best to engage with an expert, not all information organizations have access to trained auditors. The DLF DAWG team uses these steps and [https://docs.google.com/document/d/1YVMgN2BSx1xG7wTqUgOtdpG5xOzCaZsN0PP1vqeGOyE/edit#heading=h.ignecjocxmlc the accompanying template] for our website reviews. Please consult the full [[Accessibility Auditing Resources]] list for courses, tools, specifications, and guidelines.

			The main [[IT and Development]] wiki page contains a full list of software and applications that have been reviewed so far.

	===First Steps===		===First Steps===