UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
Platform: 11021.81.0

Steps to reproduce the problem:
1. Start the Chromebook
2. Go to Accessibility
3. 

What is the expected behavior?
When a Chromebook is at the login window, any user can go into Accessibility and turn on features like 'Highlight mouse cursor', 'Docked magnifier', or 'High contrast mode' and turn it on.

What went wrong?
Users can enable these settings and they stay enabled for other users.

Did this work before? No 

Chrome version: 70.0.3538.110  Channel: stable
OS Version: 70.0.3538.110
Flash Version: 

In an educational environment, students should not be able to go into Accessibility at the login window and turn on any of these features.  For example, we have students turning on 'Highlight mouse cursor' and then setting stays enabled until someone goes into Accessibility and turns it off again.  Some settings like 'Large cursor', 'Spoken feedback', 'High contrast mode', 'Screen magnifier type' and changed back to defaults once a user logs in or is idle but that doesn't help for these other settings.  I have 'Turn off accessibility settings on sign-in screen upon logout' enabled.  It would be nice to have a policy called 'Disable Accessibility at login window' so admins can choose whether or not to disable these options.