Keyboard (no exception)

Silktide prompts you to verify that every function on the page can be operated using only a keyboard, with no exceptions. This is success criterion 2.1.3 (level AAA) - the stricter form of 2.1.1 Keyboard.

This is a : proving full keyboard operability requires a person to try every control. Silktide raises the prompt on each page and a person confirms it.

Why this matters

2.1.1 (level A) already requires keyboard access, but allows an exception for functions that depend on the path of the user's movement

freehand drawing, signatures, some games. 2.1.3 removes that exception: if the site claims AAA, even those functions need a keyboard alternative (for example typed coordinates, an upload of a drawn image, or a step-by-step form).

People who cannot use a pointer - including many switch and voice-control users - need that alternative.

What to check

Tab through the whole page. Every interactive control must be reachable and operable using only a keyboard.
Look for path-dependent features: drawing canvases, signature pads, drag-to-reorder, gesture-only controls. For each one, confirm there is a keyboard (or non-pointer) way to achieve the same result.
Confirm there are no keyboard traps (see also Applet or plugin focus).

Silktide's Keyboard support check already flags many Level A failures automatically; this review covers the stricter AAA threshold.

How to fix it

Provide a keyboard alternative for every path-dependent control (typed input, upload, step-by-step form, or equivalent).
Ensure custom widgets follow the ARIA Authoring Practices keyboard patterns for their role.
Never rely on pointer-only gestures for essential tasks.

If every function on the page is keyboard-operable (including those that would be exempt under 2.1.1), the finding.

How Silktide tests this

Silktide cannot prove keyboard operability from a crawl, so this check raises one review prompt per page describing what to verify. Related automated and assisted checks under 2.1.1 still run. No mainstream tool automates 2.1.3 - there is no W3C ACT rule for it.