This document, Accessibility Requirements for People with Low Vision, describes what people with low vision need for electronic content, tools, and technologies to be accessible. It includes an overview of low vision and describes specific user needs. Additional information is available from Accessibility for People with Low Vision.
Status of This Document
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This is First Public Working Draft of Accessibility Requirements for People with Low Vision by the Low Vision Accessibility Task Force (LVTF), a Task Force of the Web Content Accessibility Guidelines Working Group (WCAG WG). It describes what people with low vision need for electronic content, tools, and technologies to be accessible, and provides a foundation for planned future work such as a gap analysis, potential WCAG 2.0 extension, and enhancements to other WCAG 2.0 support materials.
This draft provides the overall framework and approach that the Task Force is planning for this document. Most of the information the Task Force intends to include is in this draft; however, there are several open issues that are not yet included in this draft. It is not yet copy edited or polished. The Task Force plans to publish at least one more Working Draft for public review after the content is finalized, and eventually publish it as a Working Group Note.
The Task Force welcomes any comments, and particularly seeks feedback on the following:
Is the purpose and scope of the document clear?
Does the Overview (section 2) provide sufficient explanation for readers to understand the basics of low vision related to electronic content and tools? Is any of the detail in that section unnecessary and can be left out? Is there information missing that we might want to add (while still keeping the section focused on relevant information)?
For each of the User Needs in section 3, is the issue and user experience clearly yet succinctly explained? Are there any points that need better explanation?
Do you have questions that are not answered in this draft that are within scope? ("Why does xyz make it harder for people with low vision to read?" might be in scope; whereas "Should web pages provide text resizing widgets" is out of scope for this document.)
While this is an incomplete draft and the Task Force is aware of some user needs that are not yet included, we welcome comments on additional user needs to include in the document - either now or after we publish the complete draft for review.
We welcome comments on this draft via e-mail to email@example.com or the GitHub repository. Please create separate GitHub issues or pull requests for each comment, rather than combining multiple comments together. Please submit comments by 14 April 2016.
Publication as a First Public Working Draft does not imply endorsement by the W3C
Membership. This is a draft document and may be updated, replaced or obsoleted by other
documents at any time. It is inappropriate to cite this document as other than work in
About this Draft: There are several open issues that are not yet included in this draft. Some images and image descriptions will be revised. This draft is not yet copy edited or polished.
This document, Accessibility Requirements for People with Low Vision, describes what people with low vision need for electronic content, tools, and technologies to be accessible. It includes an overview of low vision and describes specific user needs. It does not set priorities on issues.
User needs can be met at several levels, including hardware, operating systems, user agents (such as web browsers), extensions, plug-ins, assistive technologies, and content. This document does not specify responsibility for meeting user needs, and it does not set technical requirements.
This document is intended to provide the background for developing guidance on making web content, tools, and technologies accessible to people with low vision.
References provides sources for the information in this document
2. Overview of Low Vision
2.1 Scope of Low Vision
“Low vision” refers to visual impairments other than blindness. Other terms, such as “partially sighted” and “sight impaired”, are used in different contexts. Some governments and organizations such as the World Health Organization (WHO) define categories of low vision based on specific levels of visual acuity and field of vision. Visual acuity is the clarity or sharpness of vision. Field of vision is the area a person can see when their eyes are fixed in one position.
In many contexts, low vision only includes impairments that are not corrected with regular glasses, contact lenses, medicine, or surgery. For example, an inability to focus on objects close to the viewer but that can be overcome with reading glasses is not considered low vision in some disability rights contexts. In these contexts, low vision is often defined as visual impairment that interferes with a person’s ability to perform everyday activities.
In some contexts, such as social program benefits, people are classified as having low vision or being “legally blind”. Many people who are legally blind have some usable vision, and can read some text when it is displayed optimally for them.
In considering user needs, this document uses a broad scope of low vision to include all visual impairments except significant blindness — including impairments from aging, “color blindness”, and impairments that are often categorized as legally blind yet people have sufficient vision to see user interfaces in some situations. This document does not include all issues that are also relevant for people who are totally blind. It does include several issues that overlap with the needs of some people with cognitive disabilities.
In a fact sheet on visual impairment and blindness [WHO-VI] the World Health Organization (WHO) estimates that there are 246 million people worldwide who have low vision and 39 million people are blind, indicating that 86% of the people with visual impairments have low vision.
2.3 Cause and Progression of Low Vision
Most low vision is caused by eye diseases and health conditions such as cataracts, glaucoma, and diabetes. These are more prevalent in older people. Some low vision is from birth defects or injuries.
Low vision encompasses a wide and variable range of issues across people, and even a single individual may experience multiple separate issues. Many eye diseases cause progressively worsening vision, and it is not uncommon for a person’s vision to deteriorate from good vision to blindness over several years. Some causes of low vision can be improved through surgery or medication, and it is not uncommon for someone to have deteriorating vision over several months, and then experience improved vision after treatment.
Starting around age 40, most people have declining vision that is not caused by disease, including decreasing ability to focus on text that is close, decreasing color perception, decreasing contrast sensitivity, and more. Some of this is “correctable” with glasses or more lighting, and some is not. Many people with decreased vision due to aging do not consider themselves as having a disability.
2.4 Visual Impairments
This section briefly introduces five categories of visual impairment that impact web use, not including total blindness:
Visual acuity (clarity)
Field of vision
2.4.1 Visual Acuity (Clarity)
Visual acuity is the clarity or sharpness of vision. It is generally dependent on the functioning of the retina part of the eye and of the interpretation of the brain. Measurement of distance visual acuity is based on a standard of 20/20 (6/6 in metric).
Some low visual acuity can be corrected with glasses, contact lenses, or surgery – and some cannot. Therefore, some people will have blurry vision (low visual acuity) no matter what.
User needs related to visual acuity (clarity) are addressed in the following sections:
3.3 Perceiving - text size, font, style, capitalization, size of all elements
3.4 Spacing for Reading - leading, letter spacing, word spacing, justification, margins and borders, spacing between elements
Many people with low vision have extreme sensitivity to light (called photophobia). Bright light makes it difficult or impossible to see, and causes eye pain and headaches. For some people, the normal brightness of a computer screen with a light background is not readable and painful. They need to change the background to a darker color.
User needs related to light sensitivity are addressed in the following section:
Contrast sensitivity is the ability to distinguish bright and dim areas of images, for example, to discern text on a background. A common accessibility barrier for people with low contrast sensitivity is gray text on a light background.
Contrast is based on brightness. Colors that look very different (for example, red, blue, green) can have similar brightness, and not provide sufficient contrast. Tools are available to determine the contrast ratio between colors.
User needs related to contrast sensitivity are addressed in the following section:
The area from which a person’s eye is able to gather visual information when looking straight ahead is referred to as the field of vision or visual field. People generally have a field of vision of approximately 180 degrees from left to right and 150 degrees up and down, with the sharpest vision in the central 5 degrees and color vision in the central 20 degrees. Some people have a smaller field of vision, which is called field loss.
Types of visual field loss can be grouped as follows:
Central field loss: Vision is reduced or absent in the middle of people’s vision.
Peripheral field loss: People only see in the central portion of their visual field, sometimes called “tunnel vision”.
Other field loss: People have scattered patches of obscured vision, have a ring of field loss, have field loss in the left or right part of their vision, or other field loss.
Simulated examples of visual field loss:
User needs related to field of vision are addressed in the following sections:
2.2 Tracking - rewrap for one direction scrolling, reflow to single column, flexible text areas, line length, justification, hyphenation
Some people cannot see certain colors well or at all, usually because of deficiencies in the cone receptors of their eyes which are responsible for color perception. This is commonly called “color blindness”, even though most people who are color blind can see most colors. It is rare that a person cannot see any color at all. Globally, approximately 1 in 12 men (8%) and 1 in 200 women have color vision deficiencies. [Draft Note: Reference to be added; some listed in References.] Color vision deficiencies are not classified as “low vision” or disabilities in many contexts.
Simulated examples of color blindness:
User needs related to color blindness are addressed in the following section:
Most people with low vision have multiple visual impairments. For example, people with macular degeneration usually develop central field loss (“blind spots”), poor visual acuity, low contrast sensitivity, and high light sensitivity. Other factors — such as inflammation, medication, fatigue, environment, and task — influence a person’s effective vision in a given situation.
Fatigue is a significant issue for many people with low vision, particularly when they read text that is not displayed in an optimum way for their visual situation. Generally, the more a person needs to strain to read, the worse their visual fatigue will become. Some people can read for only a short time and then they need a break.
Environmental factors include:
Clarity of the device, for example, dots-per-inch (dpi)
Brightness of the device
Distance and angle
Movement, for example, reading on a train
Sometimes people have control over environmental factors, for example, they can change the lighting in the room, set the brightness of the device, move to a shaded location, or change the angle of the display. Sometimes people have little or no control over the environment, for example, when using a public kiosk.
[Draft Note: The Task Force plans to change the content of this paragraph.] Tasks may also impact a person’s functional vision. For example, a person may be able to distinguish letters at a given point size on a vision test where they are reading only one letter at a time, but they cannot actually read blocks of text at that same point size. This is the difference between legibility and readability. Legibility is related to perceiving text by distinguishing letters. Readability is related to reading and comprehending textual information. Thus text could be somewhat legible to a person, yet not functionally readable—with effort that user could distinguish one letter from another, but could not effectively read sentences.
Some low vision accessibility issues are directly related to functional vision and some are related to adaptations for visual impairments. For example, when a person with low visual acuity (and full field of vision) uses zoom or magnification, they have some similar issues as people with peripheral field loss — as considerable information may be moved outside of their field of vision as a result of their solution to reduced visual acuity.
3. User Needs
User needs varying widely across people who have low vision, and one user’s needs may conflict with another user’s needs. For example, an older person might need high contrast but that might be unreadable to a person with light sensitivity; a person with good visual acuity (clarity) and tunnel vision might need to make the text size small so they can see more words at a time to read better, whereas most people with low visual acuity need large text.
The Task Force plans to expand this section.
It is not uncommon for one person’s needs to be different from day-to-day or even throughout one day; for example, when they are more fatigued, they might need larger text or a different background color. Task and the amount of information influences user needs. For example, when a person is typing an e-mail, they may be able to have smaller font because they know what is being written and are just skimming for typos; whereas when that same person is reading an e-mail, they need larger font because they do not already know the content.
Thus users need to be able to adjust user interfaces to meet their needs. An individual's optimum display for readability often requires very specific adaptations. For example, a person with high light sensitivity and low contrast sensitivity needs to set background and text colors that are not bright and that provide sufficient contrast for them to discern the text.
The characteristics of text that make it more or less legible and readable are highly inter-related; that is, one characteristic is dependent on other characteristics. For example, a person with low contrast sensitivity might not be able to read small text with a contrast ratio of 5:1, but can read text at that ratio when then text is much larger; similarly, with some fonts a person does not need to increase the letter spacing, but with other fonts they do.
The user needs below are grouped by categories, yet some aspects relate to different categories. This section explains user needs for:
Additional User Needs will be added related to contrast and image accessibility.
Each section briefly explains the issue and the user experience, and then states a specific user need after "User Need - ". User Needs that say “Users can...” indicate that users can change a setting.
3.1 Brightness and Color
Brightness relates to luminance and luminosity. [Draft Note: The Task Force plans to link to additional information on this topic.] This document uses "brightness" for simplicity.
3.1.1 Brightness Overall
Bright light from a screen or other sources prevents some people with low vision (including those with photophobia and with reading disabilities such as dyslexia) from reading and causes pain for some people. Some people turn down the brightness of their screen or use an overlay.
User Need - Brightness:
Users can set the overall brightness of a display.
3.1.2 Text Contrast
As mentioned in the Light Sensitivity section, some people need low brightness, especially for backgrounds. Some people who need low brightness for backgrounds also need low brightness overall and thus need low brightness text.
Other people need high contrast between text and background, including many older people who lose contrast sensitivity from ageing. Some read better with dark text on light background.
For some people, common color combinations or colors from a limited color palette work fine, for example, black text on white background or the inverse with white text on black background. Other people need to select more specific background and text colors. For example, people who need low brightness overall, need to select the specific background and text colors that provide sufficient contrast for them yet not too high brightness. Readable and optimal color combinations differs vastly among individuals and can even vary for one individual depending on conditions such as fatigue and lighting.
User Need - Contrast:
Users can set the background color and the text color from the full color spectrum.
3.1.3 Not Relying on Color
Some people cannot distinguish colors... [Draft Note: The Task Force plans to add additional information here.]
User Need - Color:
Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Tracking is following along lines of text, including getting from the end of one line to the beginning of the next line of text.
This section includes rewrap, reflow, line length, and hyphenation. Tracking is also impacted by leading, justification, and margins and borders, especially when blocks of text are in columns or near other text.
3.2.1 Rewrap for One Direction Scrolling
For many people, with and without disabilities, it is difficult to read when they have to scroll back and forth to read a line of text. When people with low vision increase the text size and the text doesn't “reflow”, they sometimes have to scroll horizontally several screens to read a single line of text. Additionally, the scrollbar and cursor is harder to find for some. Getting from the end of a line of text, scrolling back left, and then finding the beginning of the next line can take considerable attention. This degrades reading flow and comprehension, sometimes significantly enough that effective reading is not possible when horizontal scrolling is required.
User Need - Rewrap:
Blocks of text rewrap so that only one direction of scrolling is needed, e.g., for left-right and right-left scripts (languages), usually vertical scrolling and not horizontal scrolling.
Script direction: Rewrap above and Reflow below are written for left-right and right-left scripts for now for simplicity. We'll edit it to make it generic to apply also vertically to top-to-bottom scripts as appropriate — if we can without complicating it too much, or change it to example only. script vs. language reference says “Languages don't have a direction. Scripts have a writing direction”.
3.2.2 Reflow to Single Column
For many people, with and without disabilities, it is more difficult to read when they have to scroll from the bottom of a column of text to the top of another column. For some people with low vision, with multiple columns, they have to scroll up several screens to get from the bottom of one column to the top of the next. Additionally, the scrollbar and cursor is harder to find for some. Getting from the bottom of a column and finding the top of the next column can take considerable attention. This degrades reading flow and comprehension, sometimes significantly.
User Need - Reflow:
Users can set blocks of text in one continuous block, instead of in multiple columns.
3.2.3 Line Length
For many people, with and without disabilities, it is harder to read very long lines of text than shorter lines. For people with a small field of vision, it can be even more difficult to read long lines of text, and from the end of a line of text, to find the beginning of the next line.
People with good visual acuity yet small field of vision might want to set the text size small and the text area narrow so they can get more characters in their field of vision.
User Need - Line Length:
Users can set the line length for blocks of text. Often the easiest way to do this (for developers, designers, and users) is for users to resize text areas and the text rewraps to change the line length.
For some people it is especially difficult to understand words that are hyphenated, and they need to turn off hyphenation. While primarily an issue for people with cognitive impairments, hyphenation becomes more of an issue when text size is increased, thus it is also related to low vision. Some people with very large text may prefer hyphenation on so that more characters fit on a line of text.
User Need - Hyphenation:
Users can turn hyphenation on or off.
Perceiving includes being able to recognize individual letters based on their characteristics, which is legibility, and non-text information and interface elements.
This section includes text size, font, style, capitalization, and size of all elements. Spacing also impacts how hard it is to perceive letters.
3.3.1 Text Size
Some people need larger text in order to perceive letters. Although increasing size is most common, some people with tunnel vision and good visual acuity may prefer smaller letters so they can see more words at a time.
Text settings don't increase the text in tool-tip text and other pop-up text
Text settings don't increase the text in images
Text settings don't increase the text in maps
User Need - Text Size:
Users can change the text size (font size) of all text, without zooming the entire interface.
Some fonts/typefaces are more readable than others. For example, some people cannot read fonts with sub-pixel rendering.
Note to tool developers: When providing users a list of fonts to choose from, present the font name in the font itself — e.g., Times, Veranda, Courier — so users can tell what each font looks like before choosing it.
User Need - Font:
Users can change the font face (also called font family or typeface) of all text, choosing from a wide range of fonts including serif and sans serif fonts.
For some people, bold text is easier to read. For some people, it is difficult to read blocks of text that is all underlined or italicized.
User Need - Style:
Users can change the text style (underline, italic, bold) of blocks of text.
Text in all capital letters is more difficult to read for most people, with and without disabilities.
User Need - Capitalization:
Users can change the capitalization (all capital letters, small capital letters, sentence style) of blocks of text.
3.3.5 Size of All Elements
Some people need to increase the size of all interface elements in order to perceive information. Although increasing size is most common, some people with tunnel vision and good visual acuity may prefer to decrease the size so they can see more information at a time. For example, users need to:
Zoom to make everything larger.
Increase the width of the text cursor, which is usually done at the operating system level.
Increase the size of the mouse pointer, which is usually done at the operating system level.
User Need - Size:
Users can change the size of all elements.
3.4 Spacing for Reading
Spacing such as space between lines and space between words impacts readability.
This section includes leading, letter spacing, word spacing, justification, margins and borders, and spacing between elements.
Leading is the space between lines in a block of text. It is also called line spacing and line height. Some people need more space between lines to be able to read text. Leading also helps with tracking.
User Need - Leading:
Users can change the leading (line spacing, line height) of blocks of text.
3.4.2 Letter Spacing
Some people need more space between letters to read text.
User Need - Letter Spacing:
Users can change the letter spacing (space between letters/characters) of blocks of text.
3.4.3 Word Spacing
Some people need more space between words to read text.
User Need - Word Spacing:
Users can change the word spacing (space between words) of blocks of text.
Justification or alignment options usually include: left, right, full/both, centered.
Justification impacts readability and tracking. Sometimes full justification makes reading more difficult because extra space between words causes “rivers of white” making it difficult to track along a line of text, or less space between words makes it difficult to distinguish separate words. Some people find it easier to track from the end of one line to the next with full justification, and others prefer left justification (for left-to-right scripts). [Draft Note: The Task Force plans to add a glossary definition for “river” or “river of white”. For now, here's an explanation and example: River (typography).]
User Need - Justification:
Users can change the justification / alignment (left, right, full/both, centered) of blocks of text.
3.4.5 Margins and Borders
If text is close to edges, it is hard for some people to distinguish letters and it negatively impacts readability. Having wide margins around blocks of text helps some people focus on the text and not get distracted by surround text, images, etc. This is especially important for tracking when blocks of text are in columns or near other text.
For people who need very large text, wide margins could make line length too short. For people with tunnel vision, wide margins could make it hard to track text. Therefore, some people might need borders to separate blocks of text instead of, or in addition to, margins.
User Need - Margins and Borders:
Users can change the margins (blank space) and borders — including line color, width, style — around blocks of text.
3.4.6 Spacing Between Elements
Having additional space between unrelated elements helps people group related information. For example, having more space above a heading and less space below it, helps associate the heading with the text below.
[Draft Note: Possible figures to be added: examples equal space before & after headings vs. more space above a heading and less space below it.]
User Need - Spacing Between Elements:
Spacing groups related elements and separates less related elements.
3.5 Identifying Elements
Identifying elements is about distinguishing elements such as headings and lists.
3.5.1 Element-level Customization
Some people change the way certain elements are displayed to make it easier to distinguish types of text, such as headings. If all text is increased proportionally, headings can become very large and bigger than people need to read the main body text. So some people prefer for headings to be smaller and they use styling such as font, color, and indentation to distinguish heading levels.
The Task Force may provide additional image descriptions in this section - including a bulleted list of the user customization in the figures.
User Need - Element-level Customization:
Users can customize text differently for specific elements, such as headings, lists, and paragraph text.
Users can set at least:
Text color and background color
Text style (that is, turn on or off underline, italic, bold)
Borders — including border line color, width, style
3.6 Point of Regard and Proximity
The point of regard is the area that the user is viewing. [Draft Note: More info is available in: UAAG 2 Glossary and IndieUI wiki. The Task Force will probably add a glossary definition to this document.] Proximity is the space between items. In user interface generally, proximity is about using space to group related content and separate unrelated content.
As discussed in the Field of Vision section, some people with low vision see only a small amount of content and/or the user interface at a time.
The Task Force plans to add additional information in this section related to point of regard and proximity.
3.6.1 Maintain Point of Regard
Sometimes people will be viewing content and need to change the display to read it better, for example, make the text larger. If the place where they are reading (called “point of regard”) changes much, they lose their place and, especially with a small visible area and large text, it can be very difficult to find their place again.
Mouse hover changes point of regard, but is lost. Screen magnification user hovers over image, acronym, or other thing with pop-up. The pop-up is larger than their view. When the user scrolls to read it, it loses focus and disappears.
User Need - Point of Regard:
The point of regard remains visible within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed.
3.6.2 Proximity of Related Information
People with limited field of vision or who use large text have little in their field of view at one time. If related information is not close together, they can have trouble knowing about it, seeing it, and using it. In most cases, it is best if:
Related information — such as labels and controls, or matching tests in two columns, or feedback — is in close proximity.
Feedback is in close proximity to the user’s visual focus.
Dialog boxes and other such pop-up messages appear over the users point of regard.
Users are informed of new information that may be outside of their view — such as a new browser tab opening in the background.
User Need - Related Information:
Users know about and can find related information.
3.7 Work with User Settings
3.7.1 Seeing All Interface Elements
When people increase text size, increase leading, or change other text display aspects through text-only zoom or other text settings, content that is poorly designed can become unusable. For example, with text areas in web pages, sometimes columns and sections overlap, the space between lines disappears, lines of text become too long, or text disappears.
Often it is best for text areas to automatically resize to fit the text, and for users to be able to change the size of text areas. When the areas cannot be resized to accommodate all content, usually a scrollbar should be available. See also the Rewrap for one direction scrolling section.
When people use large fonts or lower screen resolution, it is not uncommon for dialog boxes to include information that is not in the viewport. In such cases, it is usually best practice for scrollbars to be provided for the dialog box.
[Draft Note: Possible figure to be added: example dialog box cut off]
Scrollbars generally provide the additional benefit of communicating where the user is in an interface.
Some users increase the size of mouse pointers in their operating system or with screen magnification software. These should not obscure tooltip text.
[Draft Note: Possible figure to be added: hover hand obscures important tooltip text]
User Need - All Elements:
Users can see all interface elements that are intended for users to see, including when users have changed display settings such as text size.
3.7.2 Printing Customized Text
It is difficult for some people to read text on the computer; they need to be able to print electronic text on paper in order to read it. For example:
It is uncomfortable or painful for some people to be in the physical position required for reading on a computer monitor, for example, some people with low vision need to be an inch away from the display. While some people have mobile devices, others have only a monitor that is difficult to move, or use a public terminal.
Some people print so they can block out surrounding text; for example, they slide a sheet of paper down as they read to cover up the line below where they are reading. Some people need colored overlays.
Sometimes people need to print text to use it away from the computer, for example, presentation notes, recipes, and repair instructions.
User Need - Printing:
Users can print content after customizing how the text is displayed.
3.7.3 Using User Settings
Most operating systems allow users to set ... [Draft Note: The Task Force plans to add additional information here.]
Most browsers allow users to set ... [Draft Note: The Task Force plans to add additional information here.]
User Need - User Settings:
Content picks up all relevant user settings, such as ... [Draft Note: The Task Force plans to add additional information here.]
Low Vision Task Force
Task Force Facilitators: Jim Allan, Andrew Kirkpatrick
W3C Staff Contacts: Michael Cooper, Shawn Lawton Henry
Editor: Shawn Lawton Henry
Content drafters: Jim Allan, Laura Carlson, Wayne Dick, Shawn Lawton Henry, Andrew Kirkpatrick
Code editors: Michael Cooper, Andrew Kirkpatrick
Task Force contributors:
Jonathan Avila (SSB BART Group)
Srinivasu Chakravarthula (Deque Systems, Inc.)
Wayne Dick (Knowbility, Inc)
Katie Haritos-Shea (Knowbility, Inc)
Shawn Lawton Henry
Andrew Kirkpatrick (Adobe Systems Inc.)
Erich Manser (IBM Corporation)
This publication has been funded in part with Federal funds from the U.S. Department of Health and Human Services, National Institute on Disability Independent Living and Rehabilitation Research (NIDILRR) under contract HHSP23301500054. The content of this publication does not necessarily reflect the views or official policies of the U.S. Department of Health and Human Services, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.