[TYPO3-hci] My 4.1 proposal - again

[Kasper Skårhøj]

Lets assume we made the menu accessible without JavaScript, would  
that make the backend accessible or even close to be? If not, then  
lets forget it for version 4.x

So, we had lots of suggestions for menus and what tags to use etc.

Did anyone actually look at my code and point out things that are  
really bad?

Did you all consider that this is more than a menu? That any item in  
the menu bar should be able to open a layer beneath it which can  
contain menu items but could as well be a nice search box or a  
calendar or an IM window?

Did you consider the clock application where menu items are NOT just  
a URL call but an AJAX call which requires an onclick action which in  
turn requires JS and makes an accessible approach impossible?



If people are gifted with a screenreader of Lynx; does it make any  
sense at all to present to them more than the menu and a few other  
important things like a logout button? The clock would be irrelevant.  
An IM application would be as well. The icon bar with shortcuts is  
obsolete and module sensitive options and tabs are irrelevant. To me  
this looks like an argument for "alt_main_accessible_backend.php"  
which would use the same libraries to get all modules but wrap them  
in <ul><li> instead.




- kasper

"Necessity is the mother of invention"
-------------------------------
kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |  
gizmo: kasper_typo3