3 ms·

Hi Everyone, I created a free - research based - usability checklist, which can be used to catch common usability issues on websites before doing expensive use

by userium 13y ago

Hi 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 advance! -Nina, nina@userium.com, http://userium.com http://userium.com

ianox 13y ago
Looks good. It should help raise awareness of common issues and help make more user-friendly web sites and applications. Minor gripe: shouldn't it be alt attributes, instead of tags?
holic 13y ago
I'm seeing the content flash when checking/unchecking an item. Can I suggest toggling a class instead of wrapping/unwrapping the <del> tag? <style> .done { text-decoration: line-through; } </style> <script> $(document).on('click', '[type="checkbox"]', function () { var $this = $(this); $this.parent().toggleClass('done', $this.is(':checked')); }); </script>
TuringTest 13y ago
The title should reflect that it's a checklist focused on websites. I opened it expecting to apply it to desktop applications and was surprised by it.
kmfrk 13y ago
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 https://developer.mozilla.org/en-US/docs/Accessibility/ARIA
- snomad 13y ago
  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/checklist.pdf http://www.csus.edu/irt/web/accessibility/Resources/checklis...
cbhl 13y ago
..."pay" is be a button"... should probably say ..."pay" should be a button....
- userium 13y ago
  Thanks, I will fix that!

by userium 13y ago

ianox 13y ago

Looks good. It should help raise awareness of common issues and help make more user-friendly web sites and applications. Minor gripe: shouldn't it be alt attributes, instead of tags?

holic 13y ago

I'm seeing the content flash when checking/unchecking an item. Can I suggest toggling a class instead of wrapping/unwrapping the <del> tag? <style> .done { text-decoration: line-through; } </style> <script> $(document).on('click', '[type="checkbox"]', function () { var $this = $(this); $this.parent().toggleClass('done', $this.is(':checked')); }); </script>

TuringTest 13y ago

The title should reflect that it's a checklist focused on websites. I opened it expecting to apply it to desktop applications and was surprised by it.

kmfrk 13y ago

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 https://developer.mozilla.org/en-US/docs/Accessibility/ARIA

snomad 13y ago
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/checklist.pdf http://www.csus.edu/irt/web/accessibility/Resources/checklis...

cbhl 13y ago

..."pay" is be a button"... should probably say ..."pay" should be a button....

userium 13y ago
Thanks, I will fix that!