{"id":"8947eaea-5bd1-47fe-9093-863e9faca780","arxiv_id":"2501.19380","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":5.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":0,"one_line_summary":"Blind and low-vision software professionals treat creative problem-solving as a daily necessity for basic job function, not as an optimization.","lead":"This study interviews 30 blind and low-vision software professionals and finds that they rely on creative problem-solving to deal with inaccessible tools and workplace barriers. A reader might care because it reframes accessibility work as a necessary, innovation-driven practice rather than an optional extra.","discovery_kind":"extension","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The abstract's contrast with sighted peers ('who pursue optimization') is unsupported by the study's own data or any cited empirical baseline; the descriptive findings for BLVSPs remain credible, but the comparative claim needs softening or direct evidence.","rationale":"The reader's weakest-assumption analysis correctly identifies the load-bearing issue: the abstract's comparative claim about sighted peers is not supported by the study's design. This is not a manufactured concern; it is a clear mismatch between the strength of the claim and the evidence. The descriptive, non-comparative findings—six themes grounded in 30 interviews, transparent method, and honest limitations—are credible and valuable. My recommendation is unchanged from the reader's conditional verdict: the paper should be accepted only if the comparative framing is removed or empirically supported. A conditional acceptance with a request to revise the abstract and Discussion is appropriate. I found no other concern that would justify rejection: the sample, though skewed male, is typical for this population; the re-use of previously collected interviews is disclosed; and the abductive analysis is standard qualitative practice. The concrete test I propose would directly settle whether the sighted-baseline assumption is correct by reusing existing data or a small new dataset, which is feasible and proportionate to the claim.","tokens_in":9658,"tokens_out":1815,"duration_ms":20247,"concrete_test":"Conduct a secondary analysis using a comparable dataset of interviews with sighted software developers (e.g., transcripts from Groeneveld et al., ICSE-SEIS 2021, or a new matched sample of 15–20 sighted developers) and apply the same thematic codebook used in this study, specifically coding for whether creative problem-solving is described as optimization-driven, necessity-driven, or both. If necessity-driven creativity appears at substantial rates among sighted developers, the abstract's binary contrast is empirically false and should be removed.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim in the abstract—'For BLVSPs, creative problem-solving is essential for navigating inaccessible work environments, in contrast to sighted peers, who pursue optimization'—rests on an empirical contrast that this study does not test. The paper reports interviews with 30 BLVSPs and analyzes their experiences, but it collects no data from sighted developers and cites no prior study establishing that sighted professionals' creative problem-solving is primarily optimization-oriented. The Discussion itself hedges this point: 'While sighted professionals might employ creative solutions to optimize or improve their workflows' (Section V). The abstract then hardens this 'might' into a categorical statement. Existing software-engineering creativity literature, including the very works cited by the authors (e.g., Groeneveld et al. [3], Inman et al. [23]), describes developer creativity as involving clever reuse, problem reframing, and necessity-driven adaptation—not solely optimization. Without a comparison group or a defensible baseline, the abstract overstates the evidence. The six themes themselves and the qualitative findings about BLVSPs' necessity-driven creativity are well supported by the interview data and analysis procedures; the vulnerability is specifically the comparative framing that elevates the finding into a claimed difference from sighted peers. If the authors soften the abstract to describe BLVSPs' creativity as essential and necessary, without asserting what sighted peers 'pursue,' the paper's contribution stands on its own.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper reports a qualitative re-analysis of semi-structured interviews with 30 blind and low-vision software professionals (BLVSPs), using reflexive thematic analysis informed by Amabile's componential model of creativity. The authors identify six themes: motivation driven by need, creation of opportunities, creation of tools, use and customization of tools, workflow strategies, and communities/sharing. The central claim, stated in the abstract, is that creative problem-solving is essential for BLVSPs to navigate inaccessible work environments, in contrast to sighted peers, who pursue optimization. The paper positions itself as the first study of creativity in the workplace experiences of BLVSPs and offers implications for organizations, tool builders, and communities.","tokens_in":9861,"tokens_out":4154,"duration_ms":46961,"significance":"If accepted with the comparative claim appropriately bounded, the paper is a meaningful qualitative contribution at the intersection of software engineering creativity research and accessibility research. Its strengths include a reasonably large interview sample for this population (30 participants), a documented two-phase coding process with multiple coders, explicit researcher reflexivity, a public protocol/codebook link, and an honest threat-to-validity discussion that acknowledges partial data saturation. The six themes are grounded in participant quotes and align with prior work on invisible access labor and DIY accessibility solutions. The descriptive finding that BLVSPs' creativity is often necessity-driven and community-supported is credible and useful for practitioners. The main weakness is that the abstract and parts of the discussion assert a categorical difference from sighted professionals that the study's design cannot support; this is fixable by softening or removing the unsupported comparative framing.","major_comments":[{"comment":"The categorical contrast with sighted peers, stated in the abstract as 'in contrast to sighted peers, who pursue optimization,' is not supported by the study's data. The paper reports interviews with 30 BLVSPs but collected no data from sighted developers and cites no empirical baseline establishing that sighted professionals' creative problem-solving is primarily optimization-oriented. The Discussion itself hedges this point ('While sighted professionals might employ creative solutions to optimize or improve their workflows'), so the abstract hardens an unsupported 'might' into a claim of fact. Because this contrast is part of the paper's central concluding claim, it is load-bearing. The authors should either remove the comparative assertion and describe BLVSPs' creativity as essential and necessity-driven, or provide direct comparative evidence or a defensible cited baseline for the sighted comparison.","section":"Abstract and Section V (Discussion)"},{"comment":"The comparison in the Discussion is also in tension with the paper's own cited literature. The authors cite Groeneveld et al. [3] and Inman et al. [23] to characterize developer creativity as involving clever reuse, problem reframing, exploration, and usefulness, not merely optimization. The dichotomy in the Discussion—BLVSPs create out of necessity, sighted professionals optimize—therefore conflicts with the characterization of creativity in the related work the authors themselves rely on. This makes the comparative claim internally inconsistent, not merely unproven. A more defensible framing would contrast the mandatory, access-critical nature of creativity for BLVSPs with its more optional, improvement-oriented role for other professionals, without asserting a categorical difference in the content or motivation of sighted developers' creativity.","section":"Section V (Discussion) and Section II (Related Work)"}],"minor_comments":[{"comment":"The opening phrase 'A distinctive aspect of LVSPs' appears to be missing the initial B; it should read 'BLVSPs.'","section":"Section V"},{"comment":"The quote about the video positioning tool lacks a participant identifier (e.g., P-number), whereas most other quotes in the Findings include one; adding the identifier would improve consistency and auditability.","section":"Section IV-C"},{"comment":"References [14] and [35] are the same source (Armaly, Rodeghero, and McMillan, 'A comparison of program comprehension strategies by blind and sighted programmers'); they should be consolidated into a single citation.","section":"References"},{"comment":"The description of abductive analysis could be clearer about how Amabile's model was used to derive themes without constraining inductive discovery; the linked codebook helps, but a sentence explaining how conflicts between inductive and deductive coding were resolved would strengthen the methods section.","section":"Section III-C"},{"comment":"The authors acknowledge that 'full saturation was not reached,' but this caveat is not reflected in the strength of some conclusions, such as the claim that creative problem-solving is 'essential' for BLVSPs. Softening Conclusion statements to 'participants in this study' or 'the interviewed BLVSPs' would align the claims with the stated saturation limitation.","section":"Section VI"},{"comment":"Demographic information (vision status, country, gender) is reported in prose; a summary table of participant characteristics and professional roles would improve transferability and make the diversity of the sample easier to assess.","section":"Section III-B"}],"recommendation":"major_revision","confidential_remarks":"The manuscript is a solid qualitative contribution that fits the journal's scope, and the descriptive findings about BLVSPs are likely to be of interest to both accessibility researchers and the software engineering community. The main issue is the unsupported comparative claim in the abstract, which is load-bearing but easily fixable by softening the wording or adding direct evidence. I do not believe new data collection is required for revision, because the paper's descriptive value stands independently of the sighted-peer contrast. I would encourage the editor to treat the comparative framing as the key point to be resolved in revision."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Punchline: this is a solid, transparent qualitative study of creative problem-solving among 30 blind and low-vision software professionals, re-analyzing an existing interview dataset with a creativity lens. The six themes are credible and useful. The soft spot is the abstract's claim that sighted peers 'pursue optimization,' which the data cannot support.\n\nWhat's new and what it does well: the prior DIY-solutions paper is here reframed around Amabile's componential model, which is a legitimate new research question. Connecting the creativity-in-SE literature to accessibility research is valuable, and the paper gives concrete examples of necessity-driven tooling and workflow adaptation. Methods are honestly reported: two-phase coding, researcher reflexivity, and they even ship the interview protocol and codebook via Zenodo. They also note partial saturation and uncertainty about motivation types, which is more candid than most.\n\nWhere it's soft: the sighted comparison in the abstract is not backed by a comparison group or a cited baseline. The Discussion says sighted professionals 'might' optimize, so the abstract hardens a hedge into a categorical claim. And the cited literature (Groeneveld et al., Inman et al.) actually describes sighted developer creativity as involving clever reuse and problem reframing, so the contrast is likely false. That needs fixing. The 'Creation of Opportunities' theme is thinner than the others, with limited participant support, but that's minor.\n\nWho it's for: anyone in accessibility and software engineering, plus folks studying creativity in the workplace. The organizational recommendations (dedicated time for tool customization, open-source support) are sensible. I'd send it to peer review; with the abstract softened it's a solid contribution.","headline":"Honest, useful qualitative re-analysis with one overreach in the abstract: the sighted-comparison claim needs softening.","tokens_in":10444,"tokens_out":1836,"would_cite":true,"duration_ms":18184,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"For blind and low-vision software professionals, creative problem-solving is a daily necessity for accessing standard development tools, not an optional route to optimization.","keywords":["creative problem-solving","blind and low vision","accessibility","software engineering","workflow adaptation","assistive technology","qualitative interviews","open-source accessibility"],"falsifier":"A matched-sample study using the same interview protocol with sighted software professionals would settle the claim: if sighted developers report routinely creating or adapting tools to access standard features or complete routine tasks, rather than mainly to optimize, the essential-versus-optional distinction would fail.","tokens_in":9430,"feed_emoji":"🦯","tokens_out":7772,"duration_ms":71417,"temperature":0.7,"pith_summary":"This paper argues that for blind and low-vision software professionals, creative problem-solving is not an optional improvement but a daily necessity: they must invent, customize, or repurpose tools simply to access standard development environments and complete routine work. Drawing on re-analysis of semi-structured interviews with 30 professionals, it identifies six recurring strategies, from building custom screen-reader add-ons to devising workflow tricks. The paper frames this as a contrast with sighted peers, for whom creativity is typically a path to optimization. The finding matters because it recasts accessibility adaptations as core creative labor rather than peripheral workarounds.","feed_headline":"For blind coders, creativity is a job requirement","feed_subtitle":"30 blind and low-vision developers describe inventing and adapting tools that sighted peers can take for granted.","key_machinery":"The machinery is a thematic-analysis framework built on a componential model of creativity, which splits creativity into domain-relevant skills, creativity-relevant processes, and task motivation. The paper uses these categories to organize interview accounts into six themes and to interpret tool-building, customization, and workflow tricks as instances of creativity. This model carries the argument by making it possible to show that the motivating force behind BLVSPs' creative work is necessity and autonomy, rather than the optimization that the paper attributes to sighted professionals.","core_discovery":"The paper's central claim is that for blind and low-vision software professionals, creative problem-solving is essential for navigating inaccessible work environments, in contrast to sighted peers, who pursue optimization. Through thematic analysis of interviews, the authors identify six themes: motivation driven by need, creation of opportunities, creation of tools, use and customization of tools, workflow strategies, and communities, sharing, and publicizing. These themes describe how BLVSPs build and adapt tools, such as NVDA plugins and autocomplete accessibility fixes, and develop strategic workflows to maintain autonomy and professional presence. The authors conclude that creativity is a fundamental requirement for basic job functioning for BLVSPs, not an optional enhancement.","pith_inferences":["An implication the paper leaves implicit is that its central contrast with sighted peers is an extrapolation; the interview data came only from BLVSPs, so a study of sighted developers is needed to verify that their creative problem-solving is primarily optimization-oriented.","The 'mandatory creativity' finding may generalize beyond blindness to other disability contexts and to any worker whose primary tools are not designed for them; the paper's framing of autonomy and professional presence could be tested there.","A testable extension is to measure the adoption and reuse of user-created accessibility tools (for example, screen-reader plugins) to quantify how the community-sharing theme translates into actual collective problem-solving.","If tool accessibility improves, the necessity-driven creativity documented here may diminish or shift shape, so the paper's claims are time-sensitive; a longitudinal replication would clarify whether the creativity is a stable trait of the population or a response to current tooling."],"forward_implications":["Organizations should give blind and low-vision software professionals dedicated time and resources to adapt tools and workflows, since creative problem-solving is a key part of their work.","Tool vendors should treat customizability and user-created solutions as first-class requirements, because real-world accessibility depends on end-user modification.","Open-source accessibility projects are not optional extras; they are the distribution channel through which BLVSPs get usable tools, such as screen-reader add-ons.","Teams should create channels for sharing accessibility solutions and feedback, and foster collaboration between BLVSPs and sighted colleagues.","Necessity-driven creativity can be self-reinforcing: solutions that restore independence motivate further creative problem-solving, so supporting early adaptations may compound benefits."],"supporting_citations":[{"why":"Supplies the prior interview dataset with 30 blind and low-vision software professionals that this paper re-analyzes through a creativity lens.","marker":"[15]"},{"why":"Supplies the componential model of creativity used to structure the thematic analysis and interpret motivation.","marker":"[17]"},{"why":"Supplies the notions of clever reuse and exploration that the paper applies to tool customization and workflow adaptation.","marker":"[23]"},{"why":"Documents inaccessible IDEs and programming tools, grounding the claim that creativity is needed for basic access.","marker":"[13]"},{"why":"Documents collaboration and programming barriers for people with visual impairments, supporting the necessity premise in shared work.","marker":"[12]"}],"fun_headline_variants":["Creativity is non-negotiable for blind devs","Blind software pros must innovate to do their job","Blind devs don't have the luxury of optimization","Creative problem-solving is baseline for blind coders","Blind programmers must build tools to work at all"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The study's central contrast with sighted peers assumes that sighted developers' creative problem-solving is mainly about optimization, yet no data from sighted developers were collected and no empirical baseline is cited to establish that; if sighted developers also create out of necessity, the contrast weakens even though the descriptive themes about BLVSPs remain.","fun_headline_variants_meta":{"raw":{"variants":["Creativity is non-negotiable for blind devs","Blind software pros must innovate to do their job","Blind devs don't have the luxury of optimization","Creative problem-solving is baseline for blind coders","Blind programmers must build tools to work at all"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000938,"raw_usage":{"total_tokens":3952,"prompt_tokens":825,"completion_tokens":3127,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":441,"completion_tokens_details":{"reasoning_tokens":3050}},"tokens_in":441,"tokens_out":3127,"duration_ms":19414,"temperature":1.0,"reasoning_tokens":3050,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-09T20:16:54.363280+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"A matched-sample study using the same interview protocol with sighted software professionals would settle the claim: if sighted developers report routinely creating or adapting tools to access standard features or complete routine tasks, rather than mainly to optimize, the essential-versus-optional distinction would fail.","supporting_citations":[{"cited_title":"The dynamic componential model of creativity and innovation in organizations: Making prog ress, making meaning,","cited_arxiv_id":null,"evidence_quote":"Supplies the componential model of creativity used to structure the thematic analysis and interpret motivation."},{"cited_title":"Developer pro ductivity for humans, part 8: Creativity in software engineering,","cited_arxiv_id":null,"evidence_quote":"Supplies the notions of clever reuse and exploration that the paper applies to tool customization and workflow adaptation."},{"cited_title":"An exploratory study of b lind software developers,","cited_arxiv_id":null,"evidence_quote":"Documents inaccessible IDEs and programming tools, grounding the claim that creativity is needed for basic access."}],"review_version":1}