2.1.1 requires all functionality of the content to be operable in a non-time-dependent manner through a keyboard interface. However, many Web sessions eventually time out, and there is no practical way to design the server software to avoid this. Even when the Web content complies with criterion 2.2.1 and 2.2.6, which in many cases requires the user have some control over such time-outs, that does not make it comply with 2.1.1.
Define "non-time-dependent manner" as "method that does not require user action within any period shorter than ten minutes", or else add a Note to 2.1.1 explaining that server-based session time-outs of at least some minimum duration are not considered part of the content.
Time-outs are covered under another success criterion. This refers to not requiring individual keys to be pressed or released under particular time contraints. To make this clear, we have rewritten the SC to
2.1.1 All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.