Cutomization - Disable shortcut keys

Question

We are working in an enterprise environment, where our requiement is to give Customize Firefox to the users. Only Address Bar visible to the user.
1- Hide Menus. (Task Done)
2- Icon along the Address bar. (Task Done)
3- Disable all Shortcut keys. (Partial Done)
4- Disable all commands of about (i.e about:config)
I have explored about the disabling of shortcut key, it cannot be done through user prefences js file as I did for Task 1 & 2. We can to do with xul programming as I read. We dont want to use the Third party Extensions as for this we have to do for each user. We want to do change in the base file from where user profile generated.
I have disabled the shortcut keys by editing in the [ C:\%Firefox Dir%\omni.ja\chrome\browser\content\browser\browser.xul ]
just by adding disbaled = "true" attribute
[<key id="key_openAddons" key="&addons.commandkey;" command="Tools:Addons" disabled="true" modifiers="accel,shift"/>
<menuitem id="menu_openAddons" label="&addons.label;" accesskey="&addons.accesskey;" disabled="true" key="key_openAddons" command="Tools:Addons"/>]
The Shortcut key disabled but only for the administrator but not work for the normal users whose menu disabled or not.
No issue for Admin user ethier shortcut disabled but not rest features.
Please help in this regard. Either any other file which create the user profile and for point no 4. or How to resolve this issue.

Answer 1

Looking for an alternate method to do this without an event structure.  My implementation uses a state machine with while loops, and is setup to only respond to specific keystrokes/mouse clicks, at specific times.  When in these states, it waits for the user to interract, and can not proceed until they do (by either progressing with the sequence, or aborting it).  
When I implement the method provided, it does work when it is in the state that expects F1, but if the user presses F1 at any other time, the event is triggered, and the VI goes into an invalid state (locks up).  I do inderstand that normally an event structure would be the correct implementation for keyboard inputs, but the application needs to respond in different ways depending on the user input, and needs to ignore all user input at other times.  I couldn't figure out a practical way to ignore events while in certain states, so I implemented the statem machine instead.  
Any ideas?  Working in LV 2013. Thanks in advance.
GSinMN