Legacy, oh legacy

Just got started with Working Effectively with Legacy Code (Michael Feathers, Prentice Hall) since there's a lot of legacy on my current project. Actually since I also (as do Feathers in the first couple of pages) specify legacy code as code withouht tests my current project is 99.8% legacy. A tiny little bit of code that was developed during last year actually have unit tests. But there's no automated acceptance tests, which right now seems like the biggest problem. I'm quite sure that acceptance tests will gives us the most bang for the buck in the beginning, mostly due to lack of (disciplined) testing from the client. Currently it looks like we're going to go with Selenium which I relly like, but I still think that some kind of recording functionality would be good (more efficient?). I wonder if there's some nifty way to do recording use javascript so that one could enhance Selenium... dum di dum di dum.