I should keep blogging of course, but I put it off, like claiming expenses – when the next one comes in I’ll do the batch. The problem is keeping up with the incoming and my terminal curiosity. Briefly then…
I have 8 digital literacy in the disciplines projects running and almost 60 CLL micro-projects. All of these have some accessibility tales within them (and I am sure I will have problems teasing them out) but they are only just reaching the final reporting stage. When they are in I can put out more about them. See the HEA website for more info- http://www.heacademy.ac.uk/cll and http://www.heacademy.ac.uk/digital-literacies
In so many recent interactions I have eventually led tutors towards the TechDis ‘User Needs’ section to discover what the issues are. Then the conversation begins. Have a visit, then contact our helpdesk.
If you have a project…
It would really help me to discover the accessibility aspects if you adopt this simple tactic:
- Identify students with disabilities as clear and separate skakeholder. Think of their needs in an anticipatory fashion. If you are only thinking of the students without disabilities as all the others can be dealt with on a case-by-case basis (i.e. fixed at the last minute) then start again. Read the advice on the legislation. It’s there to give you the time to do it properly. Now you have them properly in mind.
- In the final report of the project have a paragraph heading Accessibility Challenges, Issues and Benefits.
This will describe what challenges were raised by various disabilities in the project (e.g. VI students could not see the detail in the demonstration of the weekly lab techniques), the issues that arose from these challenges (e.g. getting demonstrations onto accessible video in sufficient advance time) and the eventual benefits (e.g. the students found the video useful for practice; lab time saved; revision; better techniques from preparing scripts; everyone gained not only the disabled students etc.)
- Describe these in a slide whenever your project disseminates to an audience to raise the profile of the importance of doing the accessibility audit for your project to improve the outcomes for all future students, not just those who happened to be there at the time.
if the above was done for all projects, wherever you are, we could see each others innovations, tips, ideas etc. far more easily – “Simples”.
Finally, with the forthcoming demise of the DSA we are concerned about the affect it will have on the support for students – but that’s what we are here for: to support the practitioners use the technology more effectively in their teaching. If you are writing about your practice and the use of our advice and guidance please use #techdis so we can pick it up more easily.
For TechDis matters the TechDis team blog is generally the place to follow hence this has dried up a little. There’s far more going on in there.