Good stuff! Here's few more..
Should there be one check to ensure that the site works at least somehow if javascript is disabled?
Also, there could be one check to ensure that the pages can be printed.
Show HN: Usability checklist – catch common problems before user testing
21–30 of 37 posts
Re: Show HN: Usability checklist – catch common problems before user testing
#22Hi Everyone, I created a free - research based - usability checklist, which can be used to catch common usability issues on websites before doing expensive user testing. By fixing obvious usability problems you get more meaningful feedback from user testing. Please help me make this service better by sending some feedback. Do you find this useful? Would you use this? Should I develop it further? Many thanks in advanc…
More suggestions for the accessibility list: 1. If you have to use divs and spans instead of more semantic elements like lists and headings, use precise, descriptive IDs. Same for classes. 2. Use WAI-ARIA in your HTML[1]. 3. Link skips. [1]: https://developer.mozilla.org/en-US/docs/Accessibility/ARIA
This[1] is the official CSU Sacramento checklist for accessibility, it might help flush out some of OP's checklist items. It is a bit outdated (2009) so I wouldn't necessarily recommend taking it wholesale.
[1]: http://www.csus.edu/irt/web/accessibility/Resources/checklis...
Re: Show HN: Usability checklist – catch common problems before user testing
#23If 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…
Very good suggestions, thanks for the feedback! I will continue to improve the site.
Re: Show HN: Usability checklist – catch common problems before user testing
#24Hi Everyone, I created a free - research based - usability checklist, which can be used to catch common usability issues on websites before doing expensive user testing. By fixing obvious usability problems you get more meaningful feedback from user testing. Please help me make this service better by sending some feedback. Do you find this useful? Would you use this? Should I develop it further? Many thanks in advanc…
..."pay" is be a button"...
should probably say
..."pay" should be a button....
Re: Show HN: Usability checklist – catch common problems before user testing
#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 nice list. Can probably be made infinitely long though
Re: Show HN: Usability checklist – catch common problems before user testing
#26I suggest a new name. userium is giving me a headache trying to figure out how to pronounce it.
Re: Show HN: Usability checklist – catch common problems before user testing
#27Good stuff! Here's few more.. Should there be one check to ensure that the site works at least somehow if javascript is disabled? Also, there could be one check to ensure that the pages can be printed.
Here's even more:
- Site should work even if the page is zoomed in (e.g., visually impaired people may do this). There are two kind of zooms in browsers, one zooms the whole page pixel by pixel. The other one zooms only fonts. It is usually tricky to get the font zooming look good.
- Icons and images should look good in high resolution retina screens. Bitmap graphics have a tendency to look pixelated in retina screens if not done properly. See http://www.html5rocks.com/en/mobile/high-dpi/ and http://www.html5rocks.com/en/mobile/easy-high-dpi-images/
- Some people use Screen Readers to browse the web. The web site should have easy navigation and have text for all non-textual content. See http://webaim.org/techniques/screenreader/
Also, you already mention responsive design for various screen sizes. You could mention that it means the pages should look ok on tablets and phones.
EDIT: I just can't stop... one more thing: The page should load fast even for users who are using 3G networks
Re: Show HN: Usability checklist – catch common problems before user testing
#28> 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…
Visited link coloring work on my Mac Safari 5.1.7. You can easily try it on your own browser by going to google.com and clicking a search result there. The link changes color.
Here's a good explanation what the exploit is and how it was prevented in Firefox: http://blog.mozilla.org/security/2010/03/31/plugging-the-css...
Re: Show HN: Usability checklist – catch common problems before user testing
#29I suggest a new name. userium is giving me a headache trying to figure out how to pronounce it.
Use the european pronunciation: user-eee-um.
Re: Show HN: Usability checklist – catch common problems before user testing
#30Hi Everyone, I created a free - research based - usability checklist, which can be used to catch common usability issues on websites before doing expensive user testing. By fixing obvious usability problems you get more meaningful feedback from user testing. Please help me make this service better by sending some feedback. Do you find this useful? Would you use this? Should I develop it further? Many thanks in advanc…
..."pay" is be a button"... should probably say ..."pay" should be a button....
Thanks, I will fix that!