Ok I'll walk you through it. As an IT guy you really need to know this stuff anyway.

In javascript { and } are just like ( and ) in C... they just group your function together so the program knows how far to go.
To save space and processing time (not that you'll notice) what I did was make an event equal to a function, instead of just making the function elsewhere and calling it.
So the event "document.onkeup" is made equal to the function :
function(e) {
...
...
}
That "e = e || event" business is just a way to transform whatever event happened and it's arguments (in this case a keyup event) in a variable so that we can work with it easily.
After that we've got a switch statement. A switch statement is just like the one you'd find in C with slightly different syntax. We are comparing the keyup value of "e" to various values, 4 in total. These 4 values in this particular instance are 37, 38, 39 and 40, which are the scancodes for up, down left and right on the keyboard. The "function1(args)" I put in each one doesn't do anything... that was just an example of the syntax you should use.....
Let me set a few up for you so you can get the hang of it. Remember where I said you can look at your click events? I'll just pull two random ones off of the bottom of the file you posted:
<input type='button' value=" " onclick="change_element('score_left', 1)" id="plus_left_label"><br />
<input type='button' value="-" onclick="change_element('score_left', -1)" id="minus_left_label">
We want what "onclick" equals.
So lets make a new switch statement that specifically uses those two.
=================================
document.onkeyup = function(e) {
e = e || event
switch(e.keyCode) {
case 38: // up
change_element('score_left', 1)
return false
case 40: // down
change_element('score_left', -1)
return false
}
}
=======================================
Now the up and down arrow keys will add and subtract to the left score. You can put the function anywhere in the "<script>" section really. I put it just after the "set_element" function towards the top of your file.
You are going to have to customize this obviously, adding enough cases for all of your functions and changing their comparative numbers to whatever the scancodes for the keys you wish to use are. That link I posted originally has a big-old table with all of the values in it for you.
Once you do this, if you no longer want the buttons, you can remove them from the file... just don't remove the functions they call.