Low Vision - Revision history

Kirabug: Replaced content with "For information about low vision, visit [https://accessibility.perpendicularangel.com/what-is-accessibility/types-of-disabilities/visual-disabilities/low-vision/ Low Visio..."

2021-09-06T03:34:11Z

Replaced content with "For information about low vision, visit [https://accessibility.perpendicularangel.com/what-is-accessibility/types-of-disabilities/visual-disabilities/low-vision/ Low Visio..."

← Older revision		Revision as of 20:34, 5 September 2021
Line 1:		Line 1:
	Low vision describes any number of situations where a person has lost a significant amount of their vision, but not enough to be considered blind. It can be caused by any of a number of factors, each of which presents as a slightly different set of visual challenges. These include:		For information about low vision, visit [https://accessibility.perpendicularangel.com/what-is-accessibility/types-of-disabilities/visual-disabilities/low-vision/ Low Vision] on [[Perpendicular Angel]].

	* albinism
	* brain injuries
	* cataracts
	* diabetic retinopathy
	* eye injuries
	* eye cancer
	* glaucoma
	* hemianopia
	* macular degeneration
	* retinitis pigmentosa
	* retinal detachments
	* various infections

	~~==Design Considerations==~~

	~~People with~~ low vision ~~may rely on the browser's zoom features, or they may use screen magnification software such as [[ZoomText]] or [[MAGic]]~~, which show a small portion of the screen at a time. Low vision users are also often [http://kb.perpendicularangel.com/index.php?title=Category:Vision_issues#Screen_readers screen reader users] so keep those requirements in mind as well.

	~~When designing for users with low vision, we need to:~~

	* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG 1.4.3 Contrast (Minimum)]]
	* Publish all information on web pages (HTML), not PDFs or other inflexible formats
	* Use a combination of color, shapes, and text
	* Follow a linear, logical layout and ensure text flows and is visible when text is magnified to 200%
	* Put buttons and notifications in context.
	* Provide a visible focus state. Ensure that your software passes [[WCAG 2.4.7 Focus Visible]]
	* Provide a clear visual distinction between content (text, images) and controls (buttons, links, etc.)

	~~We need to avoid:~~

	* Disabling pinch-to-zoom
	* Using low color contrasts and small font sizes
	* Burying information in downloads
	* Only using color to convey meaning
	* Spreading content all over a page and forcing a user to scroll horizontally when text is magnified to 200%
	* Separating actions from their context

	~~Sources for list above:~~
	* [https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/ Dos and Don'ts on designing for accessibility] and the accompanying poster on [https://accessibility.blog.gov.uk/wp-content/uploads/sites/52/2016/09/visually-impaired-low-vision.png designing for users with low vision (PNG)] by [[Karwai Pun]] at the [[UK Accessibility in Government Blog]]
	* [[Deque University]] accessibility training

	~~[https://www.invisionapp~~.com~~/blog/mobile-design-visually-impaired/ How to design mobile app experiences for the visually impaired] by [[Ayesha Zafar]] on [[Inside Design]] discusses steps specific to mobile interactions.~~

	~~==Tools==~~

	* [http://www.amd.org/what-is-~~macular-degeneration~~/~~experience~~-~~what~~-~~amd-looks-like~~/ ~~Macular Degeneration] simulator and video~~
	* [https://www.aao.org/eye-~~health~~/~~diseases/glaucoma~~-vision~~-simulator Glaucoma simulator]~~
	* [http:/~~/www.cnib.ca/en/your-eyes/eye-conditions/eye-connect/Pages/EyeSimulator.aspx#diabetic-retinopathy Simulator for Macular Degeneration, Diabetic Retinopathy, Cataracts, and Glaucoma~~]
	* [http://webaim.org/resources/contrastchecker/ WebAIM's Color Contrast Checker] - will tell you if two colors you enter pass accessibility guidelines

	~~===ZoomText examples===~~
	~~Introduction to ZoomText and Screen Magnifiers, with captions.~~
	~~<YouTube>https://www.youtube.com/watch?v=ojtiVj78QPw</YouTube>~~

	~~Leanne Clough illustrates the benefits of ZoomText. Transcript in the comments below [[https://vimeo.com/13757711 the video~~ on ~~Vimeo's site]].~~
	~~<vimeo>https://vimeo.com/13757711</vimeo>~~

	~~==Additional resources==~~

	* [~~http://www2.ca.uky.edu/HES/fcs/FACTSHTS/HF-LRA.151.PDF Responding to Color (PDF)] by the Cooperative Extension Service of the~~ [~~[University of Kentucky~~]].
	* [https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/ Dos and Don'ts on designing for accessibility] and the accompanying poster on [https://accessibility.blog.gov.uk/wp-content/uploads/sites/52/2016/09/visually-impaired-low-vision.png designing for users with low vision (PNG)] by [[Karwai Pun]] at the [[UK Accessibility in Government Blog]]

	[[Category:Vision Disabilities]]		[[Category:Vision Disabilities]]

Kirabug at 07:54, 13 February 2021

2021-02-13T07:54:40Z

← Older revision		Revision as of 00:54, 13 February 2021
Line 41:		Line 41:
	* [[Deque University]] accessibility training		* [[Deque University]] accessibility training

	[https://www.invisionapp.com/blog/mobile-design-visually-impaired/ How to design mobile app experiences for the visually impaired] by [[Ayesha Zafar]] on [[~~Invision~~]] discusses steps specific to mobile interactions.		[https://www.invisionapp.com/blog/mobile-design-visually-impaired/ How to design mobile app experiences for the visually impaired] by [[Ayesha Zafar]] on [[Inside Design]] discusses steps specific to mobile interactions.

	==Tools==		==Tools==

Kirabug at 02:01, 30 July 2020

2020-07-30T02:01:41Z

← Older revision		Revision as of 19:01, 29 July 2020
Line 25:		Line 25:
	* Follow a linear, logical layout and ensure text flows and is visible when text is magnified to 200%		* Follow a linear, logical layout and ensure text flows and is visible when text is magnified to 200%
	* Put buttons and notifications in context.		* Put buttons and notifications in context.
	* Provide a visible focus state. Ensure that your software passes [[WCAG ~~Guideline~~ 2.4.7 Focus Visible]]		* Provide a visible focus state. Ensure that your software passes [[WCAG 2.4.7 Focus Visible]]
	* Provide a clear visual distinction between content (text, images) and controls (buttons, links, etc.)		* Provide a clear visual distinction between content (text, images) and controls (buttons, links, etc.)

Kirabug at 02:00, 30 July 2020

2020-07-30T02:00:26Z

← Older revision		Revision as of 19:00, 29 July 2020
Line 20:		Line 20:
	When designing for users with low vision, we need to:		When designing for users with low vision, we need to:

	* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG ~~Guideline~~ 1.4.3 Contrast (Minimum)]]		* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG 1.4.3 Contrast (Minimum)]]
	* Publish all information on web pages (HTML), not PDFs or other inflexible formats		* Publish all information on web pages (HTML), not PDFs or other inflexible formats
	* Use a combination of color, shapes, and text		* Use a combination of color, shapes, and text

Kirabug at 21:56, 20 July 2020

2020-07-20T21:56:05Z

← Older revision		Revision as of 14:56, 20 July 2020
Line 62:		Line 62:
	* [https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/ Dos and Don'ts on designing for accessibility] and the accompanying poster on [https://accessibility.blog.gov.uk/wp-content/uploads/sites/52/2016/09/visually-impaired-low-vision.png designing for users with low vision (PNG)] by [[Karwai Pun]] at the [[UK Accessibility in Government Blog]]		* [https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/ Dos and Don'ts on designing for accessibility] and the accompanying poster on [https://accessibility.blog.gov.uk/wp-content/uploads/sites/52/2016/09/visually-impaired-low-vision.png designing for users with low vision (PNG)] by [[Karwai Pun]] at the [[UK Accessibility in Government Blog]]

	[[Category:Vision ~~issues~~]]		[[Category:Vision Disabilities]]

Kirabug at 19:17, 20 July 2020

2020-07-20T19:17:17Z

← Older revision		Revision as of 12:17, 20 July 2020
Line 36:		Line 36:
	* Spreading content all over a page and forcing a user to scroll horizontally when text is magnified to 200%		* Spreading content all over a page and forcing a user to scroll horizontally when text is magnified to 200%
	* Separating actions from their context		* Separating actions from their context

			Sources for list above:
			* [https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/ Dos and Don'ts on designing for accessibility] and the accompanying poster on [https://accessibility.blog.gov.uk/wp-content/uploads/sites/52/2016/09/visually-impaired-low-vision.png designing for users with low vision (PNG)] by [[Karwai Pun]] at the [[UK Accessibility in Government Blog]]
			* [[Deque University]] accessibility training

	[https://www.invisionapp.com/blog/mobile-design-visually-impaired/ How to design mobile app experiences for the visually impaired] by [[Ayesha Zafar]] on [[Invision]] discusses steps specific to mobile interactions.		[https://www.invisionapp.com/blog/mobile-design-visually-impaired/ How to design mobile app experiences for the visually impaired] by [[Ayesha Zafar]] on [[Invision]] discusses steps specific to mobile interactions.

Kirabug: /* ZoomText examples */

2020-07-20T19:14:47Z

ZoomText examples

← Older revision		Revision as of 12:14, 20 July 2020
Line 47:		Line 47:

	===ZoomText examples===		===ZoomText examples===
			Introduction to ZoomText and Screen Magnifiers, with captions.
	<YouTube>https://www.youtube.com/watch?v=ojtiVj78QPw</YouTube>		<YouTube>https://www.youtube.com/watch?v=ojtiVj78QPw</YouTube>

			Leanne Clough illustrates the benefits of ZoomText. Transcript in the comments below [[https://vimeo.com/13757711 the video on Vimeo's site]].
	<vimeo>https://vimeo.com/13757711</vimeo>		<vimeo>https://vimeo.com/13757711</vimeo>

Kirabug: /* ZoomText example */

2020-07-20T19:13:42Z

ZoomText example

← Older revision		Revision as of 12:13, 20 July 2020
Line 46:		Line 46:
	* [http://webaim.org/resources/contrastchecker/ WebAIM's Color Contrast Checker] - will tell you if two colors you enter pass accessibility guidelines		* [http://webaim.org/resources/contrastchecker/ WebAIM's Color Contrast Checker] - will tell you if two colors you enter pass accessibility guidelines

	===ZoomText ~~example~~===		===ZoomText examples===
	<YouTube>https://www.youtube.com/watch?v=ojtiVj78QPw</YouTube>		<YouTube>https://www.youtube.com/watch?v=ojtiVj78QPw</YouTube>
			<vimeo>https://vimeo.com/13757711</vimeo>

	==Additional resources==		==Additional resources==

Kirabug: /* Design Considerations */

2020-07-20T19:12:55Z

Design Considerations

← Older revision		Revision as of 12:12, 20 July 2020
Line 21:		Line 21:

	* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG Guideline 1.4.3 Contrast (Minimum)]]		* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG Guideline 1.4.3 Contrast (Minimum)]]
	* Publish all information on web pages (HTML)		* Publish all information on web pages (HTML), not PDFs or other inflexible formats
	* Use a combination of color, shapes, and text		* Use a combination of color, shapes, and text
	* Follow a linear, logical layout and ensure text flows and is visible when text is magnified to 200%		* Follow a linear, logical layout and ensure text flows and is visible when text is magnified to 200%
	* Put buttons and notifications in context.		* Put buttons and notifications in context.
			* Provide a visible focus state. Ensure that your software passes [[WCAG Guideline 2.4.7 Focus Visible]]
			* Provide a clear visual distinction between content (text, images) and controls (buttons, links, etc.)

	We need to avoid:		We need to avoid:

Kirabug: /* Design Considerations */

2020-07-20T18:37:40Z

Design Considerations

← Older revision		Revision as of 11:37, 20 July 2020
Line 20:		Line 20:
	When designing for users with low vision, we need to:		When designing for users with low vision, we need to:

	* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG Guideline 1.4.3 Contrast (Minimum)]		* Use good contrasts and a readable font size. Ensure that your software passes [[WCAG Guideline 1.4.3 Contrast (Minimum)]]
	* Publish all information on web pages (HTML)		* Publish all information on web pages (HTML)
	* Use a combination of color, shapes, and text		* Use a combination of color, shapes, and text