Hi Rachel,
MARKUP
Although the 2-column split may be efficient in terms of screen real
estate, the form will be less-likely to be misinterpreted if no.s 1-4
are grouped either in a single column or as a single 'row'.
The row example might look something like this:
(Headers) School | Economics | Art History | Finance | Art History |
Total Check
(Row) SchoolName(<th>) | Percentage | Percentage | Percentage |
Percentage | Total
Where the 'Percentage' is an input field, perhaps with a title
attribute and/or placeholder zero (cleared with JavaScript when the
user tabs/clicks in the input field).
ACCESSIBILITY
Accessibility-wise there are a number of ways of marking up the table
to make clear the relationships between header elements and data,
including specifying an abbreviation attribute for the discipline
headers.
Alternative <td> backgrounds for each column to visually reinforce
the relationship between the header and the percentage value for each
discipline.
USABILITY
Not sure as to the function of the drop down menus (if this is what
the down arrow represents)? If each menu lists all four subject
options, then you might run the risk of duplicates, e.g. two entries
for Economics. If this is an interface to customising a survey form,
then you may have more than four subjects per school, and would need
an option to add additional subjects?
Unless there is a meaningful connection between this number and a
real world support, such as a printed questionnaire, remove the
number before each discipline.1.,2., etc. are not meaningful labels
for the discipline input fields/menus.
Remove potentially confusion percentage signs. If SAEL, SACL, etc.
are the names of schools, then they are not percentage values?
'Split' suggests the value to be entered might be in the form 'x/y'
(whole numbers) rather than a percentage value. Depending on who will
be imputing the data, perhaps it would be more suitable to collect
whole number values rather than percentages. (As students rarely come
in less than whole units). In such a case, the user would enter the
total number of students and then the number for each discipline.
This would remove the requirement for data manipulation prior to
using the form and prevent potentially issues with round errors,
normalise the data collected for as yet unconsidered forms of
analysis, etc., etc.
It's difficult to recommend meaningful markup and/or a
standards-based solution when the purpose of the interface is
unclear. I generally find it easier when to move from function to
form.
By now, certainly OT.
Cheers,
--
Andy Kirkwood | Creative Director
Motive | web.design.integrity
http://www.motive.co.nz
ph: (04) 3 800 800 fx: (04) 970 9693
mob: 021 369 693
93 Rintoul St, Newtown
PO Box 7150, Wellington South, New Zealand
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
