Comments for Designing the DrProject User Experience http://www.lizblankenship.com/drproject/blog Just another WordPress weblog Thu, 18 Dec 2008 23:12:26 -0800 http://wordpress.org/?v=2.8 hourly 1 Comment on To do list mockup by Inception « Nick Jamil’s blog http://www.lizblankenship.com/drproject/blog/?p=26&cpage=1#comment-335 Inception « Nick Jamil’s blog Thu, 18 Dec 2008 23:12:26 +0000 http://www.lizblankenship.com/drproject/blog/?p=26#comment-335 [...] mentioned me in his blog a few times under the DrProject category. As did Liz Blankenship and my friend Kosta [...] [...] mentioned me in his blog a few times under the DrProject category. As did Liz Blankenship and my friend Kosta [...]

]]> Comment on Winding down… by The Third Bit » Blog Archive » Summer’s End http://www.lizblankenship.com/drproject/blog/?p=21&cpage=1#comment-131 The Third Bit » Blog Archive » Summer’s End Fri, 29 Aug 2008 14:04:37 +0000 http://www.lizblankenship.com/drproject/blog/?p=21#comment-131 [...] Liz Blankenship has been thinking about simplifying tickets (a mockup is available); she has also posted some musings about the divergent evolution of Trac and DrProject. [...] [...] Liz Blankenship has been thinking about simplifying tickets (a mockup is available); she has also posted some musings about the divergent evolution of Trac and DrProject. [...]

]]> Comment on To do list mockup by The Third Bit » Blog Archive » Summer’s End http://www.lizblankenship.com/drproject/blog/?p=26&cpage=1#comment-124 The Third Bit » Blog Archive » Summer’s End Tue, 26 Aug 2008 19:56:14 +0000 http://www.lizblankenship.com/drproject/blog/?p=26#comment-124 [...] Blankenship has been thinking about simplifying tickets (a mockup is available); she has also posted some musings about the divergent evolution of Trac and [...] [...] Blankenship has been thinking about simplifying tickets (a mockup is available); she has also posted some musings about the divergent evolution of Trac and [...]

]]> Comment on Simplifying Tickets by The Third Bit » Blog Archive » Summer’s End http://www.lizblankenship.com/drproject/blog/?p=19&cpage=1#comment-123 The Third Bit » Blog Archive » Summer’s End Tue, 26 Aug 2008 19:20:47 +0000 http://www.lizblankenship.com/drproject/blog/?p=19#comment-123 [...] Blankenship has been thinking about simplifying tickets (a mockup is available); she has also posted some musings about the divergent evolution of Trac and [...] [...] Blankenship has been thinking about simplifying tickets (a mockup is available); she has also posted some musings about the divergent evolution of Trac and [...]

]]> Comment on Winding down… by Ludo http://www.lizblankenship.com/drproject/blog/?p=21&cpage=1#comment-120 Ludo Tue, 26 Aug 2008 15:27:23 +0000 http://www.lizblankenship.com/drproject/blog/?p=21#comment-120 Hi, we have been using DrProject in our company (6 fulltimers, 15 partimers) in Slovakia for about 9 moths (after using Trac for about a year). Our experience are very very good ;-), as I sow your usability sugestions, if they are implemented, I am sure our experience will be even better ;-) You should push Greg to setup a blog for DrProject, so the development team effort and abilities are more visible! ;-) Take care Ludo Hi,

we have been using DrProject in our company (6 fulltimers, 15 partimers) in Slovakia for about 9 moths (after using Trac for about a year).

Our experience are very very good ;-) , as I sow your usability sugestions, if they are implemented, I am sure our experience will be even better ;-)

You should push Greg to setup a blog for DrProject, so the development team effort and abilities are more visible! ;-) Take care

Ludo

]]> Comment on About this project by Designing the DrProject User Experience » Winding down… http://www.lizblankenship.com/drproject/blog/?page_id=30&cpage=1#comment-119 Designing the DrProject User Experience » Winding down… Tue, 26 Aug 2008 14:55:44 +0000 http://www.lizblankenship.com/drproject/blog/?page_id=30#comment-119 [...] input in the future.  I’ve made up a page to summarize my efforts on this project under the About this project link in the blog navigation.  It’s mostly complete now though I’d like to add some [...] [...] input in the future.  I’ve made up a page to summarize my efforts on this project under the About this project link in the blog navigation.  It’s mostly complete now though I’d like to add some [...]

]]> Comment on Wiki page created by Liz http://www.lizblankenship.com/drproject/blog/?p=16&cpage=1#comment-36 Liz Sat, 02 Aug 2008 05:39:06 +0000 http://www.lizblankenship.com/drproject/blog/?p=16#comment-36 Haha, yeah, linear navigation is quite a change from what we're used to. :-) Luckily, most screen readers have a whole bunch of keyboard commands built in that help you move around. For instance, with WebAnywhere, try Ctrl-H to skip paste the whole top part of the page to the first actual heading. I would like if there were a way to skip paste chunks within the navigation though. That's where I think maybe tucking the items in a ul might help but I need to play with it first. Apparently the standard screen readers (which cost money and are better than this web one) have a way of saying that the page has been updated, but I don't think any of them can identify which part of the page has been updated in order to read just that part. (Though that really doesn't seem that hard... just compare the DOM tree? Hmm...) I read about a hack that lets you set the focus to an element that has tabindex set to -1 but I want to understand it better before I suggest using it. Thanks for the link, that's probably a better part of the site to link developers to than the part of that site I found earlier today. I'll add it to the wiki page. Haha, yeah, linear navigation is quite a change from what we’re used to. :-) Luckily, most screen readers have a whole bunch of keyboard commands built in that help you move around. For instance, with WebAnywhere, try Ctrl-H to skip paste the whole top part of the page to the first actual heading.

I would like if there were a way to skip paste chunks within the navigation though. That’s where I think maybe tucking the items in a ul might help but I need to play with it first.

Apparently the standard screen readers (which cost money and are better than this web one) have a way of saying that the page has been updated, but I don’t think any of them can identify which part of the page has been updated in order to read just that part. (Though that really doesn’t seem that hard… just compare the DOM tree? Hmm…) I read about a hack that lets you set the focus to an element that has tabindex set to -1 but I want to understand it better before I suggest using it.

Thanks for the link, that’s probably a better part of the site to link developers to than the part of that site I found earlier today. I’ll add it to the wiki page.

]]> Comment on Wiki page created by Jeff Balogh http://www.lizblankenship.com/drproject/blog/?p=16&cpage=1#comment-35 Jeff Balogh Sat, 02 Aug 2008 03:21:47 +0000 http://www.lizblankenship.com/drproject/blog/?p=16#comment-35 Wow, it takes *so long* to read a page that way! Even google.com takes forever; their nav bar at the top has a bunch of "hidden" items, which the reader picks up. So, it seems like there should be a way of chunking the page, making it easy for the screen reader to jump to a certain section. This is perhaps possible with link anchors, but there should be a better way, following the structure of the page. Once you've been through the whole page serially, you probably don't want to do that again. They probably haven't standardized this yet, but is there a way to notify the reader when the page is updated through javascript? Some sort of what's-new queue? You probably know most of this already, but one of the dojo a11y experts made a design requirements document at http://www.dojotoolkit.org/developer/A11yReq Wow, it takes *so long* to read a page that way! Even google.com takes forever; their nav bar at the top has a bunch of “hidden” items, which the reader picks up.

So, it seems like there should be a way of chunking the page, making it easy for the screen reader to jump to a certain section. This is perhaps possible with link anchors, but there should be a better way, following the structure of the page. Once you’ve been through the whole page serially, you probably don’t want to do that again.

They probably haven’t standardized this yet, but is there a way to notify the reader when the page is updated through javascript? Some sort of what’s-new queue?

You probably know most of this already, but one of the dojo a11y experts made a design requirements document at http://www.dojotoolkit.org/developer/A11yReq

]]> Comment on Design challenges by The Third Bit » Blog Archive » Home Stretch for Students http://www.lizblankenship.com/drproject/blog/?p=13&cpage=1#comment-26 The Third Bit » Blog Archive » Home Stretch for Students Mon, 28 Jul 2008 13:22:06 +0000 http://www.lizblankenship.com/drproject/blog/?p=13#comment-26 [...] Liz Blankenship (and the rest of the DrProject crew) is still working on the ‘All problem. [...] [...] Liz Blankenship (and the rest of the DrProject crew) is still working on the ‘All problem. [...]

]]> Comment on The past few weeks (productive blog neglect) by The Third Bit » Blog Archive » A Distributed Single Point of Failure http://www.lizblankenship.com/drproject/blog/?p=12&cpage=1#comment-17 The Third Bit » Blog Archive » A Distributed Single Point of Failure Sun, 20 Jul 2008 21:30:05 +0000 http://www.lizblankenship.com/drproject/blog/?p=12#comment-17 [...] Liz Blankenship has been busy. [...] [...] Liz Blankenship has been busy. [...]

]]>