Vincent Massol wrote: -0, I don't like at all the single-H1 constraint.

> Before going further I'd like to ensure that we all agree to follow > these guidelines and put in our best practices (and ensure we verify > with some automated tests later on). > Here's my +1 > Thanks > -Vincent

Guideline R-pd.12.1: Do not use frames on websites. This applies to regular frames in framesets as well as well as iframes. Does this rule apply in edit mode? For various technical reasons the WYSIWYG editor has to use an iframe to load the edited document.

Guideline R-pd.15.3: Use fully written-out (textual) links to the language versions. I'm not sure how can we display ergonomically a large number of translations for a wiki page using the full language name.

Hi devs, Can I get some votes on whether we want to do this or not? So far I've only received a -0 from Marius but on a specific item and not in general. I'd like that we start working on this ASAP by doing the following: - Execute the tests on XE pages - Creating discrete jira issues whenever there are problems on pages, small enough so that they can be tackled one by one - Start fixing the issues Thanks -Vincent On Oct 28, 2009, at 8:41 PM, Vincent Massol wrote:

_______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On 11/02/2009 10:51 AM, Guillaume Lerouge wrote: at Normally I use links instead of lynx, which doesn't have this problem. The only way I managed to make it work is by starting it with -editor=vim, then press Ctrl+X E to open the textarea in the external editor.

Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, Can I get some votes on whether we want to do this or not? So far I've only received a -0 from Marius but on a specific item and not in general.

I'd like that we start working on this ASAP by doing the following: - Execute the tests on XE pages - Creating discrete jira issues whenever there are problems on pages, small enough so that they can be tackled one by one - Start fixing the issues Thanks -Vincent On Oct 28, 2009, at 8:41 PM, Vincent Massol wrote: _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, Can I get some votes on whether we want to do this or not? So far I've only received a -0 from Marius but on a specific item and not in general. I'd like that we start working on this ASAP by doing the following: - Execute the tests on XE pages - Creating discrete jira issues whenever there are problems on pages, small enough so that they can be tackled one by one - Start fixing the issues Thanks -Vincent On Oct 28, 2009, at 8:41 PM, Vincent Massol wrote:

On Nov 4, 2009, at 1:41 PM, Vincent Massol wrote: I've started documenting our rules (what we've agreed at so far - will keep adding as we agree on rules) at: - http://dev.xwiki.org/xwiki/bin/view/Community/XhtmlCssCodeStyle

- http://dev.xwiki.org/xwiki/bin/view/Community/Testing Thanks -Vincent > On Nov 2, 2009, at 10:41 AM, Vincent Massol wrote: > >> Hi devs, >> >> Can I get some votes on whether we want to do this or not? >> >> So far I've only received a -0 from Marius but on a specific item >> and not in general. >> >> I'd like that we start working on this ASAP by doing the following: >> - Execute the tests on XE pages >> - Creating discrete jira issues whenever there are problems on >> pages, small enough so that they can be tackled one by one >> - Start fixing the issues >> >> Thanks >> -Vincent >> >> On Oct 28, 2009, at 8:41 PM, Vincent Massol wrote: >> >>> Hi devs, >>> >>> We've always tried to follow standards in the XWiki project. I'd >>> like to propose that we start adhering to the WCAG ones to make >>> XWiki even more accessible. >>> >>> The reason I'm proposing this is because XWiki SAS has been >>> contacted by some Dutch organization promoting the usage of >>> standards in Netherlands and they're interested in using XWiki for >>> their site. As such they need that the wiki they use also follows >>> the guidelines... They've found XWiki since it was one of the >>> wikis out there that follows most closely the guidelines. >>> >>> This is our opportunity to meet the WCAG guidelines and go even >>> beyond (since the Dutch guidelines go slightly further I believe, >>> see http://www.webrichtlijnen.nl/english/guidelines/). We would be >>> the first wiki to meet this! >>> >>> If we agree we'll need to find some ways to automate the execution >>> of the verifications. Right now we can test pages using this >>> validator: >>> http://www.webrichtlijnen.nl/english/test/ >>> >>> I've started verifying this page: >>> http://playground.xwiki.org/xwiki/bin/view/Main/ >>> >>> Result: >>> http://www.webrichtlijnen.nl/english/test/report/74721/179372/ >>> >>> >>> Some examples of failing stuff: >>> >>> 1) Style attribute forbidden. Everything from CSS. >>> >>> Ex from home page: >>> <div id="globallinks"> <form action="/xwiki/bin/view/Main/ >>> WebSearch" style="margin: 0; padding: 0;"> <div id="globalsearch"> >>> <input id="globalsearchinput" type="text" name="text" >>> value="search..." size="15" class="withTip"/><input class="button" >>> value="Go" type="image" src="/xwiki/resources/icons/xwiki/ >>> search.png"/> </div> </form> </div> >>> ... >>> <div class="hidden" id="spSpaceCreateForm"><form action="/xwiki/ >>> bin/view/Main/?xpage=create" method="post"> <div> <input >>> name="tocreate" type="hidden" value="space"></input> <input >>> class="panelinput" name="title" onblur="if(this.value=='') >>> this.value='Space name'" onfocus="if(this.value=='Space name') >>> this.value=''" style="margin:auto;" type="text" value="Space >>> name"></input> <input type="submit" value="Create"></input> </div> >>> </form> </div> >>> ... >>> <p style="font-size:0.75em;padding-left:8px;"><a href="/xwiki/bin/ >>> inline/Panels/QuickLinks">(Edit this panel)</a></p> >>> >>> 2) Need to run CSS Level 2.1 validation. Lots of error. For ex on >>> home page: http://bit.ly/4x9YlM >>> 3) Apparently we made a mistake by choosing to have 2 H1 (one for >>> title and for headers). "The document hierarchy contains more that >>> one h1 tags .". >>> >>> Before going further I'd like to ensure that we all agree to >>> follow these guidelines and put in our best practices (and ensure >>> we verify with some automated tests later on). >>> Here's my +1 >>> Thanks >>> -Vincent >>>

On Nov 5, 2009, at 2:10 PM, Sergiu Dumitriu wrote: I think we should focus on WCAG first and look at this later on so that we have a chance of finishing something :) Re WCAG I've found this other checker: http://achecker.ca/checker/index.php

Seems like it's giving some different result than the Dutch Guidelines checker (it allows to test against WCAG 1.0 and 2.0 and with the different levels). Still haven't found a java source for automated WCAG tests though. Still looking... -Vincent >> - http://dev.xwiki.org/xwiki/bin/view/Community/Testing >> >> Thanks >> -Vincent >> >>> On Nov 2, 2009, at 10:41 AM, Vincent Massol wrote: >>> >>>> Hi devs, >>>> >>>> Can I get some votes on whether we want to do this or not? >>>> >>>> So far I've only received a -0 from Marius but on a specific item >>>> and not in general. >>>> >>>> I'd like that we start working on this ASAP by doing the >>>> following: >>>> - Execute the tests on XE pages >>>> - Creating discrete jira issues whenever there are problems on >>>> pages, small enough so that they can be tackled one by one >>>> - Start fixing the issues >>>> >>>> Thanks >>>> -Vincent >>>> >>>> On Oct 28, 2009, at 8:41 PM, Vincent Massol wrote: >>>> >>>>> Hi devs, >>>>> >>>>> We've always tried to follow standards in the XWiki project. I'd >>>>> like to propose that we start adhering to the WCAG ones to make >>>>> XWiki even more accessible. >>>>> >>>>> The reason I'm proposing this is because XWiki SAS has been >>>>> contacted by some Dutch organization promoting the usage of >>>>> standards in Netherlands and they're interested in using XWiki >>>>> for >>>>> their site. As such they need that the wiki they use also follows >>>>> the guidelines... They've found XWiki since it was one of the >>>>> wikis out there that follows most closely the guidelines. >>>>> >>>>> This is our opportunity to meet the WCAG guidelines and go even >>>>> beyond (since the Dutch guidelines go slightly further I believe, >>>>> see http://www.webrichtlijnen.nl/english/guidelines/). We would >>>>> be >>>>> the first wiki to meet this! >>>>> >>>>> If we agree we'll need to find some ways to automate the >>>>> execution >>>>> of the verifications. Right now we can test pages using this >>>>> validator: >>>>> http://www.webrichtlijnen.nl/english/test/ >>>>> >>>>> I've started verifying this page: >>>>> http://playground.xwiki.org/xwiki/bin/view/Main/ >>>>> >>>>> Result: >>>>> http://www.webrichtlijnen.nl/english/test/report/74721/179372/ >>>>> >>>>> >>>>> Some examples of failing stuff: >>>>> >>>>> 1) Style attribute forbidden. Everything from CSS. >>>>> >>>>> Ex from home page: >>>>> <div id="globallinks"> <form action="/xwiki/bin/view/Main/ >>>>> WebSearch" style="margin: 0; padding: 0;"> <div >>>>> id="globalsearch"> >>>>> <input id="globalsearchinput" type="text" name="text" >>>>> value="search..." size="15" class="withTip"/><input >>>>> class="button" >>>>> value="Go" type="image" src="/xwiki/resources/icons/xwiki/ >>>>> search.png"/> </div> </form> </div> >>>>> ... >>>>> <div class="hidden" id="spSpaceCreateForm"><form action="/xwiki/ >>>>> bin/view/Main/?xpage=create" method="post"> <div> <input >>>>> name="tocreate" type="hidden" value="space"></input> <input >>>>> class="panelinput" name="title" onblur="if(this.value=='') >>>>> this.value='Space name'" onfocus="if(this.value=='Space name') >>>>> this.value=''" style="margin:auto;" type="text" value="Space >>>>> name"></input> <input type="submit" value="Create"></input> </ >>>>> div> >>>>> </form> </div> >>>>> ... >>>>> <p style="font-size:0.75em;padding-left:8px;"><a href="/xwiki/ >>>>> bin/ >>>>> inline/Panels/QuickLinks">(Edit this panel)</a></p> >>>>> >>>>> 2) Need to run CSS Level 2.1 validation. Lots of error. For ex on >>>>> home page: http://bit.ly/4x9YlM >>>>> 3) Apparently we made a mistake by choosing to have 2 H1 (one for >>>>> title and for headers). "The document hierarchy contains more >>>>> that >>>>> one h1 tags .". >>>>> >>>>> Before going further I'd like to ensure that we all agree to >>>>> follow these guidelines and put in our best practices (and ensure >>>>> we verify with some automated tests later on). >>>>> Here's my +1 >>>>> Thanks >>>>> -Vincent

Hi Vincent, This would be for us a real improvement since we had already hack XWiki to have it more accessible than it was for a previous client, and we will audit and improve that effort soon, when we will upgrade that client to your latest release (or at least 1.9 depending on timeframe). The fields that we have worked on is improving navigation of a page without style, ensuring as best as we could proper reading of the page by readers for disabled peoples. Mostly, this had required a patch in the way object fields are displayed, and many small adjustment in the velocity templates (using a custom skin and some direct patch). Of course, we have not produced a full XWiki compliant solution, but the public part of our site is known to be accessible. You can see it there: http://elsaccessible.com