[TYPO3-content-rendering] Integrating Accesskeypad - Hello...

Michael Haugg michael.haugg at memmingen.de
Fri Oct 28 09:34:42 CEST 2005


Thanks all for having had a look on it!

Hmm, good arguments...

Kai Laborenz schrieb:
> Michael Haugg schrieb:
> 
>>> I integrated Jan Eric Hellbuschs "Accesskeypad" 
>>> (http://2bweb.de/accesskey/) in my Typo3-Testwebspace.
>>> I have seen it already on http://www.greenpeace.de, but my idea is 
>>> not using the accesskeys for accessing certain pages, but using them 
>>> to navigate from level to level.
>>>
>>> [Alt + 1] : Mainmenu
>>> [Alt + 2] : Submenu
>>> [Alt + 3] : Submenu Level 1 (*)
>>> [Alt + 4] : Submenu Level 2 (*)
>>> [Alt + 5] : Submenu Level 3 (*)
>>> [Alt + 6] : current position in Submenu
>>> [Alt + 7] : Breadcrumbs
>>> [Alt + 8] : Infomenu
>>> [Alt + 9] : Pagecontext
>>> [Alt + 0] : Content
> 
> 
> Hm - I think the idea of Jan was to have a unified navigation system 
> across different sites! Thats why he published it.
> 
> To have sevaral Accesskeypads which work quite different is worse than 
> nothing for blind users and will harm the idea of having one standard 
> pad system!

I contacted Jan Eric Hellbusch by eMail askimg him about his opinion and 
he answered me the following: (Sorry for this excerpt in German, but as 
I understood it, he does not totally disagree to my solution)

"... An sich spielt es keine Rolle, denn die Nutzung ist vor allem an
Tastaturnutzer gerichtet, die sich "irgendwo" auf der Seite befinden.
Seiten, die den Designvorschlag nicht nutzen und aber das Schema haben 
die Links auch überall verteilt, etwa

www.landtag.nrw.de
...
Selbstverständlich steht es Ihnen frei, ein Schema für Ihre eigenen 
Projekte zu entwickeln.

Mein Schema sollte eine Mischung aus "Ersatz für LINK" und
"Screenreader-Nutzer und andere Tastaturnutzer helfen". Ihr Schema geht
eindeutig in Richtung Tastaturnutzer, was aber nicht verwerflich ist. Nur:
Wenn Sie mit Überschriften und Listen und anderen Blockelementen 
arbeiten, dann ist die Navigation im Screenreader recht gut 
gewährleistet. Andere Tastaturnutzer haben sicherlich einen Vorteil 
durch Ihr Schema.
"
> 
> Working with abstract terms like "Submenu Level x" is not easy to 
> understand - I visited your site and I had no idea where "Submenu Level 
> 3" would take me...
> 
> After all a page shortcut navigation needs to be at the very first 
> position of a page - so that it is read to the beginning. This would be 
> even more important when you have unusual navigation tools.

This ist what Jan eric Hellbusch answered me [Translation]:
"
Also meine Ratschläge dazu: [My advices:]

- am Anfang zwei unsichtbare Links
- [at the beginning two invisible Links]

   1. zum Textbeginn
      [to content]
   2. "Wie navigiere ich diese Seiten nur mit Tastatur?"
      [How to navigate this pages with shortcuts]

- den Accesskey-Pad würde ich im Quelltext dann möglichst weit hinten
platzieren. Optisch können Sie das dann "irgendwo" platzieren, wie es 
halt im Layout passt.
[I would place the acceskeypad at the end of the sourcecode. It can be 
displayed as it fits in your layout]
"

> BTW: Three things about the memmingen site
> 1. It confused me that the vertical menu on the top left position is 
> something different on the homepage as on the other pages.
The submenu of the homepage contains the sub-homepages of some 
insitutions of Memmingen.

> 2. The page contains a lot of external links which are not marked at all 
> - very annoying.

You see it when you switch to nocss. They are marked this way:

var_exturl = <span class="invisible"> (external link, opens in new 
window)</span>
var_exturl_title = 'external link, opens in new window'
...
temp.exturlspecialwrap {
  stdWrap.cObject = CASE
  stdWrap.cObject {
    key.field = doktype
    default = TEXT
    default {
       field = title
    }
    3 = TEXT
    3 {
       field = title
       wrap = |{$var_exturl}
       #ATagParams = title={$var_exturl_title}
       #ATagTitle = {$var_exturl_title}
    }
  }
}

But unfortunately I still have no Idea how to add a title Tag to 
external urls in Menus :-( ... believe me, I tried to find it ...

> 2. You inculded a styleswitcher into the accesspad - it looks you can 
> change the layout of the Accesspad with the dropdown box - not the page 
> layout.

Good advice, this will be changed if I implement the accesskeypad to the 
live-site.


Again I want to thnak all of you very much for spending some time and to 
give me some good arguments to think about!

Regards from Memmingen

Michael



More information about the TYPO3-project-content-rendering mailing list