Skip to main content
Accessibility.com, LLC
Category: Assistive Technologies

Eye-Tracking

Also known as: Gaze Tracking, Eye Movement Tracking
Simply put

Eye-tracking is a technology that measures where a person is looking and how their eyes move, typically using cameras or specialized sensors. In accessibility contexts, it can allow people to control a computer or device with their gaze rather than a mouse or keyboard. It is also used in research to study how people view and interact with content.

Formal definition

Eye-tracking refers to the process of measuring the point of gaze (where a person is looking) or the motion of an eye relative to the head, generally accomplished through specialized sensors, infrared cameras, or standard webcams. Systems capture eye position and movement data to determine fixation points, saccades, and gaze paths, which may then be used as an input method for hands-free device control or to quantify attentional and behavioral processes in research settings. As an assistive input modality, eye-tracking can serve users with motor or mobility impairments; implementation quality, calibration accuracy, and hardware capabilities vary across products. This entry describes the technology generally and is not legal advice; applicability to specific accessibility standards or requirements should be evaluated in context.

Why it matters

For people with significant motor or mobility impairments, eye-tracking can provide an alternative input method that does not depend on the use of hands, arms, or fine motor control. By measuring the point of gaze, an eye-tracking system can allow a person to move a cursor, select items, or type using an on-screen keyboard through gaze alone. This makes it one of the assistive input modalities that can support access to computers and communication devices for individuals who cannot reliably use a mouse or physical keyboard.

Beyond serving as a direct control mechanism, eye-tracking is also widely used as a research methodology. Researchers use it to study how people view and interact with content, how vision works, and how attentional processes unfold, which can inform the design of more usable and accessible interfaces. Understanding where users look and how their gaze moves can help teams evaluate whether important information and interactive elements are being noticed.

It is important to recognize that eye-tracking is one input option among many, and its effectiveness depends heavily on implementation quality, calibration accuracy, and hardware capabilities, which vary across products. Providing eye-tracking support is not a substitute for broader accessibility conformance, and the technology's suitability for any given user or use case should be evaluated in context. This entry describes the technology generally and is not legal advice.

Who it's relevant to

People with motor or mobility impairments
Individuals who cannot reliably use a mouse or keyboard may use eye-tracking as a hands-free input method to control a computer or communication device with their gaze. The usefulness of a given system depends on calibration accuracy, hardware, and the individual's needs.
Accessibility engineers and UX designers
Teams building or evaluating interfaces should understand how gaze-based input works so that interactive elements and content are reachable and usable through this modality. Eye-tracking research can also reveal how users view and prioritize content, informing more usable designs.
Researchers in psychology and behavioral sciences
Eye-tracking is used as a methodology to quantify attentional processes and to study how people read, learn, solve problems, and interact with content. This research can inform interface and content design decisions.
Assistive technology providers and specialists
Those who recommend, configure, or support assistive technology should be aware that implementation quality, calibration, and hardware capabilities vary across eye-tracking products, and that suitability should be assessed on a case-by-case basis.

Inside Eye-Tracking

Eye-Tracking as an Input Method
Assistive technology that allows a user to control a computer or device by moving their eyes, translating gaze position and dwell time into cursor movement, selection, and other input actions. It is commonly used by people with significant motor disabilities who cannot use a mouse, keyboard, or touch input.
Gaze Detection and Calibration
The process by which an eye-tracking system identifies where a user is looking, typically requiring an initial calibration to map eye movements to on-screen coordinates for the individual user.
Dwell Activation
A selection mechanism in which fixating the gaze on a target for a set period triggers an action, serving as an alternative to physical clicking. Dwell time is often adjustable to accommodate different users.
Eye-Tracking for Usability Research
A separate use of the technology in which gaze patterns are recorded to study how users visually scan and interact with an interface. This research application is distinct from eye-tracking used as an assistive input method.
Target Size and Spacing Considerations
Interactive elements must be large enough and sufficiently separated for gaze-based selection to be reliable, since imprecise gaze positioning can make small or closely packed controls difficult to activate.

Common questions

Answers to the questions practitioners most commonly ask about Eye-Tracking.

Does supporting eye-tracking mean my website meets WCAG or ADA requirements?
No. Eye-tracking is one input method used by some people with disabilities, but accommodating it does not by itself establish WCAG conformance or legal compliance. WCAG success criteria address a broad range of needs across many input methods and assistive technologies, and conformance is evaluated against those criteria rather than against support for any single device. Meeting technical criteria also does not guarantee an accessible experience for all users or immunity from legal claims. Manual testing with a range of assistive technologies, alongside automated checks, is generally needed. This is general information and not legal advice; consult qualified legal counsel for your circumstances.
Is eye-tracking the same as an accessibility overlay or widget that vendors add to a site?
No. Eye-tracking generally refers to a hardware and software input method that lets a user control a pointer or make selections using eye movements, often at the operating system or device level. Accessibility overlays and widgets are third-party marketing products layered onto a website, and their claims should be distinguished from established standards and from user-controlled assistive technologies. The two are separate concepts and should not be conflated when evaluating how content is operated by people with disabilities.
How can I design controls so they work well with eye-tracking input?
Eye-tracking selection often relies on dwell or pointer-based activation, so interactive controls that present large, well-spaced targets are commonly easier to operate. Adequate target size and spacing, clear focus and hover states, and avoiding elements that require precise or rapid pointer movement generally help. Because these considerations overlap with criteria that benefit other input methods, addressing them can support broader usability. Verify behavior through testing rather than assuming design intent alone produces an accessible result.
Does eye-tracking replace keyboard accessibility in my testing plan?
No. Supporting eye-tracking does not remove the need to ensure content is operable by keyboard and by other assistive technologies. Different users rely on different input methods, and accessibility guidance generally expects content to work across them rather than only with one device. Include keyboard operation, screen reader testing, and other assistive technology testing in your plan, since automated tools detect only a portion of potential issues.
What practical issues can interfere with using a site through eye-tracking?
Interactions that depend on precise pointer control, very small or closely packed targets, short time limits, or content that shifts unexpectedly can make eye-tracking operation difficult. Because eye-tracking may involve dwell-based activation, elements that trigger on hover or that move can create unintended actions. Reviewing these interaction patterns during manual testing, ideally with people who use eye-tracking, helps identify barriers that automated testing may not surface.
How should I verify that content is usable with eye-tracking?
Verification generally involves hands-on testing rather than automated checks alone, since automated tools capture only part of the picture. Where feasible, testing with the actual eye-tracking hardware and software configurations your users rely on, and including people who use eye-tracking in usability testing, provides the most reliable insight. Combine this with keyboard and screen reader testing so that operability is confirmed across multiple input methods rather than assumed.

Common misconceptions

Eye-tracking used for assistive input and eye-tracking used for usability research are the same thing.
They are distinct applications. Assistive input eye-tracking gives a user direct control over a device, while usability research eye-tracking passively records gaze patterns to analyze how people view an interface. A design that supports one does not necessarily support the other.
If an interface works with a mouse or keyboard, it will automatically work well with eye-tracking.
Gaze-based control introduces its own precision and timing constraints. Small targets, tightly spaced controls, and interactions that depend on fine or rapid movement can be difficult or unreliable to operate by gaze, so additional design accommodations are often needed.
Supporting eye-tracking on its own makes a product accessible or legally compliant.
Eye-tracking addresses the needs of certain users with motor disabilities but does not by itself deliver an accessible experience for all users. Accessibility generally requires meeting recognized standards such as WCAG and testing with a range of assistive technologies; this guidance is not legal advice.

Best practices

Design interactive targets to be large enough and adequately spaced so that gaze-based selection can be performed reliably, since imprecise gaze positioning can make small or clustered controls hard to activate.
Where dwell activation is used, favor adjustable dwell timing so users can tune selection speed to their own needs and reduce accidental activations.
Avoid interactions that depend on fine, rapid, or precise pointer movement, and provide alternatives that can be completed through gaze-based control.
Test with actual eye-tracking assistive technology and users rather than relying on mouse or keyboard testing alone, as gaze input has distinct precision and timing constraints.
Keep the assistive-input use case distinct from usability-research eye-tracking in your planning, since design decisions that serve one purpose do not automatically serve the other.
Treat eye-tracking support as one component of an overall accessibility strategy alongside recognized standards such as WCAG and testing with multiple assistive technologies, and consult qualified legal counsel for compliance questions.