On Wednesday 7. May 2014 20.41.55 Brendan wrote: > On 14-05-07 11:24 AM, Thomas Bruederli wrote: > > I found it particularly hard to apply the recommendations from WCAG to > > Roundcube because it's more an application than a website providing > > contents. But I assume that's where ARIA is meant to jump in. And > > here's my first question: are there tools available that actually > > implement these standards and actually make sense of all these aria-* > > attributes? > > does it make much sense to even do this for roundcube?
Yes. > i assume that the guidelines mostly relate to websites because they are > information repositories and it's important for the information on them to > be accessible. but as you say, roundcube is more an application than a > repository (IMAP being the true repository) - it seems like anyone with > sight problems would be using an imap client designed specifically for > that purpose and not trying to use a webmail client at all. I'll let people with stronger opinions about accessibility speak for themselves, but one thing I was told by someone with a far greater depth of knowledge and experience on this topic than me was that people with greater accessibility demands than those of the average user do actually want to use the same applications as everybody else, or at least many of them do. Another concern is that accessibility is used as an argument against Roundcube in cases of procurement, especially in public organisations. I briefly investigated this last year and found various things that might be improved, but at the same time it did seem like the various JavaScript libraries used by Roundcube do support various ARIA annotations. (I can dig out my list of findings, though.) I recently learned that various supposed accessibility deficiencies in Roundcube were eventually no longer a concern for one organisation whose procurement practices I had been tracking, but it appears that the uncertainty was sufficient to use as an excuse to migrate webmail (and indeed the entire e-mail infrastructure) to something else. Having a strong accessibility reputation would be beneficial for Roundcube not just because it would ensure the solution's usability for the maximum number of potential end-users, but also because it would undermine the kind of whisper campaign that somehow manages to get it disqualified in favour of all- in-one proprietary systems in organisations like the one mentioned above. Such disqualifications and exclusions undermine both Roundcube adoption - not nice if you prefer Roundcube to other webmail solutions - as well as Free Software and open standards adoption, ultimately threatening the viability of those things and of Roundcube itself. Sorry for the lengthy and slightly tangential response, but I strongly feel that sometimes the best way to counter the kind of misinformation that is spread when there is money to be made by aggressive proprietary software vendors - at the expense of great software like Roundcube (and often at the expense of users and taxpayers) - is to be able to demonstrate a robust and complete solution that can be shown to fully address all areas of potential concern. Accessibility is one of those areas. Paul _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
