portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evangelos Vlachogiannis (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Updated: (JS2-587) Improve portal accessibility
Date Sat, 30 Sep 2006 08:38:21 GMT
     [ http://issues.apache.org/jira/browse/JS2-587?page=all ]

Evangelos Vlachogiannis updated JS2-587:
----------------------------------------

    Attachment: patch-access-29092006.txt

Fixes:
1. A bug in portlet decorator fixed
2. full path patch created by eclpse removed

no style yet

demo working site: http://guportal.gunet.gr/

> Improve portal accessibility
> ----------------------------
>
>                 Key: JS2-587
>                 URL: http://issues.apache.org/jira/browse/JS2-587
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Layout
>            Reporter: Evangelos Vlachogiannis
>            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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message