Guidelines for presenting at the Disability Research Forum
Our aim is to make the forum an accessible and safe space for as many people as possible and so these guidelines are an example of the sorts of things that we would like you to think about/provide during your session.
We do not want you to be put off with all the requirements so if you feel that you don’t have time to do some of them, it’s not a problem, but we do request that you do as many as you can. Similarly if you feel that we could help you to achieve any of them or if you would like to suggest something which would help in future sessions, just send a quick email and I’m sure we can sort something out (email@example.com).
- Please provide a title and summary at least 1 month before your session – this is so that we can advertise and get as many people as possible to the event
- If possible please provide an accessible summary of the paper either around 1 week before the session (so that I can distribute it via email) or ready for the session itself. The summary should be easy to read and conceptualise. It should briefly explain your paper/presentation and where possible explain any problematic terms (e.g. if you use terminology in a certain way, but you are aware that this may be problematic for some, please give a brief explanation of how and why you are using the term in the way that you are). We understand that doing this with papers that are particularly theoretical may be difficult and we do not want to discourage this type of work being presented at the DRF but if you think it is something that you could provide please do.The summary doesn’t need to be more than 3-5 sentences.
- Please provide a couple of hard copies of your slides as some people find this easier than looking at them on the screen (it will be at your discretion if you would like these back at the end or if people are allowed to keep them)
- If you are reading a paper outloud please provide a couple of hard copies of this as well for people to read along with you (preferably at least one in large font). These will be claimed back to protect your intellectual property.
If you require any materials printing for you, just send them to the email address above and this can be arranged (please do this at least 24 hours before your session).
- If you are using pictures/charts/illustrations/photos/quotations in your presentation please come prepared to describe what the picture is and tell us why it’s there.
- If your presentations include short videos and any of the movement is important please be prepared to give short verbal descriptions of what is/has happened.
- If your session includes any sudden or loud noises please consider if these are integral to the session. If they are, please warn us beforehand.
For PowerPoint presentations:
- use no less than 20 point font Arial or Helvetica in capitalized lower case
- use left justification only
- ensure headings are not underlined
- ensure lists are numbered (bullet points are avoided)
- aim for around 20-25 words per slide
- ensure text does not overlay pictures or a patterned background
- use black text
- if the background has 10% grey scale this can reduce glare and offer a contrast with the black text. However if you feel that you want to move away from this, please make sure that the background is different enough for your black lettering to show clearly when on the screen
- provide a verbal narration of your slide
- where pictures are used, it is also important to provide a complete verbal description
For accompanying handouts (including copies of PowerPoint), in addition to the above, it is helpful if:
- material is produced at a minimum of 14 point Arial or Helvetica
- layout is clear, with space to make notes
- copies are available on the day
- a range of alternative formats is available if requested in advance
[These are adapted from: Mallett, R., Runswick-Cole, K. and Collingbourne, T. (2007) ‘Guide for accessible research dissemination: Presenting research to everyone’ Disability and Society 22:2, pp.205-207. We recognise that they are not an exhaustive list and will not cover all access requirements.]
Thank-you for your cooperation,
Steph Swain and Hannah Ebben