By the way, please forgive me if these posts are in the wrong forum, I couldn't find anywhere else to put them.

The menus on here are completely inaccessible via the keyboard because they aren't actually links, and because of this, the normal mouse link actions don't work either (like CTRL+Click or middle click to open in a new window, or right-clicking to copy the URL).

In addition, the drop-downs are too hard to read, because the background is translucent and they frequently overlap text.

Nope, this is totally the right place.

That's correct, the menus aren't accessible via keyboard. I can do something about the translucency, but the keyboard accessibility wasn't a primary design goal for the site. Not saying it won't be going forward - just trying to set an expectation that it's not something likely to be changed in the very near term.

Hmm. It is evidently harder than I thought. I'm having trouble tracking down where the transparency is coming from - it isn't in the stylesheet (well, it was, so I took that out). Bear with me - it's not forgotten; I just need to hunt it down.

EDIT: Okay, found the little blighter. It was an undefined CSS class, somehow. Anyway... non-transparent. I'll let folks make background color suggestions if they don't like the default gray.

Looks good. It would be nice if they were ... you know ... real links. But at least now they're legible :)

I guess I should say: *normally* hitting enter on a form (other than in a textarea element) submits the form. It _appears_ to do the same here (since the page actually reloads) ... but the search doesn't happen. As far as I can tell, that's because they didn't put an actual form in for the search, -- in typical ASP.Net fashion, they're wrapping the WHOLE PAGE in a form, so they didn't actually create a separate search form, so when ENTER submits the form, it doesn't *DO* anything, since the main form doesn't have any default action coded for handling the search box (instead, they ONLY search when you click the command button). Frankly, wrapping the whole page in a form is just a sloppy way of creating "buttons" for page events... but it's typical Asp.Net code

REPOST because of the html (wow, typing tags into the "design" put a textarea in my post ... that's kind-of scary).

I guess I should say: *normally* hitting enter on a form (other than in a TEXTAREA element) submits the form.  It _appears_ to do the same here (since the page actually reloads) ... but the search doesn't happen.

As far as I can tell, that's because they didn't put an actual form in for the search, -- in typical ASP.Net fashion, they're wrapping the WHOLE PAGE in a form, so they didn't actually create a separate search form, so when ENTER submits the form, it doesn't *DO* anything, since the main form doesn't have any default action coded for handling the search box (instead, they ONLY search when you click the command button).

Frankly, wrapping the whole page in a form is just a sloppy way of creating "buttons" for page events... but it's typical Asp.Net code

We permit HTML in posts. A Textarea is HTML. No biggie.

No, the Enter isn't being used to submit the form - because as you notice there's no form. It's just reloading the page. The "submit" isn't a "submit button," so there's no way a browser could "see" it as a submit button - it's just a link with some javascript behind it.

And it *is* the way ASP.NET is usually done, you're right.