Spatial Navigation

Written: 2017-10-17, Updated: 2018-12-12

Spatial Navigation provides a processing model and standards APIs for directional(top/left/bottom/right) focus navigation using arrow keys, jog shuttle, and gesture on several devices. (e.g. TV, feature phone, game console, IVI system)

This repository is for supportive tools such as polyfill, demo, and relevant documents. The spatial navigation spec has been migrated from WICG to CSS WG as an official draft according to the decision at the CSS WG meeting in TPAC 2018.

You can raise a spec issue in CSS WG, but also raise others(polyfill, demo, ideas) in WICG here.



Spatial navigation is the ability to navigate between focusable elements based on their position within a structured document. Spatial navigation is often called ‘directional navigation’ which enables four(top/left/bottom/right) directional navigation. Users are usually familiar with the 2-way navigation using both ‘tab key’ for the forward direction and ‘shift+tab key’ for the backward direction, but not familiar with the 4-way navigation using arrow keys.

Regarding TV remote control, game console pad, IVI jog dial with 4-way keys, and Web accessibility, the spatial navigation has been a rising important input mechanism in several industries. If the web can embrace the spatial navigation and efficiently support the functionalities in web engines and W3C standard APIs, it will be more promising technology for existing products as mentioned above and various upcoming smart devices.


Prior to the requirement explanation, we need to first understand how the arrow keys currently work on the web. If you’re watching this page in a normal HD monitor and desktop, not mobile, please push a down-arrow key on your keyboard. What happens? Basically, scrolling downward would be triggered. That’s the default behavior of arrow keys in the web, only when the page is scrollable in the direction.

In spatial navigation mode, the default behavior of arrow keys is changed from scrolling behavior to focus moving so that users can use the arrow keys to navigate between focusable elements based on their position. To support the functionalities of the spatial navigation, we should consider the following three steps:

  1. A heuristic algorithm to be supported in web engines by default (e.g. how to judge a next best focusable element)
  2. Overriding methods on top of the heuristic algorithm (DOM method/attribute/event as standard APIs)
  3. Some relevant APIs for efficiently supporting the spatial navigation (e.g. setting an element as a container)

See the explainer for the details of W3C standardization for #1, #2 and #3 above.

See the implStatus for the details of the implementation in web engines for #1 above.


Q. I’m not sure how the spatial navigation works.

Q. Isn’t it enough just using the relevant web frameworks?

Q. The spatial navigation seems not the general feature esp. in mobile with no physical key-based interface.

Q. I would like to raise an issue or idea about spatial navigation.