Designing for low vision

Learn how to design web content that’s accessible for people with low vision.

On this page

What is low vision?

Low vision is vision impairment that affects a person's everyday activities and cannot be fully corrected with glasses, contact lenses or other standard treatments. Some people with low vision may identify as blind while retaining some useful vision.

People with low vision have diverse experiences. They may have:

Some people’s vision also changes overtime.

These differences mean there is no single text size, colour combination, typeface or magnification level that is accessible to everyone.

How people with low vision use the web

People with low vision may change how content is displayed or use assistive technologies to make it easier to perceive and read. Strategies include:

People may use several of these strategies together and may change them for different content, devices and environments.

For more, see the Knowledge Area: Adaptive Strategies .

Zoom and text resizing

Enlarging content is an important way people with low vision use digital content. Browsers, operating systems and assistive technologies provide different ways to enlarge a web page, text or magnify part of the screen.

Do not design for one particular zoom method or level. Design content so that people can enlarge it using the features available to them without losing information or functionality.

Design for enlarged content

As content becomes larger, the available space becomes smaller. Layouts should adapt so that content remains readable and usable.

In particular:

Do not prevent zoom

Do not prevent people from enlarging web content. Users need to remain in control of the size at which they view a page.

Browser and device behaviour changes over time. Test with the browsers and devices your service supports rather than relying on assumptions about which zoom features a particular browser provides.

Resize Text

Text must be resizable up to 200% without loss of content or functionality, as required by WCAG 2 Success Criterion 1.4.4 Resize Text.

Follow the W3C guidance for techniques and testing considerations. Do not rely on a particular browser zoom setting as the only way of determining whether the requirement has been met.

For advice on text resizing in mobile apps, see Text contrast and typography — Knowledge Area: Mobile applications.

Reflow

People who substantially enlarge content should be able to read and operate the page without repeatedly scrolling backwards and forwards to see it all.

The reflow requirements and exceptions for content at narrow viewport dimensions are in WCAG 2 Success Criterion 1.4.10 Reflow.

Follow the W3C guidance when testing reflow rather than relying on a particular device, browser, screen resolution or zoom percentage.

For advice on reflow in mobile apps, see Responsive design and reflow — Knowledge Area: Mobile applications.

Screen magnification

Screen magnification enlarges part of the display. For more, see Screen magnifiers — Knowledge Area: Assistive technologies.

At high levels of magnification, a person may see only a small part of the page at one time.

Design interactions so that important information is not easy to miss when only part of the interface can be seen.

Where possible, show related content next to each other, and the result of an interaction close to the control that caused it. This helps people using screen magnification find changes and related content without having to search other parts of the page.

For example:

Fixed and sticky content

Content that remains fixed in the viewport can take up a large proportion of the available space when a page is enlarged. It may also obscure other content.

Keep fixed and sticky content to a minimum. Where it is needed, make sure it does not prevent people from seeing or operating other content when the page is enlarged. Allow non-essential overlays and similar content to be dismissed where appropriate.

Hover content

Do not rely on pointer hover as the only way to access information or functionality. Content that appears on hover can be especially difficult to use with screen magnification. This is because the user might need to move the pointer to bring the new content into view, but that moves the pointer off the element that triggers the new content, which makes it disappear.

When content appears or disappears in response to pointer hover or keyboard focus, follow WCAG 2 Success Criterion 1.4.13 Content on Hover or Focus.

User display preferences

People with low vision may change colours, contrast, text size, spacing and other display settings. Design web content so that it continues to work when users apply their own preferences.

For some of the ways that users change display settings, see Customising how content is presented — Knowledge Area: How disabled people use the web.

Colour and contrast

Text, controls, focus indicators and meaningful visual information need sufficient contrast to be perceivable.

For guidance, see the Knowledge Area: Colour and contrast .

Colour schemes

Some people find light content on dark backgrounds easier to read, while others find dark content on light backgrounds easier.

Where your service provides more than one colour scheme, make sure each scheme remains accessible. Where appropriate, web content can also respond to a person's light or dark colour preference.

For current technical guidance, see prefers-color-scheme — MDN Web Docs .

Forced colours

Some people use settings that replace website colours with a limited colour palette chosen by the user or operating system. Make sure important information, controls and interaction states remain perceivable when colours are replaced.

For current technical guidance, see forced-colors — MDN Web Docs .

Text spacing

People may increase the spacing between lines, paragraphs, letters or words to make text easier to read. Avoid layouts that break, clip text or hide content when text spacing is changed.

Text content on the web needs to accommodate certain changes in text spacing. For more, see WCAG 2 WCAG Success Criterion 1.4.12 Text Spacing and follow the associated guidance for testing.

Reader modes

Some browsers and operating systems provide reader modes that present suitable content in a simpler view. Depending on the reading tool, users may be able to change characteristics such as text size, typeface, spacing and colours or have the content read aloud.

Reader modes can be useful to people with low vision, but they are not available for every page and work differently across browsers and devices.

Use well-structured semantic HTML so that the meaning and structure of the content can be understood by browsers and assistive technologies. For article-like content, it can also be useful to check how the content is presented by common reader modes.

Do not rely on a reader mode to compensate for accessibility problems in the original page.

For current information about browser reading features, see:

Typography

There is no single typeface, text size or presentation that is most accessible for everyone. Aim for clear, legible typography and allow people to adapt text to their needs.

In general:

For more about the needs underlying these recommendations, see Accessibility Requirements for People with Low Vision — W3C .

Images of text

Use real text rather than images of text where possible. Real text can usually be enlarged, recoloured and otherwise adapted more effectively to a person's needs.

For more, see:

Printing

Some people with low vision print web content so they can read it at a preferred size or in a different environment.

If the content is intended to be printed, check that meaningful information is not clipped, hidden or omitted when printed and that the printed presentation remains clear when users apply print scaling.

Do not assume that one paper size, text size or colour scheme will meet everyone's needs.

For current technical information about styling web content for print, see Printing — MDN Web Docs .