[VOTE] Following Web Content Accessibility Guidelines (WCAG)

[vmassol]

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

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Marius Dumitru Florea]

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 .".

-0, I don't like at all the single-H1 constraint.

Marius

>
> 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
>
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Alex Jeannopoulos]

Sent from my iPhone

On Oct 28, 2009, at 5:24 PM, Marius Dumitru Florea <[hidden email]
 > wrote:

> 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 .".
>
> -0, I don't like at all the single-H1 constraint.
>
> Marius
>
>>
>> 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
>>
>> _______________________________________________
>> devs mailing list
>> [hidden email]
>> http://lists.xwiki.org/mailman/listinfo/devs
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[vmassol]

Hi Marius,

On Oct 28, 2009, at 10:24 PM, Marius Dumitru Florea wrote:

> 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 .".
>
> -0, I don't like at all the single-H1 constraint.

I've re-read what they say about it and the reason is simply to forbid  
skipping levels which we agree about. In our case we haven't skipped  
any level so I believe we are fine. We could also imagine a document  
with 2 columns and each column having a H1 title. Thus I believe there  
are cases when it's valid.

In addition they say:

- "It is advisable not to skip any levels in the heading hierarchy..."
- "From a practical point of view, the decision was taken for this  
manual to discourage skipping levels, but not forbid it outright."

So my readind is that we can keep our H1 as they are and still be  
compliant.


Marius and others, could you review the guidelines at http://www.webrichtlijnen.nl/english/guidelines/ 
  and let us know which rules you agree with and which you don't?

Thanks
-Vincent

>> 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
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Marius Dumitru Florea]

Vincent Massol wrote:

> Hi Marius,
>
> On Oct 28, 2009, at 10:24 PM, Marius Dumitru Florea wrote:
>
>> 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 .".
>> -0, I don't like at all the single-H1 constraint.
>
> I've re-read what they say about it and the reason is simply to forbid  
> skipping levels which we agree about. In our case we haven't skipped  
> any level so I believe we are fine. We could also imagine a document  
> with 2 columns and each column having a H1 title. Thus I believe there  
> are cases when it's valid.
>
> In addition they say:
>
> - "It is advisable not to skip any levels in the heading hierarchy..."
> - "From a practical point of view, the decision was taken for this  
> manual to discourage skipping levels, but not forbid it outright."
>
> So my readind is that we can keep our H1 as they are and still be  
> compliant.
>
>
> Marius and others, could you review the guidelines at http://www.webrichtlijnen.nl/english/guidelines/ 
>   and let us know which rules you agree with and which you don't?

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.

The rest of the rules are good IMO.

Thanks,
Marius

>
> Thanks
> -Vincent
>
>>> 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
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Sergiu Dumitriu-2]

On 10/29/2009 09:32 PM, Marius Dumitru Florea wrote:
> 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.

Yes, it does apply, but the WYSIWYG is a complex editing mode, a rich
alternative for the basic wiki editor, so we're covered.

> 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.

The current position of the language links is not good anyway, so when
we'll find a good position for them, we should also keep this in mind.

--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[vmassol]

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
>

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Denis Gervalle]

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

For those who are afraid to limit your ability to develop cool stuffs,  
I would remind that complying with the rules mainly means providing an  
accessible solutions to all parts and functions of site (as much as  
possible), but does not refrain you to provide an event better and  
more enjoyable solution to non-disabled peoples. This also means,  
using the coolest and latest web standards to ensure that !

As a contributor, here is my big +1 :)

Denis

On Oct 28, 2009, at 20:41, 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
>
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Guillaume Lerouge]

Hi,

On Mon, Nov 2, 2009 at 10:41 AM, Vincent Massol <[hidden email]> 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
>

I'm +1 too.

By the way, I've been playing around with XWiki and Lynx over the weekend
and the result is pretty much ok both in view and in wiki edition mode (I
was able to edit and save a page easily). There's a lot of "menu" clutter at
the top of the page though :-)

Anyway, the experiment with a text-based web browser leads me to think that
following the guidelines and creating an accessible tool will also lead us
to create a leaner solution: when looking at the wiki as text-only, plenty
of ideas on how to improve it spring to mind.

Guillaume

PS: Sergiu, if you know how to add a line between 2 written lines in a
TextArea in Lynx I'd like to learn about it: so far when hitting 'Return' at
the end of a line the cursor goes to the next line but does not add a new
line between my 2 existing lines


> > Thanks
> > -Vincent
> >
>
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs
>



--
Guillaume Lerouge
Product Manager - XWiki SAS
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[tmortagne]

On Mon, Nov 2, 2009 at 10:41, Vincent Massol <[hidden email]> 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

+1 to follow accessibility standards by default and then see what we
can do for the specific use cases reported

>
> 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
>>
>
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs
>

--
Thomas Mortagne
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Marius Dumitru Florea]

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'm +1 now.

Thanks,
Marius

>
> 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
>>
>
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Anca Luca]

+1

Anca

On 11/02/2009 11: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
>>
>
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Sergiu Dumitriu-2]

On 11/02/2009 10:45 AM, Denis Gervalle wrote:

> 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

We'd really appreciate some patches.

--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Ecaterina Valica-2]

+1

On Mon, Nov 2, 2009 at 14:22, Sergiu Dumitriu <[hidden email]> wrote:

> On 11/02/2009 10:45 AM, Denis Gervalle wrote:
> > 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
>
> We'd really appreciate some patches.
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs
>

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Sergiu Dumitriu-2]

On 11/02/2009 10:51 AM, Guillaume Lerouge wrote:
> PS: Sergiu, if you know how to add a line between 2 written lines in a
> TextArea in Lynx I'd like to learn about it: so far when hitting 'Return' at
> the end of a line the cursor goes to the next line but does not add a new
> line between my 2 existing lines

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
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Guillaume Lerouge]

Hi,

On Mon, Nov 2, 2009 at 3:56 PM, Sergiu Dumitriu <[hidden email]> wrote:

> On 11/02/2009 10:51 AM, Guillaume Lerouge wrote:
> > PS: Sergiu, if you know how to add a line between 2 written lines in a
> > TextArea in Lynx I'd like to learn about it: so far when hitting 'Return'
> at
> > the end of a line the cursor goes to the next line but does not add a new
> > line between my 2 existing lines
>
> 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.
>

Yep, that's what Fabio told me to do.

Thanks,
Guillaume

--
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
> _______________________________________________
> devs mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/devs
>



--
Guillaume Lerouge
Product Manager - XWiki SAS
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[vmassol]

Ok the vote is passed.

I'm sarting to work on it:
- 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
- I'll flag issues with the "wcag" keyword in jira

However for the implementation work (ie fixing the jira issues) I'll  
need all devs' help.

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
>>
>

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[vmassol]

On Nov 4, 2009, at 1:41 PM, Vincent Massol wrote:

> Ok the vote is passed.
>
> I'm sarting to work on it:
> - 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
> - I'll flag issues with the "wcag" keyword in jira
>
> However for the implementation work (ie fixing the jira issues) I'll  
> need all devs' help.

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
>>>
>>
>

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[Sergiu Dumitriu-2]

On 11/04/2009 03:09 PM, Vincent Massol wrote:

>
> On Nov 4, 2009, at 1:41 PM, Vincent Massol wrote:
>
>> Ok the vote is passed.
>>
>> I'm sarting to work on it:
>> - 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
>> - I'll flag issues with the "wcag" keyword in jira
>>
>> However for the implementation work (ie fixing the jira issues) I'll
>> need all devs' help.
>
> 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

We should also follow the ATAG guidelines:
http://www.w3.org/WAI/intro/atag.php

> - 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
>>>>

--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs

[vmassol]

On Nov 5, 2009, at 2:10 PM, Sergiu Dumitriu wrote:

> On 11/04/2009 03:09 PM, Vincent Massol wrote:
>>
>> On Nov 4, 2009, at 1:41 PM, Vincent Massol wrote:
>>
>>> Ok the vote is passed.
>>>
>>> I'm sarting to work on it:
>>> - 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
>>> - I'll flag issues with the "wcag" keyword in jira
>>>
>>> However for the implementation work (ie fixing the jira issues) I'll
>>> need all devs' help.
>>
>> 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
>
> We should also follow the ATAG guidelines:
> http://www.w3.org/WAI/intro/atag.php

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

_______________________________________________
devs mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/devs