I don't think we have a policy for this currently.

Max, do you know who would be the right PM to triage this?

Thanks! Makes sense as a policy but no there are no plans for that and I doubt that will change without a lot more requests.  We can keep this FR open so others can star it, but realistically I doubt this one will happen unless your team wants to take this on.

Hi Max and Pavol,
We use these kiosks for password change on day one for employees in all offices at Google. Every month, we onboard thousands of people including FTEs and TVCs. The number of people who mistake this key is very high and many of them end up wasting precious time figuring out what happened to their password when everything looked good on the kiosk.

I request someone to get this policy included in the list as we can avid hours of work lost every month due to the absence of a very simple feature. Let me know if you want to VC and discuss this. 

adding Alex for Kiosk

Makes sense, but there are many policies we would like to build so we need to prioritize one way or another.  Could this be handled at the application layer in any case?

Is there a way for the kiosk app to modify this setting programmatically?

Before we start discussing a policy, have you taken a look at the input IME API to build your own interface?

https://developer.chrome.com/extensions/input_ime

This should give your app control over inputs, including "Whether or not the CAPS_LOCK is enabled" under KeyboardEventType