Design for user empowerment
Open accessThe DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
As an accessibility researcher, I have noticed that some of the best work comes when there are people with disabilities on the design and development team, contributing to all aspects of the design and implementation, not just as participants in user studies.I call this strong engagement by users design for user empowerment, meaning, in its strongest sense, that the users of the technology are empowered to solve their own accessibility problems.Here, I will try to explain, mostly using examples, why this approach is so powerful.Although I am not disabled, I am very fortunate to have lived around disabled people my entire life.My parents were deaf college graduates and successful professionals.I learned from them that disability is not a tragedy, but rather simply part of the diversity of life.I also learned from them the power of technology to be transformational, not in any kind of medical sense but in a purely social sense.When they and their friends got TTYs, surplus Western Union Teletypewriters attached to acoustic modems, in the early 1970s, they could finally communicate easily at a distance with friends and colleagues around the country by typing, or what we now call texting or instant Insights → It is important for designers of technology for people with disabilities to engage with people with disabilities to achieve the most usable designs.→ Better yet is empowering people with disabilities to design and build the technologies themselves.→ Two features of design for user empowerment are self-determination and technical expertise.
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
Cites
Kane, S. K., Bigham, J. P., & Wobbrock, J. O. (2008) · Proceedings of the 10th International ACM SIGACCESS Conference on Computers and Accessibility · doi:10.1145/1414471.1414487 · Cited by 374 · cited 1×
“…made accessible using a very simple principle: Exploring the screen with one finger allows the screen elements to be read aloud without activating anything, and once an element is read, it can be activated by a gesture that does not occur during exploration, such as a spit tap or a double tap [3].”
Background
Cited by
Considerations for AI fairness for people with disabilities
Trewin, S., Basson, S., Muller, M., Branham, S., Treviranus, J., Gruen, D., Hebert, D., Lyckowski, N., & Manser, E. (2019) · AI Matters · doi:10.1145/3362077.3362086 · Cited by 143
Generative Theories of Interaction
Beaudouin-Lafon, M., Bødker, S., & Mackay, W. E. (2021) · ACM Transactions on Computer-Human Interaction · doi:10.1145/3468505 · Cited by 75
How accessible is my visualization? Evaluating visualization accessibility with Chartability
Elavsky, F., Bennett, C., & Moritz, D. (2022) · Computer Graphics Forum · doi:10.1111/cgf.14522 · Cited by 68
Interaction Proxies for Runtime Repair and Enhancement of Mobile Application Accessibility
Zhang, X., Ross, A. S., Caspi, A., Fogarty, J., & Wobbrock, J. O. (2017) · Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3025453.3025846 · Cited by 59
“Ensuring full access to the wealth of information and services provided by such apps is a matter of social justice [39], but for the estimated 15% of the world population with a disability [60], many capabilities and services offered by apps remain inaccessible.”
BackgroundKopeć, W., Nielek, R., & Wierzbicki, A. (2018) · Proceedings of the 11th International Workshop on Cooperative and Human Aspects of Software Engineering · doi:10.1145/3195836.3195840 · Cited by 45
Metadata
- Authors
- Ladner, R. E.
- Venue
- Interactions
- Published
- 2015-02-25
- Volume
- 22
- Issue
- 2
- Pages
- 24-29
- ISSN
- 1072-5520 (ISSN-L)
- 1558-3449
- OpenAlex
- W2200611418
- Cited by
- 160
- References
- 1
- FWCI
- 83.48
- Type
- journal article
- Language
- en
- Open access
- bronze
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
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.