Note: When clicking on a Digital Object Identifier (DOI) number, you will be taken to an external site maintained by the publisher.
Some full text articles may not yet be available without a charge during the embargo (administrative interval).
What is a DOI Number?
Some links on this page may take you to non-federal websites. Their policies may differ from this site.
Approximately 10% of computer science and engineering majors have a disability. Students with disabilities face a variety of challenges including those related to stigma around disability, inaccessible tools and instruction, disability disclosure, and a lack of mentors. This BOF will bring together individuals who are interested in increasing the representation of students with disabilities in computing and improving their success. Participants will share strategies to help each other do a better job of including these students in our classes and research projects. Resources related to accessible tools and instruction, universal design of learning, opportunities for students, and more will be shared.
A major goal of AP Computer Science Principles (CSP) is equity, that is, that all students should have the opportunity to learn computer science at a basic level. In this experience report, we explore how well the Code.org version of AP CSP meets the needs of Deaf students. We report on a professional development workshop for 14 teachers that teach at schools for the Deaf or in Deaf programs in mainstream schools. These schools and programs use the bilingual approach to teaching with instruction in American Sign Language (ASL) and other resources (e.g., textbooks, workbooks, videos, websites, computer apps, exams) in English. Synthesizing the experiences and advice of the teachers and workshop staff, we offer lessons learned for CS teachers in schools for the Deaf and Deaf programs in mainstream schools, mainstream CS teachers who may have one or a few Deaf students in their classes, and AP CSP content providers. Index Terms—Computer Science Principles, Deaf, English Language Learners, Bilingual, Professional Development
Block-based programming environments are very popular for introducing children to programming. Unfortunately, they are not accessible to many children with visual or motor impairments. In this paper we outline why block-based environments should be made accessible for these children, describe current efforts to make environments accessible, and describe how developers can incorporate accessibility into their own block-based programming environments.
The College Board's AP Computer Science Principles (CSP) content has become a major new course for introducing K-12 students to the discipline. The course was designed for many reasons, but one major goal was to broaden participation. While significant work has been completed toward equity by many research groups, we know of no systematic analysis of CSP content created by major vendors in relation to accessibility for students with disabilities, especially those who are blind or visually impaired. In this experience report, we discuss two major actions by our team to make CSP more accessible. First, with the help of accessibility experts and teachers, we modified the entire Code.org CSP course to make it accessible. Second, we conducted a one-week professional development workshop in the summer of 2018 for teachers of blind or visually impaired students in order to help them prepare to teach CSP or support those who do. We report here on lessons learned that are useful to teachers who have blind or visually impaired students in their classes, to AP CSP curriculum providers, and to the College Board.
The report documents the program and outcomes of Dagstuhl Seminar 18061 "Evidence About Programmers for Programming Language Design". The seminar brought together a diverse group of researchers from the fields of computer science education, programming languages, software engineering, human-computer interaction, and data science. At the seminar, participants discussed methods for designing and evaluating programming languages that take the needs of programmers directly into account. The seminar included foundational talks to introduce the breadth of perspectives that were represented among the participants; then, groups formed to develop research agendas for several subtopics, including novice programmers, cognitive load, language features, and love of programming languages. The seminar concluded with a discussion of the current SIGPLAN artifact evaluation mechanism and the need for evidence standards in empirical studies of programming languages.