Re: First look at www.openoffice.org accesibility

2014-01-22 Thread Marcus (OOo)
[Top post to give you the latest update] I've done fixed on the homepage [1] and download webpage [2]. The remaining things to fix are a missing title in the search box (top right) and the missing lang ID. Both applies to the entire website and not only to the both. To be continued ... [1]

Re: First look at www.openoffice.org accesibility

2014-01-22 Thread Marcus (OOo)
Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Rob Weir To: "dev@openoffice.apache.org" Sent: Tuesday, January 21, 2014 1:39 PM Subject: Re: First look at www.openoffice.org acces

Re: First look at www.openoffice.org accesibility

2014-01-22 Thread Marcus (OOo)
to do. ;-) Marcus From: Rob Weir To: "dev@openoffice.apache.org" Sent: Tuesday, January 21, 2014 1:39 PM Subject: Re: First look at www.openoffice.org accesibility On Tue, Jan 21, 2014 at 4:09 PM, Marcus (OOo) wrote: In the meantime it's already

Re: First look at www.openoffice.org accesibility

2014-01-21 Thread Rob Weir
Nancy Web Design > Free 24 hour pass to lynda.com. > Video courses on SEO, CMS, > Design and Software Courses > > > > > > From: Rob Weir > To: "dev@openoffice.apache.org" > Sent: Tuesday, January 21, 2014 1:39 PM

Re: First look at www.openoffice.org accesibility

2014-01-21 Thread Nancy K
"dev@openoffice.apache.org" Sent: Tuesday, January 21, 2014 1:39 PM Subject: Re: First look at www.openoffice.org accesibility On Tue, Jan 21, 2014 at 4:09 PM, Marcus (OOo) wrote: > > > In the meantime it's already online on www.oo.o. I've added a h1 tag and > fixed the double-lin

Re: First look at www.openoffice.org accesibility

2014-01-21 Thread Rob Weir
On Tue, Jan 21, 2014 at 4:09 PM, Marcus (OOo) wrote: > > > In the meantime it's already online on www.oo.o. I've added a h1 tag and > fixed the double-link problem. > > @Rob: > Please can you test if this is now OK in the screen reader? > > Thanks > > Here's the tool I used to check: http://wav

Re: First look at www.openoffice.org accesibility

2014-01-21 Thread Marcus (OOo)
Am 01/19/2014 01:43 AM, schrieb Marcus (OOo): Am 01/16/2014 12:17 AM, schrieb Dave Fisher: On Jan 14, 2014, at 3:03 PM, Marcus (OOo) wrote: Am 01/14/2014 06:53 PM, schrieb Rob Weir: On Mon, Jan 13, 2014 at 4:09 PM, Marcus (OOo) wrote: Am 01/13/2014 07:52 PM, schrieb Rob Weir: I've been sc

Re: First look at www.openoffice.org accesibility

2014-01-18 Thread Marcus (OOo)
Am 01/16/2014 12:17 AM, schrieb Dave Fisher: On Jan 14, 2014, at 3:03 PM, Marcus (OOo) wrote: Am 01/14/2014 06:53 PM, schrieb Rob Weir: On Mon, Jan 13, 2014 at 4:09 PM, Marcus (OOo) wrote: Am 01/13/2014 07:52 PM, schrieb Rob Weir: I've been scanning pages on our website to see what kinds

Re: First look at www.openoffice.org accesibility

2014-01-18 Thread Marcus (OOo)
Am 01/16/2014 04:22 PM, schrieb Rob Weir: On Wed, Jan 15, 2014 at 6:17 PM, Dave Fisher wrote: . . . This can be done by updating the ssi setup Add to all ssi.mdtext files a language property Here is /fr/ssi.mdtext language: fr doctype: /doctype.html brand: /fr/brand.html footer: /footer

Re: First look at www.openoffice.org accesibility

2014-01-16 Thread Rob Weir
On Wed, Jan 15, 2014 at 6:17 PM, Dave Fisher wrote: > . . . > > This can be done by updating the ssi setup > > Add to all ssi.mdtext files a language property > > Here is /fr/ssi.mdtext > language: fr > doctype: /doctype.html > brand: /fr/brand.html > footer: /footer.html > topnav: /fr/topnav.ht

Re: First look at www.openoffice.org accesibility

2014-01-15 Thread Dave Fisher
On Jan 14, 2014, at 3:03 PM, Marcus (OOo) wrote: > Am 01/14/2014 06:53 PM, schrieb Rob Weir: >> On Mon, Jan 13, 2014 at 4:09 PM, Marcus (OOo) wrote: >>> Am 01/13/2014 07:52 PM, schrieb Rob Weir: >>> I've been scanning pages on our website to see what kinds of A11Y issues we should tak

Re: First look at www.openoffice.org accesibility

2014-01-14 Thread Marcus (OOo)
Am 01/14/2014 06:53 PM, schrieb Rob Weir: On Mon, Jan 13, 2014 at 4:09 PM, Marcus (OOo) wrote: Am 01/13/2014 07:52 PM, schrieb Rob Weir: I've been scanning pages on our website to see what kinds of A11Y issues we should take care off. I'm concentrated initially on issues on our most popular

Re: First look at www.openoffice.org accesibility

2014-01-14 Thread Kay Schenk
On Tue, Jan 14, 2014 at 9:53 AM, Rob Weir wrote: > On Mon, Jan 13, 2014 at 4:09 PM, Marcus (OOo) > wrote: > > Am 01/13/2014 07:52 PM, schrieb Rob Weir: > > > >> I've been scanning pages on our website to see what kinds of A11Y > >> issues we should take care off. I'm concentrated initially on

Re: First look at www.openoffice.org accesibility

2014-01-14 Thread Rob Weir
On Mon, Jan 13, 2014 at 4:09 PM, Marcus (OOo) wrote: > Am 01/13/2014 07:52 PM, schrieb Rob Weir: > >> I've been scanning pages on our website to see what kinds of A11Y >> issues we should take care off. I'm concentrated initially on issues >> on our most popular pages as well as issues on the te

Re: First look at www.openoffice.org accesibility

2014-01-13 Thread Louis Suárez-Potts
On 13-Jan-2014, at 13:52, Rob Weir wrote: > I'll continue investigating, but that is what I've found initially. > If anyone has ideas for these items, please let me know. Thanks, Rob. Don't we have any A11Y experts on this list or in the project? I can ask some acquaintances who were involved

Re: First look at www.openoffice.org accesibility

2014-01-13 Thread Marcus (OOo)
Am 01/13/2014 07:52 PM, schrieb Rob Weir: I've been scanning pages on our website to see what kinds of A11Y issues we should take care off. I'm concentrated initially on issues on our most popular pages as well as issues on the template, since the template generates the repeated headers/footers

First look at www.openoffice.org accesibility

2014-01-13 Thread Rob Weir
I've been scanning pages on our website to see what kinds of A11Y issues we should take care off. I'm concentrated initially on issues on our most popular pages as well as issues on the template, since the template generates the repeated headers/footers nad navigation on every page. We'll get m