Accessible Virtual Conferences | SIGACCESS SIGACCESS ACM's Special Interest Group on Accessible Computing SIGACCESS Mission Statement Leadership Join Local Chapters Contact RSS Feed Calls Call For Papers Call For Nominations Call For Award News ASSETS (Conference) Current ASSETS Conference Most Recent Proceedings Past ASSETS Conferences Related Conferences Resources Accessible Conference Guide Accessible Virtual Conferences Accessible Writing Guides Describing Figures Accessibility FAQ Page Generator Accessible PDF Author Guide Accessible Presentation Guide Conflict of Interest Thesis Repository Download Logo ACM Diversity and Inclusion Council Access SIGCHI TACCESS (Journal) Anti-Harassment Policy Awards Outstanding Contributions Impact Award Best Paper Best Student Paper SIGACCESS Travel Scholarship Accessible Virtual Conferences Version: 1.0 [December 2020] Lead author: Michele A. Williams Additional contributors: Shari Trewin, Jennifer Mankoff, Elaine Short, Matt Huenerfauth, Tiago Guerreiro, Soraia Prietch This is a guide to organizing and executing accessible virtual conferences inclusive for people with disabilities. Guidance is based on accessibility standards such as the W3C’s Web Content Accessibility Guidelines (WCAG) and user experiences with virtual meetings. This is intended to supplement the ACM Virtual Conferences Guide and SIGACCESS Accessible Conference Guide (for in-person conferences). Contents 1. About Disability A. Assistive Technology B. Communication Diversity C. Invisible Inclusion Needs 2. Early Planning A. Accessibility Chair B. Conference Software C. Help Desk Channels D. Conference Website E. Registration F. Budgeting for Accommodations G. Advertisements 3. Conference Set-up A. Program and Schedule B. Presenter and Attendee Accommodations C. Pre-Recorded Clips and Sessions D. Microphones, Cameras, and Backgrounds E. Chat and Question & Answer (Q&A) Features F. Moderators G. Multi-Track Sessions H. Social Hour I. Breaks J. Pre-Conference Tours 4. Presentations A. Poster and Slide-based Presentations B. Panel C. Workshops D. Submissions & Proceedings 5. Additional Resources A. Conference Guidance B. Web Accessibility C. Document Accessibility D. Presentation Accessibility E. Video Accessibility 6. Checklist 1. About Disability We first provide details about disability and accommodations to help organizers understand the scope of what, and more importantly who, needs to be considered in the planning and execution of a virtual event. Below we detail information about assistive technology, communication diversity, and invisible inclusion needs. A. Assistive Technology One means of accounting for the diversity of conference participants is to understand the ways they may be using their personal computing devices. Note that people with a variety of disabilities as well as no disability use any one of these settings and tools, or a combination of them. Though not completely exhaustive, below are some of the most common assistive technologies and example categories of users. Common Assistive Technology Assistive Technology Description Beneficiaries Screen reader Text-to-speech software that translates code from GUI-based interfaces into audio output. People who are blind or low vision and cannot see a GUI clearly or at all, or sighted users who benefit from auditory rather than visual output, such as some people with migraines. Refreshable braille display Hardware device that translates computer output into braille by electronically raising and lowering pins in braille cells. People who are blind or deaf-blind. Zooming Application setting that increases text size of individual applications, generally through keyboard shortcuts such as Control +/-. People with low vision for whom a larger view helps overcome visual limitations including many adults over 40, or users with difficulty reading or focusing who find the zoomed view easier to follow. Magnification An operating system setting or third-party software that creates a magnifying glass effect to enlarge screen content. People with vision impairments for whom a larger view helps overcome visual limitations, such as myopia or cataracts. Recolor Setting that changes screen colors to an inversion or limited set such as yellow and blue or black and white. People with visual impairments that benefit from increased color contrast, or sighted users with conditions that impact visual processing such as Dyslexia. Keyboard-only navigation Using keyboard keys and commands to mimic mouse behaviors such as Tab to move and Enter to select. People with mobility impairments that impact manual dexterity such as Cerebral Palsy or repetitive strain injury. Switch control Large button on a mountable base that, when paired with the operating system, can mimic keyboard and mouse behavior with button presses by any body part. People with mobility impairments that impact fine motor control in their hands, such as Quadriplegia. Mouth or Head stick Stylus held in one’s mouth or worn around one’s head to type on the keyboard or tap on a touchscreen. People with mobility impairments who have fine mobility control in their head and neck area. Foot mouse Hardware device that allows using a mouse with one’s feet rather than hands. People with mobility impairments who have better control in their feet or people without hands and arms or repetitive strain injury. Voice control Operating system setting or software for dictating text and commands that mimic a keyboard and mouse People with mobility impairments that impact dexterity or use of hands but not voice. Eye tracking Software that controls the mouse cursor with eye movement and dwell on on-screen controls. People with mobility impairments that impact dexterity and their voice. Text-to-speech Operating system setting or software that reads aloud selected text in a computer voice and sometimes accompanied by highlighting the text being read. Note, while similar to a screen reader, this is primarily focused on text and not announcing GUI elements such as “Button” or “Link”. People with difficulty focusing and/or reading such as those with learning disabilities, Dyslexia, or Tourette’s Syndrome (which can impact eye movement). While this may feel overwhelming, with proper planning and execution we can harness technology to provide an environment where every participant can flourish – all in the same tool. B. Communication Diversity Along with assistive tools and technologies, it is important to understand how people communicate when one or more of their senses is impacted by an impairment. Below we detail the main communication styles and tools organizers should consider in their virtual event planning. Communication Diversity Communication Style Description Beneficiaries Captions Text translation of talking and sounds. People who are hard of hearing or deaf including many older adults, listening in their non-native language, or have auditory processing disorders. Sign language Visual language expressed by movements of the hands and face. Note, there are different languages and dialects of sign language as in oral languages. People who are deaf, particularly members of the Deaf community. Tactile sign language Method of receiving sign language by placing one’s hands over a communication partner’s hands to feel their shape and movement. Used by people who are deafblind, though for virtual meetings this will likely be supplemented by a braille display. Audio description Auditory descriptions of visual information, such as a presenter describing a photo on their slides. People who are low vision and blind. Augmented and Alternative Communication (AAC) Devices & Text-to-Speech Software often driven by touch interfaces or eye tracking to form text-to-speech output. People with a speech impairment or who are otherwise non-verbal. Text-based communication Related to AAC and Text-to-Speech, this includes typing conversations rather than talking as in typing via a chat feature. People who are hard of hearing or deaf, those with a speech impairment, or those who are otherwise non-verbal. It is key to remember that people take-in and relay information through a variety of means. Throughout this guide we will explain how to best address these communication styles in all facets of a virtual conference. C. Invisible Inclusion Needs Many participants will have inclusion needs that are not necessarily physical but still need consideration for an inclusive conference. Below we explain areas of particular importance to the virtual conference environment. Considerations for non-physical impairments Consideration Description Beneficiaries Clear organization of information Conference information clearly defined and easy to find to aid keeping tasks ordered, orderly, and accomplishable. People with conditions impacting processing and organizing information such as Attention Deficit Disorder (ADD) or a Traumatic Brain Injury (TBI). Distraction-free engagements Avoiding unexpected sounds or unnecessary moving visual media can prevent impediments to taking in information or completing a task. People with conditions impacting attention, such as ADD. Flexibility in engagement A person’s mental and physical energy levels can fluctuate. Thus, opportunity to engage when at one’s best (or have clearly defined programs that allow proper planning around key moments) is critical to a successful event. People with conditions that can put a tax/drain on one’s mental capacity and desire to engage in groups, such as Autism or chronic fatigue. Lack of excessive animation and flashing in presentations Many popular animations such as parallax scrolling can cause motion sickness and other harmful effects for users. While there is not yet formal guidance on animations, it is advised they be avoided or used sparingly. (Note, for instance, the recent operating system setting to “Reduce Motion” which turns off such effects.) Excessive flashing content can cause seizures. WCAG advises on no more than 3 flashes per second ( Guideline 2.3.1 ). People with motion sensitivity or photosensitive epilepsy. Much of what benefits conference participants with conditions as mentioned are preparation, organization, and structure – overall goals for any conference organizing team. Thus, even though these goals are not different from the main goals of the event, we will point out throughout this guide where they should be particularly emphasized. 2. Early Planning Considering accessibility early in the conference planning is key to a successful outcome. This includes appointing an Accessibility Chair to oversee key accessibility related activities and being mindful to create and choose accessible technology for the conference. A. Accessibility Chair Appointing an Accessibility Chair at the start of your conference planning is vital to the implementation of a welcoming and inclusive event. For a large event, or a hybrid event, more than one accessibility chair may be needed. The Accessibility Chair, as explained in the ACM Virtual Conference Guide , is responsible for the following: Helping with the selection of accessible platforms and tools. Working with attendees to ensure the necessary access services are included. Helping to plan and budget for access services. Establishing best practices for preparing and running accessible sessions. Providing information on accessibility to authors and prospective attendees. An Accessibility Chair should be well-versed in working with people with diverse access needs, familiar with evaluating accessible technology, and comfortable guiding teams and vendors on making outcomes accessible. In particular, the accessibility chair should have sufficient standing in their research community to influence the decisions of the local arrangements, publicity, publications, and general chairs, and we therefore would recommend that the accessibility chair be a faculty member (rather than a student or postdoc) or have a co-chair who is a senior faculty member. The accessibility chair should be someone with a strong understanding of accessibility considerations, for example someone whose research touches on accessibility, who teaches accessibility-related classes, who holds an accessibility-related position in their university, or who comes from a university with large numbers of students with disabilities (such as Galludet University). In addition, we strongly recommend that the accessibility chair develop a relationship with at least one professional who specializes more generally in accessibility across a wide range of needs, such as employees and connections of their university Disability Support Services office, independent accessibility consultants, or people involved in programs with accessibility focus (such as the University of Washington’s Center for Research and Education on Accessible Technology and Experiences). Your organization may have an accessibility community that can connect conference organizers with potential candidates for this position. Within ACM, the Access SIGCHI group offers support for accessibility chairs. You can also reach out to the leadership of SIGACCESS or the ACM Diversity and Inclusion Council for advice. B. Conference Software The video conferencing tool used for the conference must consider accessibility; that is, the system must work when using the assistive technologies listed in the first section. Keep in mind that much of current technology is not accessible. Making a tool accessible requires development teams to consider accessibility at all points of the lifecycle including design, development, and testing, for which many companies do not make the investment. Thus, the Accessibility Chair(s) should be directly involved in deciding the conference’s software. ACM does have access to an organization license for Zoom ; more information may be found in the “ Zoom Meeting Guide “. In leveraging this license, you will be accessing a highly accessible video conferencing tool with many built-in capabilities for accommodations and the added benefit of increased familiarity based on its ever-increasing popularity. Note, however, that Zoom does not automatically come with captioning. That is, Communication Access Realtime Translation (CART) interpreters still need to be hired (along with sign language interpreters where applicable); this is not currently available with the ACM Zoom license nor the overall offerings from Zoom. If other video conferencing tools are being considered, note they should be able to provide documentation as to the state of overall accessibility. This is usually in the form of a dedicated Webpage detailing their product’s accessibility features and/or an Accessibility Conformance Report (ACR), sometimes referred to as a Voluntary Product Accessibility Template (VPAT) document (preferably completed by a third party). For example, Zoom provides a page dedicated to accessibility . They should also be able to provide how-to documentation for users of particularly complex assistive technology; for example, Microsoft Teams has documentation for screen readers Tool providers’ attitudes to accessibility also vary widely. Check whether they have accessibility expertise and would be responsive to issues. Additionally, there should be support within the disability community as to the validity of the company’s claims, such as social media posts from disabled users that verify they are able to use the software (and, conversely, no posts saying the claims are false). One good measuring tool is to consider the software used by national disability organizations for their 2020 virtual events. For example, you can explore how the National Federation of the Blind (NFB) handled their 2020 virtual convention When selecting tools, consider if/how they incorporate captions and transcripts. It is highly preferred to have tools that offer closed captions and real-time transcription in the same window as the video conferencing itself, as opposed to a separate window. It is also important to offer “closed captions” (meaning captions that are optional to view) as some people may find the captions equally distracting as some find them necessary. Transcripts in the same window allow a running view of the entire presentation which can be helpful to many participants. However, organizers will also need to work with the CART personnel to provide a separate Website for real-time transcripts that work for deafblind braille users. These streams are also an important alternative if the videoconferencing technology’s caption display introduces too much lag time. A real-time transcript that can be followed visually and one with a refreshable braille display are going to have different technical needs and be derived with different technologies to provide equivalent experiences. Set-up for sign language interpreters should also be considered in the process. This should include options for showing/hiding interpreters (similar to closed captions), keeping them present for group discussions like panels or breakout groups, how best to identify interpreters in the sea of video feeds (such as customize their name to include “Interpreter”), confirming the ability to “pin” the interpreter’s video on the screen at a reasonable size for those deaf participants watching them, and how to switch views upon interpreter hand-offs. Note that deaf presenters might be signing their presentation and have that spoken aloud to the audience by the interpreter and they need to see that interpreter for any question & answer sessions. C. Help Desk Channels Organizers should provide a means for attendees with disabilities to obtain real-time assistance, particularly just before and during the conference. Accessible chat-based interaction tools such as Discord offer a great means of immediate assistance and repository of instructions and answers to frequent questions, particularly when organized into subject-based channels. The Accessibility Chair(s) should work with the team to organize this set-up (including ensuring the tool chosen is accessible) and work with designated team members and volunteers to monitor the system before and during the event. This can also be used for gathering feedback after the conference to make improvements for the next year. Note this does not replace direct contact with the Accessibility Chair(s) (e.g., email) as participants may need assistance with the Help Desk tool itself. Also, note that users may find this additional channel overwhelming and hard to follow during the conference if notifications are not set properly; tutorials on how to manage communications are highly recommended. D. Conference Website Gathering information from the conference Website is vital for people with disabilities who need to evaluate their participation based on how the conference has considered their needs. Thus, the site itself must be accessible (that is, the code of the site must allow assistive technology use) and then the site’s content must answer a lot of questions. Building an accessible Website takes a detailed understanding of the W3C’s Web Content Accessibility Guidelines . At the time of writing, WCAG 2.1 AA is the recommended standard to use. As not everyone is taught accessibility when learning to create a Website, it is best to start with an accessible base such as a WordPress “accessibility-ready” template or template from software tools that are based on native HTML such as Webflow . If developing from scratch, the key is to avoid as much custom code and outside widgets as possible if not familiar with how to create accessible custom elements. Additionally, Webpage builders should keep in mind the most common techniques such as those listed in this WordPress accessibility article and Webflow accessibility article . Developers are also encouraged to leverage automated testing tools to evaluate their page accessibility, as explained in this article on testing tools from A11y Coffee . Make sure the site can be fully navigated using only a keyboard by testing manually. The WCAG checklist on A11y Project can be helpful to understand if the site is meeting the WCAG criteria and where items may be difficult for users. The Website’s content should contain the following where appropriate on the site: Identify the video conference software used for the event and, preferably, link to any accessibility documentation for the software Accommodations available (namely captions and sign language interpreting), and whether they are automatically provided (including in what language) or by request The primary conference language(s) The primary conference time zone(s), and when events will occur within those time zones How breaks will be handled (namely when and how long) Presentation formats (e.g., presentations, panels, etc.) and whether presentations will be live or pre-recorded (or both) If recordings of the conference will be made available after the conference, and if those will have captions and transcripts Registration requirements (before starting the registration process) including deadline, any membership requirements, pricing, and accessible alternatives for any inaccessible registration tools Conferences should provide a standard means for accessing the accessibility information. To support this, SIGACCESS and AccessSIGCHI are working together to develop an Accessibility F.A.Q. generator that will collect information about your virtual conference’s accessibility. To further standardize information access, we recommend putting this page at “[your conference url]/access” under an “Accessibility” navigation option. While the generator is still under development, available examples include the ASSETS 2020 and UbiComp 2020 pages. Information should include: Accessibility Chair(s) contact information Conference Accessibility Statement (or where to find) Conference format and tools details including state of accessibility of the tools, how captions and transcripts are displayed, major assistive technology considerations (such as screen readers, keyboard navigation, and screen magnification), and whether participants can see a technology preview before the conference Workarounds for inaccessible processes such as inaccessible registration tools Where to obtain assistance before and during the conference, such as a chat tool or direct contact person How to request accommodations and which accommodations may be requested, including whether you will accommodate differing languages for captions and interpreters than the official conference language Details regarding the distribution of materials, including when (before, during, or after) and in what formats (as in PDF, PowerPoint, etc.) E. Registration The registration and payment tool should meet the W3C’s Web Content Accessibility Guidelines (WCAG 2.1 AA); the Accessibility Chair(s) can aid with evaluating the best systems if using third-party tools. Key items include proper labels on form fields (as in the