Colour-coding creates accessibility issues, not only for those who are using screen readers but for those who are colour-blind or who simply cannot process certain types of colours - plus, hard-coding a colour to note this would not work well with custom journal colours or layouts. There would need to be some other, more accessible way to mark it. (I like the basic idea, for sure, but this particular implementation seems problematic.)
I, too, would love to be able to collapse posts, but I'm wondering how long the collapse would persist - until navigating away from the page? Until logout? Until closing the browser? Lassarina Aoibhell Webmaster, The RPG Place http://www.rpgplace.net On Thu, Apr 16, 2009 at 2:43 PM, Ronja Verrine <[email protected]>wrote: > I think collapse/expand on all individual posts on the reading page, with > the ability to set some posts to be auto-collapsed by tag or number of > characters is the best solution. If such functionality existed, I wouldn't > just be using it to hide things I don't want to read, I'd use it to hide > things I've already read, to make it easier to see where I am on the page. > > If it would be possible to color-code for the reason (as in the > auto-collapsed posts tagged "twitter" showing up in, say, orange while the > X number of characters ones show up in green and the ones I've collapsed > myself in black), that would be even better. > > Now if it could be used to collapse all posts by a specific *user* > automatically, I would love dw forever. I'm thinking of communities here, > not subscriptions to individual journals. I've been in enough communities > that have one irritating poster while everyone else is fine to want this > feature. > > But seriously, the most important/desired thing for me is the ability to > collapse posts on the reading page myself, with or without auto-collapsing. > I *would* be willing to pay for the other, more complicated stuff, though. > > On Thu, Apr 16, 2009 at 4:06 PM, <[email protected]> wrote: > >> >> Instead of having to rely on userscripts, DW could give users the option >> to: >> >> -collapse (or cut) loudtwitter >> -collapse the content in posts that are over X number of characters - >> maybe not collapse ALL the content, but just those than go over the limit >> - so people aren't forced to scroll for multiple screens. >> >> That way if people *are* interested, they click the expand and read >> without reloading and without blocking the actual content - and since they >> opted into it, I don't see how it could be regarded as censorship >_> >> >> g >> >> _______________________________________________ >> dw-discuss mailing list >> [email protected] >> http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss >> > > > _______________________________________________ > dw-discuss mailing list > [email protected] > http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss >
_______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
