...
We received some revisions to the proposed look and feel. On July 27th the ZEST:attached PDF was provided as feedback along with the following comments in email:
Okay, I have collected the feedback for you. I'm presenting it in raw form, because I don't want to put a barrier between you and ideas unless it is actually helpful. One thing I can say - you don't need to worry overmuch about the fiddly details of text. We need help figuring out where we need a heading, a sentence, or a paragraph, but given a general idea of what should be where, we feel comfortable hashing it out with the various internal folks who need to be satisfied. So long as I understand what you're referring to in a particular place, I can talk to them and figure out what the final words should be.
One of the replies is in the form of a pdf file (attached), and the rest are in text, below:
-----------------------
One piece of feedback on the "success" pages for tickets and certificates -- having just a checkbox for the "Always use ..." options is problematic, since the "continue" button takes you back to the calling web site. That's why we're using a button for this currently in the test environment. (We could have a checkbox with, say, a "Save" button for it, but it seems better to minimize the number of clicks a user has to make).unmigrated-wiki-markup
\[ZEST:The other idea we have discussed is to have a checkbox like this on the login page, and perhaps have a separate (new) page allowing you to set the preference. But that would require fairly significant effort, which I fear we don't have time for at this point.\]
Has she said anything specifically about this? Can we ask about using a button instead of the checkbox (or some other way to get the preference cookie saved)?
-------------------------------------------------------------------
1) It's important that we come up with a name for the service and have that clearly displayed on the page. This will give people something to refer to this by and will help avoid any kind of confusion with explaining what it is that they are referring to when they call regarding issues.unmigrated-wiki-markup
2) The username/password form will not only be used by people with MIT IDs. It's expected to be the entry point for MIT people who choose to log in using their Kerberos authentication as well as other folks who have non-MIT (external IDs). It's misleading to ask people to enter their MIT ID and to specify that this is the preferred way to log in for MIT collaborators and visitors. In this case, it may be better to stay away from trying to explain and leave it up to users to decide what log in method works best for them. *\ [Note: this is inaccurate. The current intent is to have a seperate IdP and login server for people with an external email address. \ -pbh\]*
3) This one's more cosmetic but I was wondering why we picked the color palette we did? Is it really helping us to make it look so different than anything else our users are familiar with?
...