3 ms·

I have to agree with this one. I went round and round, with a (top of the industry) UX designer on a project we where working on. All of the profiles where call

by kls 16y ago

I have to agree with this one. I went round and round, with a (top of the industry) UX designer on a project we where working on. All of the profiles where called out to pop up a user summary when the user hovered over the profile thumb. While it was still usable it is annoying, especially for persons with disability (one of my UX specializations) screen readers like JAWS. I had to develop an entire library to trick JAWS into reading the site correctly because of these things. To me, if a user wants to see a summary of the profile, they can click, then provide an extender to show the full profile. They wanted to reserve the click for taking them to the profile. To me it is silly to kill usability because you think that a click is reserved for displaying the full information. When a link could be provided in the summary to accomplish the same task.

ultrasaurus 16y ago
"if a user wants to see a summary of the profile, they can click" Or much of the benefit can be had through the title attribute, with the bonus benefit of working with screen readers ( http://www.w3.org/TR/html401/struct/links.html#h-12.1.4 http://www.w3.org/TR/html401/struct/links.html#h-12.1.4 ) Do any of the Accessibility laws require designers to spend a day using a screen reader? I'd love to see that.
- kls 16y ago
  I always use JAWS on any project that I work on, if it does not work correctly it gets scrapped and reworked. Many times the UX designers I work with do not, are ignorant of the fact and combative about it. So in the end the onus falls on me to make the damn thing work which can require some pretty involved JavaScript tricks and browser hacks. I have thought about releasing a library of all of these accessibility helpers. As I have never really found one that focuses on accessibility.
  - wahnfrieden 16y ago
    Take a look a lt Dojo Toolkit's UI widgets (Dijit) - they at least advertise full accessibility compliance, and the set of widgets is rather comprehensive. Might save you some time in the future even if you just use them as a starting point for your own UI.
    - kls 16y ago
      Yes I use Dojo extensively, It is my toolkit of choice for a plethora of reasons, but accessibility is one of them.

by kls 16y ago

ultrasaurus 16y ago

"if a user wants to see a summary of the profile, they can click" Or much of the benefit can be had through the title attribute, with the bonus benefit of working with screen readers ( http://www.w3.org/TR/html401/struct/links.html#h-12.1.4 http://www.w3.org/TR/html401/struct/links.html#h-12.1.4 ) Do any of the Accessibility laws require designers to spend a day using a screen reader? I'd love to see that.

kls 16y ago
I always use JAWS on any project that I work on, if it does not work correctly it gets scrapped and reworked. Many times the UX designers I work with do not, are ignorant of the fact and combative about it. So in the end the onus falls on me to make the damn thing work which can require some pretty involved JavaScript tricks and browser hacks. I have thought about releasing a library of all of these accessibility helpers. As I have never really found one that focuses on accessibility.
- wahnfrieden 16y ago
  Take a look a lt Dojo Toolkit's UI widgets (Dijit) - they at least advertise full accessibility compliance, and the set of widgets is rather comprehensive. Might save you some time in the future even if you just use them as a starting point for your own UI.
  - kls 16y ago
    Yes I use Dojo extensively, It is my toolkit of choice for a plethora of reasons, but accessibility is one of them.