Desire2Pod Cast 3: Web Accessibility
This is the third podcast in this series. The focus this time is on web accessibility issues, although much of the discussion is general in nature and not just related to accessibility within D2L.
Once again I need to apologize for somewhat less than wonderful sound quality. This time I recorded a Skype call using Pretty May, which appears to do something funky with the incoming call occupying only the right-track (at a low volume) and the outgoing call occupying only the left-track. After much editing in Audacity (but not nearly enough), I finally have something not too painful to listen to (a bit of a hum when James is speaking), but I'm still going to have to find a better method for recording these telephone interviews. I'm posting this a little ahead of schedule since I leave for China in about 5 hours and then all bets are off.
- Why worry about web accessibility?
- D2L wish list for accessibility (approx. 6:45)
- Tips for course designers (approx. 11:15)
- MnSCU system accessibility concerns (approx. 21:30)
Some of the resources referred to include:
- W3C Web Accessibility Initiative (WAI)
- Access e-learning website (Site used by LSC faculty and staff)
- MnSCU Web Accessibility Guidelines
- CSS Zen Garden
- Firefox Extensions for Accessibility (scroll down for list)
- D2L Consortium: Importance of LMS Accessibility (10/04/06 article)
Once again I need to apologize for somewhat less than wonderful sound quality. This time I recorded a Skype call using Pretty May, which appears to do something funky with the incoming call occupying only the right-track (at a low volume) and the outgoing call occupying only the left-track. After much editing in Audacity (but not nearly enough), I finally have something not too painful to listen to (a bit of a hum when James is speaking), but I'm still going to have to find a better method for recording these telephone interviews. I'm posting this a little ahead of schedule since I leave for China in about 5 hours and then all bets are off.
Comments
Do you have any idea whether the $80 million increased I.T. spending contains anything related to web accessibility? Okay, I retract the question on the grounds that it just makes me look silly.