Microsoft is working to bring built-in eye-tracking to Windows 10. Currently called Eye Control, Microsoft explains (opens in new tab) that the feature is currently available to test for Windows Insiders (via MSPU).
The feature works using the Tobii Eye Tracker 4C, which can track where a person is looking on a screen. With it, users can navigate the OS using only their gaze. And while Tobii's tracker is the only one supported at the moment, Microsoft is working to support others on the market.
The basis of Eye Control was initially developed as part of a hackathon in 2014 as a way for people with ALS to drive a wheelchair using the movement of their eyes and controls on a Surface. Microsoft says it was inspired by the project to adopt eye-tracking technology in Windows 10 as an accessibility feature.
If you're a Windows Insider, the feature can be tested in the latest Insider builds — provided you have access to the Tobii Eye Tracker 4C. The feature is expected to launch with the Fall Creators Update as a general public beta. The Fall Creators Update will also herald a number of other accessibility improvements mostly centered on things like Narrator and tools to assist in reading and writing.
Dan Thorp-Lancaster is the Editor in Chief for Windows Central. He began working with Windows Central as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. Got a hot tip? Send it to email@example.com.
People complained about 'telemetry' tracking. Goodness knows what those people will say about eye tracking :) All accessibility improvements are great for those that need it and enable it though. Lots of features like this don't make the 'big feature' list reported about but can really help many people.
Surface Phone / Mixed View / Surface Glasses.... That's all I read.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.