![\"LRUD](\"https://github.com/bbc/lrud-spatial/blob/master/.github/lrud.svg?raw=true\")
\n\n \n
\ngetNextFocus(currentFocus, keyOrKeyCode, [scope])\n\n\n### Parameters\n\n- `currentFocus` should be an\n [`HTMLElement`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement)\n that you want LRUD spatial to consider as the element you are navigating _from_.\n In simple applications, this can just be a reference to `document.activeElement`.\n- `keyOrKeyCode` should be a\n [`key`](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/key) string or\n a [`keyCode`](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode)\n decimal representing the directional key pressed.\n- `scope` is an optional `HTMLElement` that you only want to look for focusable candidates inside of. Defaults to the whole page if not provided.\n\n### Returns\n\nAn `HTMLElement` that LRUD spatial thinks you should\nnavigate _to_.\n\n## Focusables\n\nLRUD spatial defines focusable elements as those which match any of the\nfollowing CSS selectors:\n\n- `[tabindex]` (for tabindex >= 0)\n- `a`\n- `button`\n- `input`\n\n### Ignoring Focusables\n\nAny potential candidate with the `lrud-ignore` class, or inside any parent with the `lrud-ignore` class, will not be considered focusable and will be skipped over. By default LRUD will not ignore candidates that have `opacity: 0` or have a parent with `opacity: 0`, so this class can be used for that.\n\nFocusables with a `tabindex=\"-1\"` attribute will be skipped over, however any focusable inside any parent with `tabindex=\"-1\"` will still be considered focusable.\n\nPotential candidates with `disabled` or `aria-disabled=\"true\"` attributes will not be considered focusable.\n\n### Focusable Overlap\n\nBy default, LRUD will measure to all candidates that are in the direction to move. It will also include candidates that overlap the current focus by up to 30%, allowing for e.g. a 'right' movement to include something that is above the current focus, but has half of it's size expanding to the right.\n\nThis threshold can be adjusted on a per-element basis with the `data-lrud-overlap-threshold` attribute, as a float from 0.0 to 1.0. An overlap of 0.0 will make a candidate only be considered if it is located _entirely_ in the direction of movement.\n\nPlease also note that LRUD does not consider the Z Axis, which can cause surprising results with elements that are overlapped in this way, including in the case of full screen overlays on existing UIs. The above attribute can help alleviate this issue.\n\n## Containers\n\nFocusables can be wrapped in containers. Containers can keep track of the last\nactive focusable item within them using a `data-focus` attribute.\n\n> Focusables that should be tracked must have a unique ID attribute.\n\nWhen a container has no previous focus state, it's first focusable element is\nused instead.\n\nAt this time, containers are defined as matching the CSS selectors:\n`nav`, `section` or `.lrud-container`.\n\n### Block exits\n\nIn some instances, it is desirable to prevent lrud-spatial from selecting another\n\"best candidate\" for example at the bottom of a list. To do this, a container element\nshould add an additional `data-block-exit` attribute to prevent further selection in\nthat direction. This should be a space separated list.\n\nE.g.\n\n```html\n