What questions should I ask to client before to start PSD 2 XHTML work?

Question

I have a PSD design file for fixed width site which I'm converting to accessible cross browser xhtml markup. It is not my design and I cannot write server side coding (php, asp.net, etc). My job is to write only XHTML, CSS and javascript/jquery if needed.

What questions should I ask my client before starting the work?

Edit:

1. Client want Template should be compatible to all A Grade browsers http://developer.yahoo.com/yui/articles/gbs/

2. and Code should be compatible with screen reader and WCAG 2.0 compatible.

3. He want if i use javascript then without javascript at least site should be function-able and accessible

Answer 1

What browsers does he want it to work in? Double the price if everything has to work in IE6.

Also, do you know what has to happen when certain parts of content are overflowing?

Answer 2

A wireframe should provide all the static information: colors, layout, proportions, etc. What you can't tell from a wireframe is the dynamic stuff: link hover styles, menu flyouts, animations, etc.

Answer 3

Ask him everything that couldn't fit into a PSD file: animations, client-side data validation, what to do on events, what to do on mouseovers, what to do on overflow, how much speed is an issue (this will effect asset compression, file formats, etc), if he wants the code commented.

Answer 4

1. Behavior, such as :hover, :focus, animation, etc. are important with PSDs, because they're not obvious.
2. Are there any concessions the client will be willing to make for certain browsers in order to fulfill for example WCAG requirements? Your work needs to comply, but does the designer's work also comply?
3. Contingency design: if there are forms, and/or if something goes wrong, what should happen? How should that look? Is there a design for it?
4. Is it clear what things will be handled server-side and what the client wants handled client-side?
5. Be careful with charging more for IE6. If you're worth your salt with CSS and use a good reset, it shouldn't really be much of an issue as far as layout/bugs go.
6. DO discuss what subtle differences are acceptable for IE6 and some other browsers: normal corners instead of rounded corners? Transparency? etc. Some of these things WILL take more time to make work for IE6, and may have performance implications.
7. Put it on paper, have them sign it, and have them be explicit.
8. Agree to this: if it's not EXPLICITLY requested/mentioned in the contract, it's not part of your work, because you haven't had an opportunity to estimate costs for it.

Hope this helps.