Press shift+down (or another shortcut associated with spatnav) repeatedly to navigate through the elements.
Expected result: Both links, form fields and other interactive elements are traversable by spatnav.
Elements that can consume shift+arrows themselves (e.g. a multiline textarea) should only be prefocused, not focused,
so you can navigate past them without interruption and without changing any values.
Links in Table | Links in Table | Links in Table |
Links in Table | Links in Table | Links in Table |
Paragraph with two links that will wrap.
"Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea ommodo consequat.
Input type=text
Input type=tel
Input type=url
Input type=email
Input type=password
Input type=date
Input type=time
Input type=number
Input type=range
Input type=color
Input type=checkbox
Input type=radio:
Input type=file
Input type=button
An iframe including focusable elements:
A scrollable div.
This div contains links.
.....
.....
.....
.....
.....
Also links below the fold that should be scrolled into view with Spatnav.
Span with onclick listener. Try to click me by keyboard!
Span with tabindex=0.
This is a span with a pointer cursor. It usually indicates something clickable for mouse users and can be reasonably expected to be interactive. Not included as a spatnav target in old Opera, but I think it does no harm and may fix a few additional cases where web apps aren't specifically developed with keyboard accessibility in mind.