A browser is only as useful as it is usable — and for the millions of people who navigate the web with visual, motor, cognitive, or hearing differences, usability depends directly on how well the browser supports their specific access needs. Chrome’s accessibility features address a wider range of needs than most users realise: high-contrast mode and screen reader support for visual impairments, keyboard navigation and focus indicators for those who can’t use a pointing device, text size and page zoom controls for low vision and reading comfort, captions and transcript support for deaf and hard-of-hearing users, and reduced-motion options for vestibular and cognitive differences. We go deeper on the whole subject in our Chrome How-To Guides.
Vision accessibility — zoom, high contrast, and screen readers
The most immediately accessible Chrome accessibility tools for visual impairments are page zoom and text size control. Both work without any settings configuration:
- Page zoom: Ctrl+Plus to increase, Ctrl+Minus to decrease, Ctrl+0 to reset. Enlarges the entire page — images, layout, and text — simultaneously. Chrome remembers the zoom level per site, so returning to a site previously zoomed shows it at the saved level rather than resetting to 100% on each visit.
- Text-only font size: Chrome Settings → Appearance → Font size → slider ranging from Very small to Very large. Setting a minimum font size (also in Appearance settings) prevents websites from rendering text below a certain point size regardless of their CSS specifications. For users with low vision who encounter websites with very small body text: setting a minimum font size of 14-16 pixels causes Chrome to override any website’s CSS that specifies smaller text. This can occasionally break the layout of sites whose design depends on small text fitting into specific containers, but for users who need it, the layout distortion is preferable to unreadable text.
High-contrast display is managed at the operating system level on Windows and Mac (through Windows Accessibility settings and macOS Accessibility settings respectively). ChromeOS provides it directly in the accessibility settings panel. Chrome respects the OS-level high-contrast setting and adjusts its own interface accordingly. The CSS media query forced-colors: active tells websites that the user has requested high-contrast mode, allowing well-implemented sites to serve a high-contrast stylesheet automatically.
Screen reader compatibility in Chrome works through the operating system’s accessibility infrastructure — Chrome Accessibility on Linux, UI Automation on Windows, NSAccessibility on macOS. This exposes the browser’s content to screen readers like NVDA, JAWS, Narrator, and VoiceOver. The quality of the screen reading experience depends significantly on how well each specific website has implemented accessibility in its HTML structure — Chrome surfaces whatever accessibility information the website provides.
Chrome also includes ChromeVox, its own built-in screen reader, which is the primary screen reader for ChromeOS. It activates on Chromebooks with Ctrl+Alt+Z and provides full keyboard-navigable reading of both web content and the ChromeOS operating environment — making ChromeOS through Chrome a particularly strong platform for screen reader users.
Keyboard navigation and motor accessibility
Full keyboard navigability — browsing Chrome and interacting with web content without any mouse or pointing device — relies on Chrome’s own keyboard support combined with website-level keyboard implementation.
Within Chrome’s browser interface: Tab navigates between focusable elements on a page (links, buttons, form fields, interactive elements); Enter or Space activates the focused element; Shift+Tab navigates backward. Chrome’s Focus Highlight setting (Settings → Accessibility → Focus Highlight, or on ChromeOS in the Accessibility settings panel) adds a prominent visual indicator around the currently focused element. Without it, the default browser focus ring is often barely visible — enabling Focus Highlight makes keyboard navigation significantly more practical for users who rely on it.
Caret Browsing is one of the most valuable motor accessibility features in Chrome. Activated by pressing F7 (a toggle also available via Settings → Accessibility → Navigate pages with a text cursor), it places a text cursor on the page — similar to the cursor in a word processor — that can be moved through page content using arrow keys. This allows selecting and reading text entirely with the keyboard without needing to click and drag with a mouse. For users with limited hand mobility who can operate keyboard arrow keys more reliably than precision mouse movements, Caret Browsing transforms text selection from a difficult physical task into a manageable one.
Voice control for Chrome interaction is handled at the operating system level — Windows Speech Recognition, macOS Dictation, and ChromeOS’s dictation feature — rather than within Chrome as a dedicated browser feature. Chrome accepts voice control input from OS-level voice control systems: Windows Voice Access, macOS Voice Control, and Dragon NaturallySpeaking can all browse Chrome, activate links and buttons, fill forms, and dictate text into form fields using voice commands. On ChromeOS, the built-in Dictation feature (Settings → Accessibility → Dictation) allows voice input into any text field in Chrome with voice commands for punctuation, formatting, and basic editing.
Cognitive accessibility and reading assistance features
Cognitive accessibility encompasses reading differences like dyslexia, attention differences that make cluttered interfaces overwhelming, processing speed differences, and memory support needs that benefit from consistent, predictable interfaces.
Chrome’s Reading Mode — available through the address bar icon on article pages — strips the page to its primary content and renders it with adjustable font, size, line spacing, and background colour. The removal of visual noise from advertising, navigation, and peripheral content makes sustained reading significantly less cognitively expensive. Our guide on Chrome Reading Mode covers this in full detail.
Text-to-speech for web content is available through Chrome extensions rather than as a built-in feature. Extensions like Read Aloud, Natural Reader, and Speechify integrate with Chrome to provide text-to-speech for selected text, full pages, or PDFs opened in Chrome, with configurable reading speed and voice options. For ChromeOS users: the built-in Select to Speak feature (Search+S after selecting text) reads selected text using the system’s text-to-speech engine without requiring any extension, and highlights each word as it is read — supporting simultaneous reading and listening, a combination shown to improve comprehension for users with dyslexia and other reading differences.
Reducing motion and animation in Chrome addresses vestibular disorders, migraines, and sensory processing differences. Chrome respects the prefers-reduced-motion CSS media query, which is set by enabling “Reduce motion” in the operating system accessibility settings (Windows: Settings → Accessibility → Visual effects → Animation effects; macOS: System Settings → Accessibility → Display → Reduce motion; ChromeOS: Settings → Accessibility → Reduce motion). Sites that implement this media query serve a reduced-animation version of their interface automatically. For sites that don’t, the Chrome extension “Reduce Motion” (from the Web Store) injects CSS overrides that disable or reduce animation elements globally.
ChromeOS accessibility — the most integrated environment
ChromeOS provides the most comprehensive integration of Chrome’s accessibility features across any platform Chrome runs on, because the entire operating system is built around Chrome and designed with accessibility as a first-class concern. ChromeOS’s Accessibility settings panel (Settings → Accessibility) consolidates the full range of visual, motor, and cognitive accessibility tools in a single organised interface.
What’s available directly in ChromeOS Accessibility settings without extension installation:
- ChromeVox — full screen reader
- Select to Speak — text-to-speech with word highlighting
- Focus Highlight — keyboard navigation visibility
- Sticky Keys — for users who cannot hold key combinations simultaneously
- Mono Audio — for users with single-side hearing loss
- Large Mouse Cursor — visibility improvement
- Virtual keyboard — on-screen character entry
- Dictation — voice input into any text field
The Chrome Accessibility Settings flag at chrome://flags/#enable-accessibility-features enables experimental accessibility features not yet in the stable release — features the Chrome team is testing for accessibility users specifically. For users whose accessibility needs are not fully met by Chrome’s stable-channel features, checking accessibility-related flags periodically provides access to improvements ahead of their stable release.
Our guide on Windows 11 accessibility features covers the OS-level accessibility tools that work alongside Chrome on Windows, and our guide on Chrome Reading Mode covers the reading-focused accessibility feature in detail. For the complete screen reader compatibility documentation including NVDA, JAWS, and VoiceOver integration, the Chromium accessibility documentation covers the full technical implementation including the Accessibility Object Model APIs.
Chrome accessibility features on Windows — settings beyond the browser
Chrome’s accessibility features interact with Windows’s own accessibility infrastructure in ways that multiply available options. Windows Accessibility settings (Settings → Accessibility in Windows 11) provide system-level controls for text size, pointer size, colour filters (for colour blindness and contrast sensitivity), Narrator (Windows’s built-in screen reader), Magnifier, and On-Screen Keyboard. All of these work alongside Chrome’s features:
- Windows Magnifier enlarges the entire display including Chrome’s interface and web content — different from Chrome’s Ctrl+Plus zoom which only affects the active tab
- Windows Narrator reads Chrome’s interface and ARIA-labelled web content — a lighter-weight alternative to NVDA or JAWS for users with moderate visual access needs
- Windows colour filters apply a chosen colour scheme (greyscale, inverted, colour blind correction) to everything displayed including Chrome
NVDA and JAWS are the most widely used assistive technologies for Windows users who need full screen reader support in Chrome. Both interact with Chrome through the UIA (UI Automation) accessibility API. Configuring NVDA or JAWS with Chrome requires enabling the correct browse mode and ensuring the screen reader is set to use the UIA API rather than the older MSAA API. The Chrome accessibility team publishes release notes specifically for screen reader users with each Chrome update, identifying both improvements and known issues — essential reading for accessibility professionals supporting users who rely on screen readers through Chrome.
Using Chrome DevTools to evaluate accessibility
Chrome DevTools includes a dedicated Accessibility panel for evaluating how well a website implements accessibility for its users. In DevTools (F12) → Elements panel → select any element → click the Accessibility tab in the side panel. This shows the accessibility tree for the selected element — the properties and relationships that assistive technologies will read.
For accessibility users evaluating whether a website will work with their screen reader or keyboard navigation setup: the DevTools accessibility panel provides a technical view of what the site is communicating to assistive technologies without requiring a screen reader to be active. For web developers: it’s the fastest way to identify accessibility problems in interactive components before they reach users.
The quality of the accessible browsing experience through Chrome ultimately depends on two things: Chrome’s implementation of accessibility APIs (which is generally strong and improving), and each website’s own accessibility implementation (which varies widely). When accessibility tools don’t work as expected on a specific site, the issue is most often website-level accessibility omissions rather than Chrome feature gaps. The Chrome and Chromium accessibility teams actively address browser-level issues; WCAG (Web Content Accessibility Guidelines) compliance at the website level is what makes the browser’s tools effective in practice.
Configuring Chrome accessibility for specific needs — a quick-start guide
Rather than enabling all accessibility features simultaneously — which can produce conflicts between settings designed for different needs — start with the features that address the specific access requirement:
| Access need | Primary features to enable | Where to configure |
| Low vision (partial sight) | Page zoom, minimum font size, large cursor | Ctrl+Plus (zoom), Chrome Settings → Appearance, OS Accessibility |
| Blindness / severe visual impairment | Screen reader (NVDA/JAWS on Windows, ChromeVox on ChromeOS), keyboard navigation | Install screen reader separately; ChromeVox: Ctrl+Alt+Z on Chromebook |
| Low contrast sensitivity | High-contrast mode, colour filters | OS Accessibility settings (Windows/Mac/ChromeOS) |
| Motor impairment / limited mouse use | Keyboard navigation, Caret Browsing, Focus Highlight, voice control | F7 (Caret Browsing), Chrome Settings → Accessibility → Focus Highlight |
| Reading differences (dyslexia) | Reading Mode, text-to-speech extensions, font adjustments | Address bar icon (Reading Mode), Chrome Web Store (TTS extensions) |
| Vestibular / motion sensitivity | Reduce motion (OS-level) | Windows: Settings → Accessibility → Visual effects; macOS: System Settings → Accessibility → Display |
| Deaf / hard of hearing | Live Captions, video captions | Chrome Settings → Accessibility → Live Caption; individual video player settings |
Live Captions in Chrome
Chrome includes a Live Captions feature that automatically generates real-time captions for any audio or video playing in the browser — without requiring internet connectivity for the captioning itself (it processes audio locally using on-device speech recognition). Enable it: Chrome Settings → Accessibility → Live Caption → toggle On. A caption bar appears at the bottom of the browser window whenever audio is detected, transcribing spoken content in real time.
Live Captions work for YouTube videos, podcasts played in the browser, web-based video calls, audio files, and any other audio source the browser is playing. The accuracy is generally good for clear speech in English, with additional language support added progressively. For Chromebook users on Copilot+ hardware or Chromebooks with NPU support: Live Captions with translation adds real-time translation of captions from supported languages into English — a significantly more advanced feature that extends the utility well beyond accessibility to language learning and multilingual media consumption.
Colour blindness and colour vision differences
Chrome’s built-in colour filter settings don’t include specific colour-blindness correction modes — those are provided at the operating system level. Windows: Settings → Accessibility → Color filters → choose from deuteranopia, protanopia, tritanopia, and greyscale correction modes. ChromeOS: Settings → Accessibility → Color correction → configure correction type and strength. These OS-level filters apply to everything displayed, including Chrome’s interface and web content.
For users who want browser-specific colour blindness support without applying OS-level filters: the Chrome extension “Colorblindly” simulates different types of colour blindness for testing purposes and applies correction filters for users with colour vision differences. The advantage over OS-level filters: it can be enabled and disabled per tab, allowing comparison between corrected and uncorrected views.
Chrome’s accessibility features, taken as a comprehensive suite, reflect years of investment in making the web genuinely accessible rather than technically compliant. The combination of built-in tools (zoom, Caret Browsing, Live Captions, Reading Mode, Focus Highlight), OS-level integration (high-contrast, colour filters, screen readers), and extension-based supplementation (text-to-speech, motion reduction, colour correction) provides coverage for virtually every common access need. The starting point is identifying which category of need applies, enabling the relevant tools, and testing with the actual websites and workflows that matter — then supplementing with extensions or OS settings for the specific gaps that remain. Related: Windows 11 Gaming Features.
