The Code4Lib community aims to make the conference accessible for attendees
of all abilities.
Accessibility at the Conference
Code4Lib 2007 strives to be an accessible and inclusive space for all
When registering, attendees were asked to include any accessibility needs
they might require. We are doing our best to meet these needs. Everyone is
encouraged to contact the accessibility committee if they have
questions or new accommodation needs arise. The accessibility committee may
be contacted by:
For inquiries about accessibile parking and transportation, we recommend talking
with the Luskin Center directly.
During the general conference, Code4Lib 2017 will feature live captioning.
Attendees, both local and remote, may view the text stream at:
Accessibility Instructions for Presenters
All presenters should please review these accessibility requirements
and presentation logistics. Make note of the four action items for
Action 1: PC/Mac Compatibility
Ensure that your slides will display correctly on BOTH Mac and PC.
There will be a presenter laptop at the podium to streamline transitions
and minimize tech issues. We don’t yet know if it will be a Mac or a PC.
If you absolutely need to use your own laptop (e.g. a demo that only
works on your machine), please let your Program Committee Liaison know ASAP.
Action 2: Submit Slides Early for Supporting Live Captioning
Code4Lib 2017 will feature live captioning during the three days of the
general conference. In order to improve the quality of this service, we
ask presenters to send their slides to us so that the captioners can use
them as reference and improve the quality of the live text stream.
Please submit your slides to Aaron Collier
at least 24 hours before your presentation (the earlier the better).
NOTE: You can continue to edit and change your slides
after submission. You do not need to resubmit any changes unless you
feel you added any difficult words or terms that would be challenging
for live captioning. Keep in mind that the captioners may not have domain
expertise in libraries.
Action 3: Design a Visually Accessible Presentation
Presenters are encouraged to use the following guidelines to ensure that
their presentations are visually accessible to attendees.
- Avoid fonts that use thin strokes in the characters.
- Choose readable sans serif or serif fonts. Generally avoid script or
- Suggested fonts include: Helvetica and its clones (Arial, Calibri,
etc.), Gill Sans, Comic Sans (seriously!), Verdana, Franklin Gothic,
Rockwell, Tahoma, Lucida, and Times New Roman.
- Use underlining, italics, and boldface sparingly.
- Aim for a font size of 20-30 point. Generally, do not go below
18-point for slide content (if you plan to share your slides
with the community, it’s okay to use smaller fonts for references
- Choose text and background colors that have good contrast. You can
use a contrast
checker to check for good constrast. The web accessibility thresholds
are not relevant to slide presentations, but higher contrast is still better.
- For color blindness considerations, add patterns or labels in graphs and charts.
This is especially important if are using either red-green or yellow-blue
color combinations. These are the two most common types of color blindness.
If you are uncertain about a color choice, a color
blindness simulator may help.
- Avoid blinking text and animations that endlessly repeat.
- If your presentation features lots of animations, videos, etc.,
please include a warning at the start of your talk. This is especially
needed if any contain lots of flicker.
- If a video contains sound or dialogue, please try to use a version
- Participants are encouraged to share their slides. If placed on the
web, please include a short link in your opening slides for attendees
to view on their personal machines.
- Include speaker notes with your files if the file format allows.
In particular, describe any images, tables, charts, etc. in the notes.
- Specific advice for different presentation tools and formats: