Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Usability checklist – catch common problems before user testing

userium.com

Post reply on HN
Print view View original

31–37 of 37 posts

Re: Show HN: Usability checklist – catch common problems before user testing

#31

Post by vegasje »

kmfrk wrote: post #7

If you want, you can also create a raw Markdown template to use in GitHub issues, after GitHub implemented Tasks: https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-... . To Do ===== Groceries --------- - [ ] Buy milk - [x] Buy eggs EDIT: You could also play with the idea of a paid plan that allows users to create their own custom checklist using a select amount of your checks - possibly with the option of c…

Here's the Markdown template if anyone is interested: https://gist.github.com/vegasje/5454527

Re: Show HN: Usability checklist – catch common problems before user testing

#33

Post by russellsprouts »

Too wrote: post #25

> Color. Visited links color is different than unvisited. I thought most browsers disabled that feature some years ago to prevent the exploit where you could see all the websites a user has visited by sampling colors of pixels at strategic locations. Speaking of usability, what does the "reload" button in the bottom right do? For me it resets the form, not reloads it, whatever reloading a form means. Otherwise very n…

The css :visited pseudo-class now only allows certain changes, such as changing the color of text. The browser does show those changes. JavaScript can ask what color a link is, but the browser will always lie and say that the page is un-visited. If blue is un-visited and purple is visited, you may see in the browser a mix of blue and purple links, but your JavaScript will only see blue.

Re: Show HN: Usability checklist – catch common problems before user testing

#35

Post by ygra »

As it stands this is very web-centric. I'd suggest distributing all the points on different checklists for different types of applications. Relevant types that I could think of right now could be: Web site, web application, mobile app, desktop application, console application (maybe). Of course, many points would be the same for different applications, but some are only relevant to a subset (e.g. desktop applications don't necessaily need a memorable URL or use the browser's back button).

Very nice work, though.

Re: Show HN: Usability checklist – catch common problems before user testing

#36

Post by maxkir »

kmfrk wrote: post #7

If you want, you can also create a raw Markdown template to use in GitHub issues, after GitHub implemented Tasks: https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-... . To Do ===== Groceries --------- - [ ] Buy milk - [x] Buy eggs EDIT: You could also play with the idea of a paid plan that allows users to create their own custom checklist using a select amount of your checks - possibly with the option of c…

Hi,

I want to introduce a tool which allows creating custom checklists, sharing them, printing, etc. - for free: http://checkvist.com . There are some premium features, but they are not checklist-oriented. You can create list, share it with your team, clone the checklist, print it.

May be someone will find it useful :)

Thanks, KIR

Post reply on HN