I got the same delay already mentioned on the over state of the graphic buttons and I'm on cable (IE/WinXP - SP2/1024x768). I haven't looked at the code, am more of hobbyist/student/lurker on this list. I guess my comments are from the pov of the visitor. Hope they help. An expectation -- when I clicked on About, I expected to see info About the organization, as I had already read about the service on the intro page. I learned nothing new about the organization on that particular page, though there were 2 more pages linked there about staff and partners -- perhaps that's enough though. I wonder, since the text on that About page summarizes what is on the intro page if it would work better as the intro page, It would also possibly fit and the visitor would not have to scroll to read the rest. But just a thought...
Eileen Russell http://www.bytedreams.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lachlan Hunt Sent: Thursday, March 02, 2006 10:32 AM To: wsg@webstandardsgroup.org Subject: [WSG] Site Check/Launch: Edentiti.com Hi Everyone, A new site I recently developed the front-end for over the past few months, called Edentiti [1], has just officially launched and I wanted to get some feedback about the usability, accessibility and over functionality in whatever browsers you can get your hands on. I've tested in various Windows and Mac browsers during development, but as is always the case, bugs tend to sneak in wherever they can and something may have been missed. (I know there are bugs in IE7, but I'd rather wait till MS actually release something that isn't a joke like both betas 1 and 2 were before I bother testing/fixing with it - the one to be released after Mix '06 looks slightly more promising) For all you DOM Scripting fans, if you go to step 2 of the Create an Edentiti section, there's a funky form validation script you might want to check out. http://edentiti.com/create/ (click next, to get to step 2) [1] http://edentiti.com/ PS. I know the markup is currently XHTML and I'm aware how much of a hypocrite that makes me :-), but, given the time constraints, it was a limitation of the back end solution we had to accept, with plans to convert it to HTML4 later on. -- Lachlan Hunt http://lachy.id.au/ ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
