Hi Dan,

Sorry for the delay in responding. I'm really glad you enjoyed the unconference and U-Camp!

We haven't yet done comprehensive UX Walkthroughs of uPortal from an accessibility perspective. Most of what we have observed suggests that uPortal is fairly accessibility for keyboard-only users. I haven't yet tested with a screenreader.

It's my understanding that 2.6 has improved the state of the markup and CSS in uPortal quite a bit. It sounds like if CSU Chico has done work to improve the markup even further, we should encourage them to contribute it back to the community!

Section 508 has the bizarre requirement that sites must work with CSS turned off. It would be an interesting exercise to spend some time working with uPortal with stylesheets disabled and see how it works.

JavaScript, on the other hand, is not prohibited by Section 508. Unfortunately, though, the current drag and drop layout functionality in uPortal 2.6 is not accessible. We're working with Jen Bourey and Eric Dalquist to replace this code with the more accessible Reorderer, which supports keyboard accessibility and assistive technology through ARIA.

I hope this helps,

Colin

Biondi, Dan wrote:
Anastasia, Colin, Gary, and Paul:

It was great to meet you, either directly or indirectly, at the JA-SIG 
unconference this week.  I was in awe of the work you have/are doing in 
relation to the Fluid project and your contributions to the open source 
community.

I was wondering if I could get your comments/recommendations to the thread 
below regarding the state of accessibility for uPortal 2.6 and beyond.  At Sac 
State, all Web apps implemented after 9/1/07 are required to be US Section 508 
compliant.  There is also major effort underway across the California State 
University system to bring all university media into accessibility compliance.  
What is the status of accessibility in uPortal or what would be the best 
resource to determine this status?

Thanks for help.

Dan Biondi
Web Portal Coordinator
Sacramento State
v: +1 916-278-7616


(P.S.  Being new to the open source community, I wasn't sure if there is a list 
that would be appropriate for this inquiry.  If so, please feel free to also 
post your replies there as well [or let me know where I should post].)

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jungling, Scott
Sent: Tuesday, November 13, 2007 1:21 PM
To: [EMAIL PROTECTED]
Subject: RE: [ATI-webcop] uPortal accessibility?

Peter and Dave,

Here at CSU, Chico accessibility has been a top priority for uPortal since we started back in 2004. 
Currently, we're running uPortal 2.6 and not using any of the AJAX/DHTML UI elements. In addition, 
we spent a fair amount of time de-table-ifying the XSLT files for uPortal and rebuilt it from the 
ground up using clean semantically meaningful(ish) markup. What we discovered is that in doing this 
we could make most aspects of uPortal accessible. Unfortunately there are some pieces of uPortal 
which are "outdated" and sometimes the end markup is less than optimal (jTidy for 
instances seems to love inserting the "shape"
attribute on all links...). In addition, it is tough to ensure that portlets or 
external content is 100% accessible.

Basically our uPortal instance can be viewed without CSS and/or Javascript 
while retaining all functionality. In addition, we use headings to create a 
clear outline for all the content on each page.
We're using the Yahoo User Interface(YUI) CSS to do multiple column layouts and 
the YUI TabView component to create tabs across the top.


Scott Jungling
Web Application Development
CSU, Chico



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Margolis, Dave
Sent: Tuesday, November 13, 2007 13:01
To: [EMAIL PROTECTED]
Subject: RE: [ATI-webcop] uPortal accessibility?

I would like to mirror Peter's question - we are at the same stage with uPortal.

Also, anybody using the newer AJAX/DHTML UI elements in uPortal with any 
success?  In my initial analysis, those features could be accessed through more 
static means (regular links and such), but we won't be a position to do any 
real testing/evaluating until March.

Thanks!

Dave Margolis
Coordinator of Web Services
Information Resources & Technology
Sacramento State
916-278-7343


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mosinskis, Peter
Sent: Tuesday, November 13, 2007 12:51 PM
To: [EMAIL PROTECTED]
Subject: [ATI-webcop] uPortal accessibility?

Hi folks,

I know a few CSU campuses use uPortal (Chico? SLO?).

For campuses which are using it, have you done any accessibility eval and 
repair on uPortal? If so, do you have a write-up about what kinds of repairs 
were done to make it accessible? Or, alternately, would you be able to speak to 
me about the experience and share what you recall?

We are in the early stages of a uPortal rollout, and it would be useful to not 
re-invent the wheel when it comes to discovery and repair of accessibility 
issues within the interface.

Thanks,
Peter

<snip>

--
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org

--
You are currently subscribed to [email protected] as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to