...
The UX Scorecard aims to do just that. It's a measuring stick that we'll use to gage the "qualitygoodness" or "badness" of Sakai's design, leading to . We'll then use that knowledge to make measurable and meaningful resultschanges.
How does it work?
This image is just a sample of what the UX Scorecard will look like.
...
Visual design is more than skin deep. What we'll be looking for is symmetry, good use of contrast, scale, proportion, and various other attributes that make each screen easier to visually comprehend.
E. Compliant Compliance with Trends & Standards
In this section, the scorecard will try to tackle good front-end coding principles, compliance with accessibility standards, adherence to style guides, as well as questions related to relevance (for example: Is Sakai's "user experience" what most user's expect given todays technology and design standards?).
For more information on accessibility analysis, take a look at what ~melledge Former user (Deleted) put together: Sakai Test Protocol--Firefox Accessibility Extension and WAVE 3.5 Combined. This, and other Fluid inspired protocols, will be heavily relied on to make sure this scorecard gives both you (the stakeholder) and us (the designers) the most reliable information on the status of Sakai's design quality. Because let's face it, it's hard to fix something if you don't know what's broken.