Re: [xwiki-devs] [Brainstorming] Do we still want to be accessible without javascript

On 01/07/2014 09:28 AM, Guillaume "Louis-Marie" Delhumeau wrote: -1 (non binding since this isn't a vote). But it really depends on how do we see XWiki. If it's an enterprise application, then yes, we can drop support for accessibility. If it's a wiki, then -1, any wiki should be all-inclusive, as a content authoring tool; but that doesn't mean that EVERYTHING must work without scripts, just that at least basic navigation and content authoring should work even from a text-based or voice-based browser. Same answer if it's a generic web content authoring tool, not just a wiki. However, if it's a specific data entry tool with a specific target (i.e. a custom application for somebody's intranet), then it's up to the customer to decide if accessibility is a must. If it's a web application development framework, then it doesn't necessarily have to be accessible, although it would be better (anybody can write Java code in an accessible editor, why not XWiki code?), but the resulting application (and the navigation around it) may be required to be accessible. Anyway, asking the devs is pointless, we can write whatever kind of XWiki we want, but that doesn't mean that end users are going to be happy about it. The users are the ones that should voice their opinion. FWIW, in the past a few XWiki users did choose XWiki because it was accessible, and XWiki SAS did sign a contract for providing and maintaining XWiki accessible, where "accessible" is defined as "passing the Dutch webrichtlijnen validation". I don't know if that contract is still in effect or not. -- Sergiu Dumitriu http://purl.org/net/sergiu