[xwiki-devs] WCAG 1.0 status + Need help
Hi, Here's a status of the past few days I have spent looking at fixing our pages so that we pass the WCAG 1.0 tests (the automated part of it). * I've fixed the home page so no more issues in it * I've tested the other pages using http://www.tawdis.net/ingles.html?lang=en and here's the results: - priority 1: only 2 issues - priority 2: about 162 * 7 = 1134 issues - priority 3: about 120 issues That's quite a lot but they are easy to fix. Most of them are about: - tables missing summary attributes - associate labels with <input> (using a <for>) In order to reproduce it's very easy. Use this link to run TAW: http://www.tawdis.net/taw3/descargas/jws/es/taw3.jnlp Then run XE locally and feed it to TAW. I need help to fix all these remaining issues. Who can help me? Thanks -Vincent Note that the Dutch guidelines add a bit more to WCAG 1.0 but not much and passing WCAG is already a good first step.
On Nov 12, 2009, at 12:13 PM, Vincent Massol wrote:
Hi,
Here's a status of the past few days I have spent looking at fixing our pages so that we pass the WCAG 1.0 tests (the automated part of it).
* I've fixed the home page so no more issues in it * I've tested the other pages using http://www.tawdis.net/ingles.html?lang=en and here's the results: - priority 1: only 2 issues - priority 2: about 162 * 7 = 1134 issues - priority 3: about 120 issues
That's quite a lot but they are easy to fix. Most of them are about: - tables missing summary attributes - associate labels with <input> (using a <for>)
In order to reproduce it's very easy. Use this link to run TAW: http://www.tawdis.net/taw3/descargas/jws/es/taw3.jnlp
Nice tutorial about using the tool: http://www.ariadne.ac.uk/issue46/lauke/ -Vincent
Then run XE locally and feed it to TAW.
I need help to fix all these remaining issues.
Who can help me?
Thanks -Vincent
Note that the Dutch guidelines add a bit more to WCAG 1.0 but not much and passing WCAG is already a good first step.
Hi Vincent,
- associate labels with <input> (using a <for>)
I have an old patch for this in the object model, its partial and unfortunatly, it is also mixed with another patch regarding the displaySearch() and query functionality that initially exists on object fields. Is there alrealy a jira issue for this or should I create one to add this patch that you will decide if it is worth it or not ? Denis
Hi Denis, On Nov 12, 2009, at 1:36 PM, Denis Gervalle wrote:
Hi Vincent,
- associate labels with <input> (using a <for>)
I have an old patch for this in the object model, its partial and unfortunatly, it is also mixed with another patch regarding the displaySearch() and query functionality that initially exists on object fields.
Is there alrealy a jira issue for this or should I create one to add this patch that you will decide if it is worth it or not ?
There's no jira yet, please create one (flag it with the "wcag" keyword). Thanks -Vincent
On Nov 12, 2009, at 12:13 PM, Vincent Massol wrote:
Hi,
Here's a status of the past few days I have spent looking at fixing our pages so that we pass the WCAG 1.0 tests (the automated part of it).
* I've fixed the home page so no more issues in it
And when I thought we were done with the home page, I've found a new tool that reports 79 important problems.... Basically there are 3 categories of problems remaining: 1) using noscript as alternative to <script> - level 1 pb 2) bad resizing behavior (like fixed character size or fixed space between lines instead of relative values) - level 2 pb 3) colors too close to each other for people affected by cataract, protanopia, deuteranopia or tritanopia. For ex it says: "There is insufficient contrast between the text color (#4d4d4d) and the background color (#005a83)." (to see the color: http://www.colorcombos.com/combotester.html?color0=005B9A&color1=0191C8&&sho... ) For 3) I think we could provide special color themes. We'd need for a user to be able to define the theme to use though (instead of it being only a global option). The tool that I've used to find these is: http://www.fujitsu.com/global/accessibility/assistance/wi/ Help is welcome... I especially need help for 2) in order to modify our colibri CSS so that text resizes work in the browser. Thanks -Vincent
* I've tested the other pages using http://www.tawdis.net/ingles.html?lang=en and here's the results: - priority 1: only 2 issues - priority 2: about 162 * 7 = 1134 issues - priority 3: about 120 issues
That's quite a lot but they are easy to fix. Most of them are about: - tables missing summary attributes - associate labels with <input> (using a <for>)
In order to reproduce it's very easy. Use this link to run TAW: http://www.tawdis.net/taw3/descargas/jws/es/taw3.jnlp
Then run XE locally and feed it to TAW.
I need help to fix all these remaining issues.
Who can help me?
Thanks -Vincent
Note that the Dutch guidelines add a bit more to WCAG 1.0 but not much and passing WCAG is already a good first step.
participants (2)
-
Denis Gervalle -
Vincent Massol