Lee, that is a gross exaggeration of the usability problems faced by screen readers, as is your 'tekken / rock band' comment.
Developing the server-side code to handle sorting is beneficial in a number of ways. * You can sort over multiple pages, which then means any Javascript attached to the table can utilise sorted-pagination fluidly. * You can re-use all of the existing mechanisms for server-side sorting in your Javascript enhancements. * Adding the actual 'html' sorts is a simple case of a conditional in the template. * Adding filter methods is relatively easy to do with Javascript once the backend methods are taken care of. * And of course, any HTML ready device can utilise the non-Javascript methods. Javascript should only be used as an extended interface to the already- available methods of your application and data. Making websites 'gracefully degrade' is a convoluted and backward-thinking approach. Making websites 'beautifully extend' is something else altogether. If your making methods available for sorting, it's likely that you've also included searching and complex filtering as part of that process. This will allow you to render this filtered and sorted output in any format you choose. Be that HTML table (which is the best way to handle that type of information, without question), extended Javascript interface, or even Flash. Let the sever do the work where it is supposed to. I've got absolutely nothing against Javascript. I'm a keen Mootools user due to its more OO-based structure. I understand that people's schedules may not allow for such development, but it's usually much easier to develop server-side followed by the interface, rather than the other way around. Making your app work for JQuery will cost you dearly in the long run. (Apologies for the typos.. I'm writing with a tiny keyboard!) -CaMason On Jan 11, 7:15 pm, Lee Bolding <[email protected]> wrote: > On 11 Jan 2009, at 19:07, Thomas Dedericks wrote: > > > > >> If your concern truly is for disabled users, don't present the data > >> in > >> a table. > > > Lee, I disagree on that. If we're talking about tabular data (i mean a > > bunch of any kind of data where you can find what you need by > > looking at > > the intersection of the right row & the right column...) there's no > > better way to represent it than a well-written HTML table. > > Have you ever used a screen reader when it encounters a table? in no > way, shape or form is that usable. > > Accessible? yes. > > Usable? no. > > This is the tipping point where accessibility and usability hug and go > their separate ways, abandoning common sense as a common enemy. > > The OP was concerned with accessibility of a table for disabled users, > but making it accessible only creates a worse UX (for a disabled > user). It's like strapping a stick to your head and trying to play > Tekken with a Rock Band drum set. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
