Change RSVP response form drop-down to radio buttons

Ok, I posted this under enhancement request trying to make sure I wasn't being rude with my issue on something that could wait that isn't actually a 'functional' bug, but is a 'usability' bug. However, I haven't had any response what so ever; not even a comment. Now I am asking for some basic support in terms of a question that is likely easy to answer for someone familiar with making code changes like this. If you carefully read the issue and test it yourself, you'll find that it is very easy for the user to make the mistake (in the original post) on the response form. In my opinion, if it is happening to my average user it's likely to happening to everyone else. Can someone please reply? I'm sure its a simple solution, but my clients entire organization is apprehensive and has decided NOT to use their website RSVP until the issue is solved.

In my opinion the issue does have something to do with the RSVP module design. Even though the module is using a standard drop-down menu convention, the choice of the RSVP module developer was to use a drop-down form field instead of another field type, like radio button. The field itself works just fine; that's why I originally posted this issue as an actual usability issue and not a software defect. However, even though it is a usability issue, it can have considerable impact to the use of the application. In my case, the organization won't use the web RSVP because of the issue. Even though you could just blow this off and call them stupid users ... so be it ... maybe they are ... but the issue could be avoided all-together with a different form field type. AND ... a majority of users are NOT savvy and are probably making the same mistakes. You even know what I mean because its that obvious and easy to do. Why not just remove the limitation of a drop-down box all together if its going to cause an issue. This would only improve the product rather then saying stupid people can't use this because they forget to deselect from the field before scrolling down to submit.

I truly believe that the usability can be improved without impacting functionality by changing the form field type to something that wouldn’t scroll when the user tried to scroll down the screen to submit the input.

I'm glad you understand what I am talking about though. That helps! :)

Any chance you could give me some clues about how to change the code myself? I come from a technology background for a large company and understand how long it could take, if ever, to wait on users to vote on issues like this. If I could make an override or something it would mean my users could actually use the RSVP module instead of me having to find another alternative to what is available. Don't get me wrong, I appreciate that the work is free, the module is functioning and all of that ... my users simply will not use it (at all) if it means the administrators are going to have a number of issues trying to justify what users meant to have happen by using the web-based RSVP system. The whole point was to automate the process instead of having an admin have to justify all of the results. If that were the case, just because I have average users, they choose not to use it at all. I wouldn't like that myself because it means I have to find another solution not only for their website, but for use with Drupal sites, altogether. I don't want to have to do that because drupal rocks. Anyway, let me know. At the very least, is there any way of escalating your results by conducting a poll, survey or review to get answers to what your users want, rather then think they will see my post and trail on. Could it be a more public forum article or something where its visibility won’t suffer from being buried beneath tech support request tickets? Whatever you can think of would be great.