Manifold Accessibility - Revision history

Dkrahmer at 18:24, 24 January 2025

2025-01-24T18:24:22Z

← Older revision		Revision as of 14:24, 24 January 2025
Line 5:		Line 5:
	[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.		[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.

	In general, we have some reservations around Manifold's accessibility. ~~With~~ the ~~small development staff, they are understandably unable to dedicate resources to continued development compared to PressBooks. The dark theme~~ of ~~the backend does possibly present a barrier~~ to ~~some users~~, ~~and there are focus errors that made navigation frustrating~~. There is ~~also~~ a strong cognitive load issue around understanding the various aspects of the frontend and backend; even with an expert on call, our testers struggled trying to understand and use the site.		In general, we have some reservations around Manifold's accessibility. There are focus errors and UI issues that get in the way of being able to call it generally, functionally, accessible. There is a strong cognitive load issue around understanding the various aspects of the frontend and backend; even with an expert on call, our testers struggled trying to understand and use the site. Annotations are not accessible. The backend is only available in a "night" or dark mode, which may be a barrier to some low vision users, and the focus is non-intuitive depending on the page you are accessing.

			Manifold is built on bringing documents into the program rather than authoring directly in the platform. Due to some issues, we weren’t able to properly test the new authoring options. With the small development staff, they are understandably unable to dedicate resources to continued development compared to PressBooks. Manifold also lacks links to resources on creating accessible books with Manifold.

	== General Information ==		== General Information ==
Line 18:		Line 20:
	=== Keyboard Control ===		=== Keyboard Control ===

	The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands~~; however,~~ Manifold does offer alternatives for drag-and-drop actions (select with spacebar, and use the arrow keys to move). There is also a Select a File alternative when uploading files to the project. If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.		The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands. Manifold does offer alternatives for drag-and-drop actions (select with spacebar, and use the arrow keys to move), but we were unable to get them to work on the Layout tab. There is also a Select a File alternative when uploading files to the project. If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.

	=== Color Contrast ===		=== Color Contrast ===
Line 30:		Line 32:
	=== Focus Errors ===		=== Focus Errors ===

	At times, our testers experienced nonsensical focus errors. For example, after performing a search, tabbing to the results jumped the focus to the middle of the list, rather than the top. Sometimes the skip to main content would jump to the bottom of the page, or there will be secondary or tertiary landmarks that are not included with the Skip To options.		At times, our testers experienced nonsensical focus errors. For example, after performing a search, tabbing to the results jumped the focus to the middle of the list, rather than the top. Sometimes the skip to main content would jump to the bottom of the page, or there will be secondary or tertiary landmarks that are not included with the Skip To options. For example, when entering a Manifold project with a screen reader, you don't even experience the Skip to main content text; it simply throws you down to the bottom of the page.

	=== Annotating a Book ===		=== Annotating a Book ===

	Manifold does not support an accessible alternative to annotating a book. You may be able to access some annotations using VoiceOver. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page].		Manifold does not support an accessible alternative to annotating a book. You may be able to access some annotations using VoiceOver. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page]. The Social Annotation aspects of Manifold are a big draw for use in education, but also risks leaving some disabled students unable to participate.

			=== Cognitive Load ===

			It's not impossible to use the Manifold interface, but it is frustrating a lot of the time. Several times our testers gave up trying to do something, even with having an expert user available to walk us through things (and then walk us through it again). Overall the UI is very visually-based, and the backend doesn't always function the way one expects it to. There are things that can be changed with a locally-hosted instance, but you have to have the development staff available to work on it.

			The experience of moving from page to page (or tab to tab) should be consistent; for example, sometimes you have to navigate over to the main content area, and other times the page will automatically focus into the main content area. At times, the user will get stuck in an editable field with no way to escape except reloading the page. Some pages are navigable by headers, while other pages won't allow it. The Skip to Main Content links are missing from some pages.

			=== Analytics tab (backend) ===

			The Analytics page was the most difficult to use with a screen reader and/or keyboard. The graphical statistics had some confusing language around them. For example, visually there is a graphic of a big 2 with a caption underneath saying "annotations created in 1 month 2 days", but audibly it’s confusing ("annotations level 3 list with two items has details 2 caption annotations created in 1 month 2 days has details 2 caption public"). The highlights and stars fields also make no sense to the screen reader.

			You can't use the keyboard to navigate to the Vistors graph. There was no way that we found to access the Vistors graph with a screen reader. It was pretty much invisible to the screen reader. There was no narration for visitor numbers.

			=== Texts tab (backend) ===

	~~=== Analytics~~ page (~~backend~~) ~~===~~		While there weren't any major barriers in the Texts page, there were some hiccups that were confusing to a screen reader user. The labeling in some areas was unclear or completely different from the displayed text ("Ingest New Text" button reads as "texts.add_text_label", and "Add a new section" is read as "create new category"). This may cause friction between screen reader users and sighted users when trying to support each other or explain what to do.

	The Analytics page was the most difficult to use with a screen reader and/or keyboard. The graphical statistics had some confusing language around them. For example, visually there is a graphic of a big 2 with a caption underneath saying "annotations created in 1 month 2 days", but audibly it’s confusing (~~"annotations level 3 list with two items has details 2 caption annotations created in 1 month 2 days has details 2 caption public"~~).		=== Properties Tab (backend) ===

	~~You can use the keyboard to navigate the Analytics page, but whenever~~ you go into Properties, you are ~~instantly put~~ into ~~the Title form element. This skips the explanatory text~~, ~~and has no audio component to tell~~ you ~~that~~ you are ~~editing the element before you start trying to navigate around~~ (~~pressing H to navigate by headings just types the H into your title~~).		If you click into Properties, you are thrown immediately into an editable field, but you're not told you are there. Manifold should tell users when they've entered an editable field (example: "edit Title").

	~~=== Texts Page (backend) ===~~

Dkrahmer at 17:43, 24 January 2025

2025-01-24T17:43:41Z

← Older revision		Revision as of 13:43, 24 January 2025
Line 36:		Line 36:
	Manifold does not support an accessible alternative to annotating a book. You may be able to access some annotations using VoiceOver. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page].		Manifold does not support an accessible alternative to annotating a book. You may be able to access some annotations using VoiceOver. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page].

	=== Analytics page ===		=== Analytics page (backend) ===

	The Analytics page was the most difficult to use with a screen reader and/or keyboard. The graphical statistics had some confusing language around them. For example, visually there is a graphic of a big 2 with a caption underneath saying "annotations created in 1 month 2 days", but audibly it’s confusing ("annotations level 3 list with two items has details 2 caption annotations created in 1 month 2 days has details 2 caption public").		The Analytics page was the most difficult to use with a screen reader and/or keyboard. The graphical statistics had some confusing language around them. For example, visually there is a graphic of a big 2 with a caption underneath saying "annotations created in 1 month 2 days", but audibly it’s confusing ("annotations level 3 list with two items has details 2 caption annotations created in 1 month 2 days has details 2 caption public").

	You can use the keyboard to navigate the Analytics page, but whenever you go into Properties, you are instantly put into the Title form element. This skips the explanatory text, and has no audio component to tell you that you are editing the element.		You can use the keyboard to navigate the Analytics page, but whenever you go into Properties, you are instantly put into the Title form element. This skips the explanatory text, and has no audio component to tell you that you are editing the element before you start trying to navigate around (pressing H to navigate by headings just types the H into your title).

			=== Texts Page (backend) ===




	* Back to [[Digital Accessibility Group\|main Digital Accessibility Group page]].		* Back to [[Digital Accessibility Group\|main Digital Accessibility Group page]].

Dkrahmer at 17:37, 24 January 2025

2025-01-24T17:37:00Z

← Older revision		Revision as of 13:37, 24 January 2025
Line 5:		Line 5:
	[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.		[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.

	In general, we have some reservations around Manifold's accessibility. With the small development staff, they are understandably unable to dedicate resources to continued development compared to PressBooks. The dark theme of the backend does possibly present a barrier to some users, and there are focus errors that made navigation frustrating.		In general, we have some reservations around Manifold's accessibility. With the small development staff, they are understandably unable to dedicate resources to continued development compared to PressBooks. The dark theme of the backend does possibly present a barrier to some users, and there are focus errors that made navigation frustrating. There is also a strong cognitive load issue around understanding the various aspects of the frontend and backend; even with an expert on call, our testers struggled trying to understand and use the site.

	== General Information ==		== General Information ==
Line 34:		Line 34:
	=== Annotating a Book ===		=== Annotating a Book ===

	Manifold does not support an accessible alternative to annotating a book. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page].		Manifold does not support an accessible alternative to annotating a book. You may be able to access some annotations using VoiceOver. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page].

			=== Analytics page ===

			The Analytics page was the most difficult to use with a screen reader and/or keyboard. The graphical statistics had some confusing language around them. For example, visually there is a graphic of a big 2 with a caption underneath saying "annotations created in 1 month 2 days", but audibly it’s confusing ("annotations level 3 list with two items has details 2 caption annotations created in 1 month 2 days has details 2 caption public").

			You can use the keyboard to navigate the Analytics page, but whenever you go into Properties, you are instantly put into the Title form element. This skips the explanatory text, and has no audio component to tell you that you are editing the element.


	* Back to [[Digital Accessibility Group\|main Digital Accessibility Group page]].		* Back to [[Digital Accessibility Group\|main Digital Accessibility Group page]].

Dkrahmer at 17:22, 24 January 2025

2025-01-24T17:22:39Z

← Older revision		Revision as of 13:22, 24 January 2025
Line 4:		Line 4:

	[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.		[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.

			In general, we have some reservations around Manifold's accessibility. With the small development staff, they are understandably unable to dedicate resources to continued development compared to PressBooks. The dark theme of the backend does possibly present a barrier to some users, and there are focus errors that made navigation frustrating.

	== General Information ==		== General Information ==
Line 16:		Line 18:
	=== Keyboard Control ===		=== Keyboard Control ===

	The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands; however, Manifold does offer alternatives for drag-and-drop actions (select with spacebar, and use the arrow keys to move). If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.		The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands; however, Manifold does offer alternatives for drag-and-drop actions (select with spacebar, and use the arrow keys to move). There is also a Select a File alternative when uploading files to the project. If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.

	=== Color Contrast ===		=== Color Contrast ===
Line 22:		Line 24:
	Looking specifically at the backend/editor mode, we weren't able to find areas that required color discernment for navigation or inadequate color contrast. We did note that the fact the entire backend interface is white text on a black background may be difficult for some users to view. Usually, this is something that the user can switch between (light and dark modes). Not having the flexibility to choose may negatively affect a users experience.		Looking specifically at the backend/editor mode, we weren't able to find areas that required color discernment for navigation or inadequate color contrast. We did note that the fact the entire backend interface is white text on a black background may be difficult for some users to view. Usually, this is something that the user can switch between (light and dark modes). Not having the flexibility to choose may negatively affect a users experience.

	In our testing, the backend was responsive to user-set browser defaults around colors (example: white background and black text by default), though it may affect your ability to easily use the site by sight due to the multi-pane view of the backend~~. For example, the headings have a darker background in default view~~.		In our testing, the backend was responsive to user-set browser defaults around colors (example: white background and black text by default), though it may affect your ability to easily use the site by sight due to the multi-pane view of the backend.

	With some of the books that testers looked at, there were some reports of contrast errors, but these are the responsibility of the people who created those books. The issue around headers having contrast errors was reported prior to our testing, and was fixed long after our testing was completed.		With some of the books that testers looked at, there were some reports of contrast errors, but these are the responsibility of the people who created those books. The issue around level 1 headers having consistent contrast errors was reported prior to our testing, and was fixed long after our testing was completed.

			=== Focus Errors ===

			At times, our testers experienced nonsensical focus errors. For example, after performing a search, tabbing to the results jumped the focus to the middle of the list, rather than the top. Sometimes the skip to main content would jump to the bottom of the page, or there will be secondary or tertiary landmarks that are not included with the Skip To options.

			=== Annotating a Book ===

			Manifold does not support an accessible alternative to annotating a book. There is a full explanation of this issue on [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Manifold's accessibility page].



	* Back to [[Digital Accessibility Group\|main Digital Accessibility Group page]].		* Back to [[Digital Accessibility Group\|main Digital Accessibility Group page]].

Dkrahmer at 17:07, 24 January 2025

2025-01-24T17:07:27Z

← Older revision		Revision as of 13:07, 24 January 2025
Line 10:		Line 10:
	* [https://github.com/ManifoldScholar/manifold/issues?q=is%3Aopen+is%3Aissue+label%3A%22Type%3A+Accessibility%22 Github page for reported accessibility issues]		* [https://github.com/ManifoldScholar/manifold/issues?q=is%3Aopen+is%3Aissue+label%3A%22Type%3A+Accessibility%22 Github page for reported accessibility issues]
	* [https://github.com/ManifoldScholar/manifold/issues Github page for reported general issues]		* [https://github.com/ManifoldScholar/manifold/issues Github page for reported general issues]
			* [https://github.com/ManifoldScholar/manifold/discussions/categories/accessibility Github page for discussion around accessibility issues]

	== Known Accessibility Issues ==		== Known Accessibility Issues ==

Dkrahmer at 17:06, 24 January 2025

2025-01-24T17:06:21Z

← Older revision		Revision as of 13:06, 24 January 2025
Line 9:		Line 9:
	* [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Accessibility page]		* [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Accessibility page]
	* [https://github.com/ManifoldScholar/manifold/issues?q=is%3Aopen+is%3Aissue+label%3A%22Type%3A+Accessibility%22 Github page for reported accessibility issues]		* [https://github.com/ManifoldScholar/manifold/issues?q=is%3Aopen+is%3Aissue+label%3A%22Type%3A+Accessibility%22 Github page for reported accessibility issues]
			* [https://github.com/ManifoldScholar/manifold/issues Github page for reported general issues]

	== Known Accessibility Issues ==		== Known Accessibility Issues ==

Dkrahmer at 17:05, 24 January 2025

2025-01-24T17:05:07Z

← Older revision		Revision as of 13:05, 24 January 2025
Line 3:		Line 3:
	== Accessibility Overview ==		== Accessibility Overview ==

	[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices.		[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices. It should be noted that Manifold is grant funded and open source, so updates and responses to accessibility reports may depend on the availability of the incredibly small developer group.

	== General Information ==		== General Information ==

	* [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Accessibility page]		* [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Accessibility page]
	*		* [https://github.com/ManifoldScholar/manifold/issues?q=is%3Aopen+is%3Aissue+label%3A%22Type%3A+Accessibility%22 Github page for reported accessibility issues]


	== Known Accessibility Issues ==		== Known Accessibility Issues ==
Line 18:		Line 19:
	=== Color Contrast ===		=== Color Contrast ===

	~~While~~ we weren't able to find areas that required color discernment for navigation or inadequate color contrast~~, we~~ did note that the fact the entire backend interface is white text on a black background may be difficult for some users to view. Usually, this is something that the user can switch between (light and dark modes). Not having the flexibility to choose may negatively affect a users experience.		Looking specifically at the backend/editor mode, we weren't able to find areas that required color discernment for navigation or inadequate color contrast. We did note that the fact the entire backend interface is white text on a black background may be difficult for some users to view. Usually, this is something that the user can switch between (light and dark modes). Not having the flexibility to choose may negatively affect a users experience.

			In our testing, the backend was responsive to user-set browser defaults around colors (example: white background and black text by default), though it may affect your ability to easily use the site by sight due to the multi-pane view of the backend. For example, the headings have a darker background in default view.

	~~In our testing~~, ~~the site was responsive to user-set browser defaults around colors (example: white background and black text by default)~~, ~~though it may affect your ability to easily use the site by sight due to~~ the ~~multi-pane view~~ of the ~~backend~~. ~~For example~~, ~~the headings have a darker background in default view~~.		With some of the books that testers looked at, there were some reports of contrast errors, but these are the responsibility of the people who created those books. The issue around headers having contrast errors was reported prior to our testing, and was fixed long after our testing was completed.

Dkrahmer at 16:56, 24 January 2025

2025-01-24T16:56:23Z

← Older revision		Revision as of 12:56, 24 January 2025
Line 14:		Line 14:
	=== Keyboard Control ===		=== Keyboard Control ===

	The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands; however, Manifold does offer alternatives for drag-and-drop actions. If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.		The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands; however, Manifold does offer alternatives for drag-and-drop actions (select with spacebar, and use the arrow keys to move). If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.

			=== Color Contrast ===

			While we weren't able to find areas that required color discernment for navigation or inadequate color contrast, we did note that the fact the entire backend interface is white text on a black background may be difficult for some users to view. Usually, this is something that the user can switch between (light and dark modes). Not having the flexibility to choose may negatively affect a users experience.

			In our testing, the site was responsive to user-set browser defaults around colors (example: white background and black text by default), though it may affect your ability to easily use the site by sight due to the multi-pane view of the backend. For example, the headings have a darker background in default view.

Dkrahmer at 16:24, 24 January 2025

2025-01-24T16:24:32Z

← Older revision		Revision as of 12:24, 24 January 2025
Line 3:		Line 3:
	== Accessibility Overview ==		== Accessibility Overview ==

			[https://manifoldapp.org/ Manifold] is a platform for publishing books online that can be locally installed or hosted through Manifold. For our testing, we used the University of Washington's instance. As with [[PressBooks Accessibility\|PressBooks]], the final accessibility of a published book relies on the author to use accessibility best practices.

	== General Information ==		== General Information ==

			* [https://manifoldscholar.github.io/manifold-docusaurus/docs/accessibility Accessibility page]
			*

	== Known Accessibility Issues ==		== Known Accessibility Issues ==

			=== Keyboard Control ===

			The keyboard shortcuts listed on the Accessibility page are standard keyboard navigation shortcuts. Manifold does not have any action-specific keyboard commands; however, Manifold does offer alternatives for drag-and-drop actions. If you use Manifold to host video (rather than embedding YouTube or Vimeo videos), there is no way to use the keyboard to access that video.

Dkrahmer: Created page with "This page gathers the IT Subcommittee's resources and reviews of the accessibility of Manifold. This page will be updated as new information is available or further reviews are conducted. == Accessibility Overview == == General Information == == Known Accessibility Issues == * Back to main Digital Accessibility Group page."

2025-01-17T19:38:42Z

Created page with "This page gathers the IT Subcommittee's resources and reviews of the accessibility of Manifold. This page will be updated as new information is available or further reviews are conducted. == Accessibility Overview == == General Information == == Known Accessibility Issues == * Back to main Digital Accessibility Group page."

New page

This page gathers the IT Subcommittee's resources and reviews of the accessibility of Manifold. This page will be updated as new information is available or further reviews are conducted.

== Accessibility Overview ==

== General Information ==

== Known Accessibility Issues ==

* Back to [[Digital Accessibility Group|main Digital Accessibility Group page]].