...
This is sorta mirrored after flickr, but in our case shows your tab hierarchy. What do you think?
Accessibility Support
Accessibility is a major design goal, since uPortal is focused on university needs. I'm currently working working on enabling three rough scenarios:
- Mouse/JavaScript Enabled
- Dragging and dropping portlets/tabs/pages
- Clicking on the arrows brings up menus
- Keyboard/JavaScript Enabled
- Portlets/tabs/pages can be moved using the Move Up/Down arrows on the menus
- Tab focusing arrows brings up the menus
- Keyboard/JavaScript Disabled
- No menu arrows are visible
- Portlets can be removed via Delete button on toolbar
- Further customization options available in Change Layout interface
AJAX Support
The new uP3 will make heavy use of AJAX, especially behind-the-scenes calls to the portal for layout management operations.
For channels though, the portal will only use AJAX for switching between portlet modes: Normal, Edit, Help, and others. Why? We have no safe way to make portlets use uPortal 's AJAX functionality if they weren't written to use it explicitly. We're not comfortable "rewriting" links and forms inside of unknown portlets to make their calls via AJAX.