unicorn feedback

purely on the first screen of http://qa-dev.w3.org/unicorn/

- those form elements could do with some actual label elements to go 
with them
- could the application assume http:// when an address was simply 
entered without a particular protocol?
- why exactly is javascript a requirement to validate documents? is it 
not just a requirement for the proper operation of this initial page, 
and even there could it not be implemented in a graceful way so that, 
without javascript, everything is still perfectly functioning?


After submission with an error (e.g. omitting "http://" for instance), 
you have "Below is a stack trace from Unicorn to help solving the 
problem". Who does this help, exactly? The users or the developers? As I 
suspect it's the latter, is it truly necessary to show the stack trace, 
rather than a friendly "you forgot to put a protocol in...", ideally 
with a copy of the previously submitted form, already populated with 
what the user originally entered?

And, probably a feature that's already in the works: needs to have an 
option to actually show the source code, or at least show the particular 
line that throws errors.

Apart from that, it's looking very handy.

Patrick
-- 
Patrick H. Lauke
__________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__________________________________________________________
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__________________________________________________________

Received on Monday, 9 October 2006 20:24:05 UTC