What you want to do is better achieved using the syntax designed for the SAS Reporting procedures (PRINT, REPORT, TABULATE). If you are using PROC REPORT, then look at the code for Examples 4 and 5 in this SUGI paper:http://www2.sas.com/proceedings/sugi27/p187-27.pdf
It shows the use of STYLE= overrides with PROC REPORT. Example 4 uses CALL DEFINE method and Example 5 uses the user-defined format method.
The user-defined format method will also work with PROC PRINT and PROC TABULATE....however if you are generating your output from tasks in EG (either the LIST DATA task or the SUMMARY Tables task, you would have to alter the generated code to see the desired result. Also, the syntax for doing your traffic lighting will be slightly different for PRINT and TABULATE than it is for REPORT.
There is yet another way to alter the output of any other SAS procedure -- by this I mean, if you are producing your output with PROC GLM or PROC REG or PROC MEANS or PROC FREQ, you could also alter the TABLE template used with these procedures to achieve the kind of traffic lighting you want through the use of the CELLSTYLE...AS statement. The CELLSTYLE statement is illustrated in this FAQ, but NOT shown with a procedure's table template: http://support.sas.com/faq/032/FAQ03257.html
For more help with this technique, you might consider contacting Tech Support, as they can help you identify the TABLE template that you would need to change.
Finally, if you wanted to alter the HTMLPANEL tagset directly (by changing the HTML tags that were written for your output), you would use a technique similar to the tagset technique shown in this FAQ: http://support.sas.com/faq/032/FAQ03257.html Again, you might consider contacting Tech Support for more help with this technique, as the syntax of TAGSET templates and modifying TAGSET templates is an advanced use of SAS.
As for the BEEP requirement -- I know there used to be an ASCII code that would cause a teletype terminal to beep. I don't know whether that still works or not. Tech Support is your best bet for help with this requirement. Maybe there's a CSS or HTML way to achieve this.
When I open a web page, and it then opens another included page (which is usually advertising something), I make a mental note to avoid ever visiting that page again. I find that is an unwanted intrusion.
Sadly, your requirement to have a beep created by the web page will require similar coding and may not make you very popular with your readers. Indeed, it is possible on many web browsers now to block a web page from calling another, or making a system call. Given the potential for harm to be caused to the visitors computer by the system call, this is long overdue.
I think you may want to abandon that requirement as something that may work for some people for a short time, and will then fail in the future.