Re: [Self-platform-dev] address@hidden: accessibility querks]

[krishnakant Mane]

hi wouter.
your ideas exactly match mine only thing is that you gave a couple of
more dynamic ideas which I indeed had but was not able to build up
proper examples.
I will be back to lab by day after tomorrow evening and I will sit
with some sited assistant to manage this.
I have been doing a hard check on the accessibility features and
rajive, bipin etc. have tried their level best to keep it as
acccessible as possible.
only thing is that we have broken some pone accessibility features in
the process.
actually I too looked in the html that gets generated and my
observations were the same and I infered the same static information.
I am building up some dummi pages which I will confirm with our sited
counterparts.
happy hacking.
Krishnakant.
regards.
Krishnakant

On 28/04/2008, Wouter Tebbens <address@hidden> wrote:
> Nagarjuna G wrote:
> > ----- Forwarded message from krishnakant Mane <address@hidden> -----
> > hello nagarjun,
> > 2, structured accessibility already present in plone is not available
> > on self.  this implies that most of the blocks of information on a
> > page is divided into headings of varying levels.  collection, content,
> > course etc would be easy to locate given they are indicated by heading
> > 1/3.  just like "you are here " phrase typicle in a plone based
> > portal, other things can be made into headings.
> Yes indeed, that is what is called also the "breadcrumb" (from Hansel
> and Gretl...) to see easily where you are, and it privides a direct link
> to get up to higher levels. Question is then how we want to construct
> the breadcrumb. One way would be:
> home > collection1 > course2 > chapter3
> problem: a course like course1 could be in more than one collection,
> which makes the choice for presenting "collection1" an arbitrary choice.
> How would we solve this?
>
> > 3, it seams that screen reader does not get any thing out of the title
> > bar due to no <title> </title> tag in the pages.
> I agree, the title-tag should present meaningful data. I agree with KK
> that it should present more than "SELF Platform", and also include the
> collection title, course title or whatever view the user is looking at.
>
> e.g. <title>SELF Platform | Collection1 - Course2 - Chapter3</title>
>
> And thinking of these kind of details I just had a quick look at the
> source code of the HTML page as rendered in my browser. It looks like
> this for any URL.
>
>      <title>
>          Portal
>          &mdash;
>          Portal
>      </title>
>
>
>
>          <base href="http://beta.selfplatform.eu/SELF/"; />
>
>
>
>      <meta name="generator" content="Plone - http://plone.org"; />
>
>      <meta content="This instance of selfApp was made with code checked
> out from cvs "
>            name="description" />
>
> Now for accessibility purposes it is advisable to say meaningful things
> in each of these tags. Right now they contain fixed values, but we'd
> need to make them relevant for the given page. For example, for the
> imaginary page presenting Chapter3 of Course2 in Collection1:
>
>
>      <title>SELF Platform | Collection1 - Course2 - Chapter3</title>
>      <base href="http://selfplatform.eu/"; />
>      <meta name="generator" content="SELF Platform" />
>      <meta content="Description field of Chapter3 or, if not available,
> Description field of Course2"
>            name="description" />
>
>
> > I think the problems mentioned in this report are pritty easy to solve
> > and would make up for the remaining accessibility problems.
> I agree, these issues are rather easy to solve.
>
> > I will follow up and address this problem with rajive in the next 2
> > days since I might not be there on monday and tuesday.
> excellent.
>
> best,
>
> Wouter
>
>
> _______________________________________________
> Self-platform-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/self-platform-dev
>