Skip to main content
Accessibility.com, LLC
Category: Visual and Media Accessibility

Low Vision

Also known as: Visual Impairment, Vision Impairment, Reduced Vision
Simply put

Low vision is a vision problem that makes everyday activities difficult and cannot be fixed with standard glasses, contact lenses, or other conventional treatments. People with low vision have reduced sight that remains even after correction, ranging from moderate to severe. It is different from total blindness, as some usable vision typically remains.

Formal definition

Low vision refers to moderate to severe visual impairment that cannot be corrected through conventional eyeglasses, contact lenses, medication, or surgical intervention. Any person with uncorrectable, reduced vision, meaning vision that is not further improved by spectacles or contact lenses, is considered visually impaired. In digital accessibility contexts, low vision informs design and testing considerations such as text scaling, contrast, and compatibility with magnification and other assistive technologies, though the clinical definitions above address the condition itself rather than any specific technical conformance requirement.

Why it matters

Low vision is distinct from total blindness because people who experience it typically retain some usable sight, which shapes how they interact with digital content. Rather than relying exclusively on screen readers, many people with low vision use their remaining vision alongside tools such as screen magnification, high-contrast display modes, and enlarged text. Digital products that assume users are either fully sighted or completely blind can create barriers for this large and varied group.

Because low vision ranges from moderate to severe and can affect different aspects of sight, no single design accommodation addresses every need. Content that does not reflow properly when magnified, relies on low-contrast color combinations, or breaks when text is resized can render everyday tasks difficult or impossible. Considering low vision during design and testing helps ensure that people who use magnification and contrast adjustments can perceive and operate a product effectively.

Addressing low vision is also part of meeting recognized accessibility expectations. WCAG includes success criteria commonly cited in this area, such as those related to text resizing, reflow, and contrast, though meeting technical criteria alone does not guarantee a usable experience. Manual testing with assistive technology such as magnifiers, alongside input from people with low vision, is generally needed to confirm that content works in practice.

Who it's relevant to

UX and visual designers
Designers make choices about text size, color contrast, and layout that directly affect whether people with low vision can perceive content. Designing for reduced but usable vision means supporting text scaling, avoiding low-contrast color combinations, and ensuring layouts reflow gracefully when magnified.
Accessibility engineers and testers
Engineers and testers need to verify that content works with magnification, high-contrast modes, and text resizing. Because automated checks detect only a portion of issues, manual testing with assistive technology and, where possible, input from people with low vision is generally required to confirm real-world usability.
Compliance officers and legal counsel
Those responsible for compliance should understand that low vision is a common consideration behind accessibility success criteria related to contrast, resizing, and reflow. Meeting technical criteria does not guarantee an accessible experience or immunity from legal claims, and requirements evolve through regulation and case law, so consulting qualified legal counsel is advisable.
Content authors and product teams
People who create text, images, and interface content influence readability for those with low vision. Clear typography, adequate contrast, and content that remains functional when enlarged help ensure that users with residual vision can complete everyday tasks.

Inside Low Vision

Reduced Visual Acuity
Low vision commonly involves diminished sharpness or clarity of sight that is not fully correctable with standard eyeglasses, contact lenses, medication, or surgery, distinguishing it from ordinary refractive error.
Field of Vision Loss
Some individuals with low vision experience restricted peripheral vision (tunnel vision) or central vision loss, which affects how much of a screen or page they can perceive at one time.
Contrast Sensitivity Limitations
Difficulty distinguishing between foreground and background elements is a frequent component, making sufficient color contrast and clear visual separation important for readability.
Reliance on Magnification and Customization
Users with low vision often depend on screen magnifiers, browser zoom, enlarged text, custom color schemes, and adjustable spacing rather than, or in addition to, screen readers used by blind users.
Relationship to WCAG Success Criteria
Several WCAG success criteria address low vision needs, including contrast requirements and the ability to resize or reflow content; criteria such as Reflow and enhanced contrast provisions were introduced in WCAG 2.1, so practitioners should confirm which version and level (commonly AA) they are targeting.

Common questions

Answers to the questions practitioners most commonly ask about Low Vision.

Does low vision mean the same thing as being legally blind?
No. Low vision refers to significant visual impairment that cannot be fully corrected with standard glasses, contact lenses, medication, or surgery, but that still leaves some usable vision. Legal blindness is a distinct classification used for certain benefits and legal purposes, and many people with low vision are not legally blind. Treating the two as interchangeable can lead to design assumptions that overlook the substantial number of users who retain functional vision and rely on it, often with magnification or contrast adjustments.
If a site works with a screen reader, does that mean it is already accessible to people with low vision?
Not necessarily. Screen reader support addresses the needs of some users who are blind or who prefer audio output, but many people with low vision navigate visually rather than through a screen reader. They may rely on screen magnification, increased text size, high-contrast modes, or custom color settings. A site can be usable with a screen reader yet still present problems for low-vision users, such as content that breaks when zoomed, poor color contrast, or reliance on color alone to convey meaning.
Which WCAG success criteria are most relevant to supporting users with low vision?
Several success criteria are commonly cited in relation to low vision, including those addressing contrast of text, use of color, text resizing, and reflow of content at high zoom levels. Some of these, such as criteria related to reflow and non-text contrast, were added in WCAG 2.1. AA is the conformance level most commonly cited as a target. Because criteria and their level assignments differ across WCAG 2.0, 2.1, and 2.2, verify the specific version and level you are targeting rather than assuming a criterion applies uniformly across versions.
How should content behave when a user zooms or increases text size?
Content should generally remain readable and functional when magnified or when text size is increased, without loss of content or functionality and without forcing horizontal scrolling in typical reading contexts. Responsive layouts that reflow content, avoidance of fixed-size containers that clip text, and testing at higher zoom levels help support this. WCAG addresses these behaviors through criteria related to resizing text and reflow, and manual testing at various zoom levels is important because automated tools may not surface all layout failures.
What role does color contrast play, and is meeting a contrast ratio enough?
Sufficient contrast between text and its background helps many low-vision users read content, and WCAG specifies contrast ratios at different conformance levels. However, meeting a contrast ratio is only one factor. Information should not be conveyed by color alone, and usability also depends on font choice, spacing, and the user's ability to apply their own color or contrast preferences. Meeting a contrast success criterion supports accessibility but does not on its own guarantee a usable experience for every user.
How can teams verify that a product actually supports users with low vision?
Effective verification generally combines methods. Automated tools can flag some issues, such as certain contrast problems, but detect only a portion of potential barriers. Manual testing should include zooming and magnifying content, increasing text size, applying high-contrast or custom color settings, and checking that content reflows and remains functional. Testing with assistive technologies and, where feasible, involving users with low vision provides the most reliable insight. This guidance is not legal advice; consult qualified counsel and current agency rulemaking for compliance questions.

Common misconceptions

Low vision is the same as blindness, so the same accommodations apply.
Low vision generally refers to significant but partial sight that is not fully correctable, and affected users often rely on residual vision with magnification, zoom, and contrast adjustments rather than exclusively on screen readers as many blind users do.
Meeting automated color contrast checks means a page is accessible to people with low vision.
Automated testing detects only a portion of accessibility issues. Meeting contrast success criteria does not guarantee a usable experience; manual review and testing with magnification and assistive technology are generally needed to confirm real-world usability.
Providing a fixed large-text option is sufficient for all low vision users.
Needs vary widely across individuals, so support for flexible resizing, reflow, custom color schemes, and adjustable spacing is generally more effective than a single preset, and requirements may differ by WCAG version and conformance level.

Best practices

Design for text that can be resized and content that reflows without loss of information or functionality, testing at increased zoom levels rather than relying on a single fixed layout.
Provide sufficient color contrast between text and background and avoid conveying meaning through color alone, verifying against the WCAG version and conformance level (commonly AA) you are targeting.
Support user customization such as browser zoom, custom color schemes, and adjustable text spacing, and avoid overriding or breaking these adjustments.
Combine automated checks with manual testing and evaluation using magnification tools and assistive technologies, since automated tools detect only a portion of issues.
Ensure interactive elements, focus indicators, and important visual cues remain clear and perceivable when magnified or when contrast is adjusted.
Treat conformance as one input, not a guarantee of usability or legal compliance, and consult qualified legal counsel and current agency guidance for obligations specific to your jurisdiction and context.