Feedback on MWBP 1.0

Hi all,

Coming from a perspective of user centric design can I make the following comments...

1) I can't see any reference in the document to any customer based research, surely it would be better to ask actual users of mobile devices about their experiences and desires for best practice are going forward? Otherwise we run the risk of defining what experts within the industry think is best, not what users think works.

2) Secction 5.2.5, Error Messages - you state at the start of the document that you want to try and encapsulate things that are specific to mobile experience, therefore while i completely agree that 'useful' error messages are great this is surely a web design guideline? 

3) 5.2.6, Testing - how many devices are now in captured inWURFL and how many devices are launched each year (with subtly diff version evolving over a device lifetime) - so how useful is a statement like..
 - Consequently testing should be carried out in as wide a range of real devices as is practical
Shouldn't there be some push to the device manufacturers/browser developers to help with by standardise]ing where practical?

4) 5.3.2 - Provide a Site Map - web based site maps can be very useful, but a large site map on a mobile device... just a long list, hardly good user experience. 

5) Use a small graphic at the top of the page to illustrate what site the user is on and where on the site they are at
This contradicts the point about not using graphics where text would suufice - it seems to be referring to some form of breadcrumbing navigational aid, which is surely better as text anyway. If a graphic were to be used we'd need to educate users on what it's trying to tell them.

6) Most of the points re Navigation are just good web practice (though of course that doesn't mean you see it on the web either), wouldn't it be simpler to refer out to perfectly good sources for these (Jacob Nielsen seems the most obvious - in fact wouldn't he be a good addition to your group?)

7) 5.4.7 Color - Interesting one here (and in a few other places) as clearly they you are rightly conscious of the visual impairment issues (>30% of people have some form of limitation) but isn't a better way to address this within the guide to suggest use of  'Graphics lite', 'Accessible' or 'High Contrast' menu option... and what should happen if the web source has such an option already, as many do?

8) 5.5.2, Frames, 5.5.4 Tables etc - Guide says Don't use these (agree re frames) and also dont use 1x1 gifs to control layout - BUT do use CSS when a device supports it - so if a device doesn't support CSS we should not use any other device to provide a 'nice' layout? This seems a somewhat limiting best practice.

Many thanks for your attention

Tony Cawood