Success Criterion 2.2.8 Timeouts - Split into two criterion?

[KristinaEngland]

Our Accessibility team at UMass reviewed the Issue 14 discussion for the Timeouts Criterion (2.2.8) and we were wondering if it is possible to separate out the criterion in this case. There seems to be two key criterion - one to actually warn about the timeout and one to extend the length of the timeout. Our staff feels that the first one - warning of the timeout should be Level AA rather than Level AAA while based on the overall concerns raised about extending the length of time and what that means seems to fall in the AAA level at this time. Perhaps the first half is covered somewhere else or there is already a plan to split the two out, but we wanted to raise it as an issue. There is also the third criterion of loss of data, but depending on the transaction, that one can also bring up questions as AA so our main focus is on the first criterion of warning the user about the timeout.

[rachaelbradley]

Proposed Response from TPAC

Kristina, thank you to you and the UMass team for your feedback. The updated version of this SC 2.2.8 does not include the ability to extend the length of time. The new language has been set at AAA because of the difficulty in accurately correlating and tracking user activity with server and client side activity.

[awkawk]

(response agreed to by WG) 12/5