diff --git a/test/spatial-navigation/frame.html b/test/spatial-navigation/frame.html new file mode 100755 index 0000000..725a29c --- /dev/null +++ b/test/spatial-navigation/frame.html @@ -0,0 +1,10 @@ + + + + Input focus test + + +

This should not get focus:

+

This should get focus:

+ + diff --git a/test/spatial-navigation/index.html b/test/spatial-navigation/index.html index 1d394ab..94af8be 100755 --- a/test/spatial-navigation/index.html +++ b/test/spatial-navigation/index.html @@ -9,9 +9,25 @@

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.

-

Link

-

Link

-

+

Regular link

+

Regular link

+ + + + + + + + + + + +
Links in TableLinks in TableLinks in Table
Links in TableLinks in TableLinks in Table
+
+

Paragraph with a long link text + that most likely will wrap.

+
+

Input type=text

Input type=tel

Input type=url

@@ -49,7 +65,7 @@

An iframe including focusable elements:
-

+

A scrollable div.

This div contains links.

@@ -61,11 +77,13 @@

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 div with the draggable attribute and the ondragstart event listener set (though it doesn't do anything). Only useful if drag-and-drop will be made keyboard accessible in @@ -80,6 +98,5 @@ 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.

-

Link