[
https://issues.apache.org/jira/browse/JS2-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated JS2-587:
--------------------------
Fix Version/s: (was: 2.2.1)
Too much to deal with right now. To be determined in a later time frame.
> Improve portal accessibility
> ----------------------------
>
> Key: JS2-587
> URL: https://issues.apache.org/jira/browse/JS2-587
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Layout
> Reporter: Evangelos Vlachogiannis
> Assignee: Ate Douma
> Priority: Minor
> Attachments: patch-access-26092006.txt, patch-access-29092006.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
