Introducing Accessibility Requirements through External Stakeholder Utilization in an Undergraduate Requirements Engineering Course
The DOI matches its Crossref record.
Abstract
Undergraduate software engineering courses aim to prepare students to deliver software in a variety of domains. The manner in which these courses are conducted varies, though team projects with real or imaginary stakeholders are common. While the key course concepts vary from the entire lifecycle to specific aspects of design, concepts like accessibility are rare. This paper will present a study of team projects in a requirements engineering course. One group of students conducted projects with accessibility requirements while another group of students delivered projects without accessibility requirements. The course content was the same, including discussion of accessibility. To support the understanding of accessibility, stakeholders with disabilities were included in the requirements engineering process. Both teams benefited from the experience as indirect knowledge acquisition occurred. Students from a previous offering of the course, with no external stakeholder interaction, demonstrated lower levels of accessibility understanding.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
Who Teaches Accessibility?: A Survey of U.S. Computing Faculty
Shinohara, K., Kawas, S., Ko, A. J., & Ladner, R. E. (2018) · Proceedings of the 49th ACM Technical Symposium on Computer Science Education · doi:10.1145/3159450.3159484 · Cited by 127
Why Software is Not Accessible: Technology Professionals' Perspectives and Challenges
Patel, R., Breton, P., Baker, C. M., El-Glaly, Y. N., & Shinohara, K. (2020) · Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3334480.3383103 · Cited by 96
“Other research focused on effective pedagogies toward understanding the best teaching strategies to raise awareness [10,18,19,23,24] and encourage empathy [14] for users with disabilities in accessible technology design [8,14].”
BackgroundComparison of Methods for Teaching Accessibility in University Computing Courses
Zhao, Q., Mande, V., Conn, P., Al-khazraji, S., Shinohara, K., Ludi, S., & Huenerfauth, M. (2020) · Proceedings of the 22nd International ACM SIGACCESS Conference on Computers and Accessibility · doi:10.1145/3373625.3417013 · Cited by 40
Self-citationBeyond HCI: The Need for Accessibility Across the CS Curriculum
Elglaly, Y. N., Baker, C. M., Ross, A. S., & Shinohara, K. (2024) · Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1 · doi:10.1145/3626252.3630788 · Cited by 39
“Accessibility education in computing started as stand alone assignments [41] and single courses [30].”
BackgroundFerrari, C., Kletenik, D., Sonka, K., Sturm, D., & Hurst, A. (2019) · Proceedings of the 21st International ACM SIGACCESS Conference on Computers and Accessibility · doi:10.1145/3308561.3353795 · Cited by 29
“Students’ responses to exam questions indicated increased awareness of accessibility, compared to students the previous semester who had not worked with a person with disabilities [[24] ].”
Metadata
- Authors
- Ludi, S.
- Venue
- 29th International Conference on Software Engineering (ICSE'07)
- Publisher
- IEEE
- Published
- 2007-05
- Pages
- 736-743
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W2117919808
- Cited by
- 77
- References
- 0
- FWCI
- 0.97
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Introducing Accessibility Requirements through External Stakeholder Utilization in an Undergraduate Requirements Engineering Course. https://app.cochat.ai/papers/10.1109/icse.2007.46
- The paper
- Ludi, S. (2007). Introducing Accessibility Requirements through External Stakeholder Utilization in an Undergraduate Requirements Engineering Course. 29th International Conference on Software Engineering (ICSE'07). https://doi.org/10.1109/icse.2007.46
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.