[JS2-587] Improve portal accessibility

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Layout
• Assignee: Unassigned
• Reporter: Evangelos Vlachogiannis
• Created: 26/Sep/06 19:16
• Updated: 08/Mar/11 02:00

Description

Making a portal accessible is a challenge. I can see four different levels/components for accessible portal (in a priority order):
1. Accessible important content for users
The actual important content of the portal should be accessible. This means that we should provide accessible markup in a logical form for better understanding by the users (more: http://www.w3.org/WAI/intro/wcag.php). Navigation is an important aspect that needs to neither limit nor overload user. We define different level of navigation such as main, inter-portlet and intra-portlet. Another important aspect is a updated full sitemap.. (more: http://www.syros.aegean.gr/users/evlach/page ).
2. Authoring tools that produces accessible content
See graffito jira issue : (http://issues.apache.org/jira/browse/GRFT-102)
3. Accessible authoring tools
See http://www.w3.org/WAI/intro/atag.php and http://www.syros.aegean.gr/users/evlach/page
4. Accessible portal administration
Finally, as administrators are a limited number of users that a portal can have it is last but not least to have it accessible. Usually it is also more difficult as it has UIs for complex tasks.