Cited by 0Usability and User Interface DesignInnovative Human-Technology InteractionInteractive and Immersive Displays

Proceedings of the 37th Australian Conference on Human-Computer Interaction

·2025

AI snapshot

Written from the paper’s full text.

TL;DR

The authors built A11yGuide, a browser-based prototype presenting 592 reformulated accessibility requirements in simplified, categorised language, and evaluated it with eight undergraduate HCI students. Participants found the structure navigable (4.0/5) but only moderately clear (3.4/5), and simplified wording did not reliably convey a requirement's priority.

Key findings

  • Navigation was rated positively (M = 4.0/5) and content clarity moderately (M = 3.4/5, 1 = very easy to 5 = very difficult).
  • Locating tasks varied sharply: hearing-related requirements 100% success (0.00 clicks, 00:05), typography 62.5% (1.75 clicks, 00:55, 0.63 errors), photosensitivity 12.5% (2.13 clicks, 01:29, 1.25 errors) — the latter attributed to a German/English terminology mismatch ("Photosensibilität" vs. the English-labelled "Visual Impairments" section).
  • Reading tasks showed a clarity–priority disconnect: the most technically precise requirement (capital "H" spanning at least 0.7°) was rated hardest (clarity 4.00) yet 88% identified its priority correctly, while the headings/labels requirement (clarity 2.75) drew only 12.5% correct priority and the glare and audio requirements 0%.
  • Pre-session interviews: 7 of 8 gave a concrete definition of accessibility and all 8 expressed positive attitudes, but only 2 (P5, P8) had implemented formal accessibility requirements in projects; none used structured requirements-engineering techniques.

Methods

  • Formative, mixed-methods usability study with eight undergraduate HCI students (P1–P8, mostly 18–26, German-taught bachelor's programme), recruited via mailing lists, courses, and peer outreach; moderated remote sessions of ~30 minutes on Discord, each with a 10-minute pre-interview, a 10–15-minute thinking-aloud usability test, and a 5–10-minute post-interview.
  • The prototype was a static, read-only single-page web app (HTML, JavaScript, Tailwind CSS) using a local JSON dataset; content came from 11 documents selected from Kubullek et al.'s 31 standards, reformulated with Pohl and Rupp natural-language templates and organised into 10 main and 32 subcategories, with modal verbs (shall/should/will) signalling priority. The search function and an "Ask AI" item were non-functional placeholders.
  • Tasks comprised free exploration plus three scenario-based search tasks (typography, photosensitivity, hearing impairment) and four reading tasks. Quantitative metrics (task success, click count, time on task, errors, help requests, 5-point clarity ratings, priority estimates) were aggregated in Excel; qualitative data were analysed with a descriptive thematic summary inspired by Braun and Clarke.

Limitations

  • Stated: small, homogeneous sample (n = 8, all students under 30 in the same HCI bachelor's programme), so findings are not generalisable to other populations or professional settings; only 4 of the 592 requirements were evaluated in detail; prototype and dataset are not publicly available and lack documentation, metadata, and language variants for international reuse; no side-by-side comparison against the original standard wording, so gains in comprehensibility cannot be quantified; the prototype lacks source attribution for individual requirements; a single sentence template was applied uniformly.
  • Evident from the text: the evaluated version had no working search function despite participants repeatedly requesting one, and the mixed German/English labelling (German interface, partly English tooltips and category labels) directly caused navigation errors in Task 2.2.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1145/3764687

Cites

0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Claims the paper makes

13 of 65 cited sources checked · 2 supported · 0 flagged · accuracy not yet measured

  • Premisecitation
    § 1 Introduction · p. 1

    Many developers and designers find accessibility requirements difficult to interpret and apply due to their abstract language, dispersed sources, text-heavy nature, and lack of contextual examples.

    “Many developers and designers find accessibility requirements difficult to interpret and apply due to their abstract language, dispersed sources, text-heavy nature, and lack of contextual examples [5, 26].”
    Quote in the paperSubstantial claim1 of 2 sources checked
    • cites [5] [5] Tingting Bi, Xin Xia, David Lo, John Grundy, Thomas Zimmermann, and Denae Ford. 2022. Accessibility in Software Practice: A Practitioner's Perspective. ACM Trans. Softw. Eng. Methodol. 31, 4, Article 66 (July 2022), 26 pages. doi:10.1145/ 3503508 -

      Not checked in the free run.

    • cites [26] [26] Ann-Kathrin Kubullek and Aysegül Dogangün. 2023. Creating Accessibility 2.0 with Artificial Intelligence. In Proceedings of Mensch Und Computer 2023 (Rapperswil, Switzerland) (MuC '23) . Association for Computing Machinery, New York, NY, USA, 437-441. doi:10.1145/3603555.3608541 - source
  • Premisecitation
    § ACMReference Format: · p. 2

    These challenges also affect students and early-career professionals in HCI, who often encounter accessibility only briefly during their studies.

    “These challenges also affect students and early-career professionals in Human-Computer Interaction (HCI), who often encounter accessibility only briefly during their studies [17, 56, 59].”
    Quote in the paperSubstantial claim1 of 3 sources checked
    • cites [17] [17] Yasmine N. Elglaly, Catherine M. Baker, Anne Spencer Ross, and Kristen Shinohara. 2024. Beyond HCI: The Need for Accessibility Across the CS Curriculum. In Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1 (Portland, OR, USA) (SIGCSE 2024) . Association for Computing Machinery, New York, NY, USA, 324-330. doi:10.1145/3626252.3630788 - source

      The Introduction (page not provided) says accessibility is usually taught in HCI or design courses, if at all. Section 2.1 (page not provided) says few computing graduates have more than surface-level accessibility knowledge and that applicants for UI/UX roles often lack the needed skills. The paper does not specifically establish that HCI students or early-career HCI professionals often encounter accessibility only briefly during their studies. (LLM, conf=0.83)

      Experimental — accuracy not yet measured
    • cites [56] [56] Renata Vinadé and Sabrina Marczak. 2024. Educating for Accessibility: Insights into Knowledge Gaps and Practical Challenges in Software Engineering. In Proceedings of the XXIII Brazilian Symposium on Software Quality (SBQS '24) . Association for Computing Machinery, New York, NY, USA, 646-656. doi:10. 1145/3701625.3701689 - source
    • cites [59] [59] Qiwen Zhao, Vaishnavi Mande, Paula Conn, Sedeeq Al-khazraji, Kristen Shinohara, Stephanie Ludi, and Matt Huenerfauth. 2020. Comparison of Methods for Teaching Accessibility in University Computing Courses. In Proceedings of the 22nd International ACM SIGACCESS Conference on Computers and Accessibility (Virtual Event, Greece) (ASSETS '20) . Association for Computing Machinery, New York, NY, USA, Article 6, 12 pages. doi:10.1145/3373625.3417013 source
  • Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 2

    Many HCI and design students encounter accessibility only superficially.

    “Many HCI and design students encounter accessibility only superficially [17, 56, 59].”
    Quote in the paperNot a substantial claim1 of 3 sources checked
    • cites [17] [17] Yasmine N. Elglaly, Catherine M. Baker, Anne Spencer Ross, and Kristen Shinohara. 2024. Beyond HCI: The Need for Accessibility Across the CS Curriculum. In Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1 (Portland, OR, USA) (SIGCSE 2024) . Association for Computing Machinery, New York, NY, USA, 324-330. doi:10.1145/3626252.3630788 - source

      The Introduction says accessibility is usually placed in HCI and design courses, while §2.1 says few computing graduates understand it beyond the surface. The paper does not specifically say that many HCI and design students encounter accessibility only superficially; its statement about superficial understanding concerns computing graduates generally. (LLM, conf=0.83)

      Experimental — accuracy not yet measured
    • cites [56] [56] Renata Vinadé and Sabrina Marczak. 2024. Educating for Accessibility: Insights into Knowledge Gaps and Practical Challenges in Software Engineering. In Proceedings of the XXIII Brazilian Symposium on Software Quality (SBQS '24) . Association for Computing Machinery, New York, NY, USA, 646-656. doi:10. 1145/3701625.3701689 - source
    • cites [59] [59] Qiwen Zhao, Vaishnavi Mande, Paula Conn, Sedeeq Al-khazraji, Kristen Shinohara, Stephanie Ludi, and Matt Huenerfauth. 2020. Comparison of Methods for Teaching Accessibility in University Computing Courses. In Proceedings of the 22nd International ACM SIGACCESS Conference on Computers and Accessibility (Virtual Event, Greece) (ASSETS '20) . Association for Computing Machinery, New York, NY, USA, Article 6, 12 pages. doi:10.1145/3373625.3417013 source
  • Premisecitation
    § 6 Discussion · p. 13

    Accessibility is often underrepresented in design education.

    “Regarding students' prior knowledge, our findings support research showing that accessibility is often underrepresented in design education [17, 36, 38, 40, 42, 48, 52, 56].”
    Quote in the paperNot a substantial claim2 of 8 sources checked
    • cites [17] [17] Yasmine N. Elglaly, Catherine M. Baker, Anne Spencer Ross, and Kristen Shinohara. 2024. Beyond HCI: The Need for Accessibility Across the CS Curriculum. In Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1 (Portland, OR, USA) (SIGCSE 2024) . Association for Computing Machinery, New York, NY, USA, 324-330. doi:10.1145/3626252.3630788 - source

      The Introduction says computing programs place accessibility in HCI and design courses if they address it at all, and §4.1 says it has become part of some HCI and web design courses. These passages support limited coverage in computing education, but do not establish how often accessibility is underrepresented across design education more broadly. Page numbers are unavailable in our copy. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
    • cites [36] [36] Christian Meske, Florian Brachten, Ayseguel Doganguen, and Julia Hermann. 2025. Inclusive IT Design in Higher Education. In HCI International 2024 - Late Breaking Papers , Margherita Antona, Constantine Stephanidis, Qin Gao, and Jia Zhou (Eds.). Springer Nature Switzerland, Cham, 54-65. https://doi.org/10.1007/ 978-3-031-76818-7\_5 - source
    • cites [38] [38] Tamanna Motahar, Noelle Brown, Eliane Stampfer Wiese, and Jason Wiese. 2023. Building 'Design Empathy' for People with Disabilities: an Unsolved Challenge in HCI Education. In Proceedings of the 5th Annual Symposium on HCI Education (Hamburg, Germany) (EduCHI '23) . Association for Computing Machinery, New York, NY, USA, 68-71. doi:10.1145/3587399.3587409 - source

      Section 2 (page unavailable) says accessibility teaching interventions have had limited effects on students’ knowledge and calls for more directed interventions in HCI courses. Section 4.1 (page unavailable) says common approaches give students a shallow understanding of disabled people’s experiences. This supports a gap in how accessibility is taught, but the paper does not establish that accessibility is often underrepresented across design education. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
    • cites [40] [40] Anna Nishchyk and Weiqin Chen. 2018. Integrating Universal Design and Accessibility into Computer Science Curricula-A Review of Literature and Practices in Europe. Transforming our World Through Design, Diversity and Education 256 (2018), 56-66. -

      Not checked in the free run.

    • cites [42] [42] Rohan Patel, Pedro Breton, Catherine M. Baker, Yasmine N. El-Glaly, and Kristen Shinohara. 2020. Why Software is Not Accessible: Technology Professionals' Perspectives and Challenges. In Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems (Honolulu, HI, USA) (CHI EA '20) . Association for Computing Machinery, New York, NY, USA, 1-9. doi:10.1145/3334480.3383103 - source
    • cites [48] [48] Kristen Shinohara, Saba Kawas, Amy J. Ko, and Richard E. Ladner. 2018. Who Teaches Accessibility? A Survey of U.S. Computing Faculty. In Proceedings of the 49th ACM Technical Symposium on Computer Science Education (Baltimore, Maryland, USA) (SIGCSE '18) . Association for Computing Machinery, New York, NY, USA, 197-202. doi:10.1145/3159450.3159484 - source
    • cites [52] [52] Chia-En Tseng, Seoung Ho Jung, Yasmine N. Elglaly, Yudong Liu, and Stephanie Ludi. 2022. Exploration on Integrating Accessibility into an AI Course. In Proceedings of the 53rd ACM Technical Symposium on Computer Science Education - Volume 1 (Providence, RI, USA) (SIGCSE 2022) . Association for Computing Machinery, New York, NY, USA, 864-870. doi:10.1145/3478431.3499399 - source
    • cites [56] [56] Renata Vinadé and Sabrina Marczak. 2024. Educating for Accessibility: Insights into Knowledge Gaps and Practical Challenges in Software Engineering. In Proceedings of the XXIII Brazilian Symposium on Software Quality (SBQS '24) . Association for Computing Machinery, New York, NY, USA, 646-656. doi:10. 1145/3701625.3701689 - source
  • Findingown data
    § Abstract · p. 1

    The structured presentation improved the findability and comprehensibility of accessibility requirements.

    “Results indicate that the structured presentation improved the findability and comprehensibility of accessibility requirements, though participants noted issues with terminology, guidance, and visual hierarchy.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim. 41
  • May combine two claims. 55
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 2

    Typical barriers include fragmented standards and guidelines like WCAG, complex language, and a lack of accessible, pedagogically aligned tools.

    “Typical barriers include fragmented standards and guidelines like WCAG, complex language, and a lack of accessible, pedagogically aligned tools [5, 26, 42].”
    Quote in the paperNot a substantial claim1 of 3 sources checked
    • cites [5] [5] Tingting Bi, Xin Xia, David Lo, John Grundy, Thomas Zimmermann, and Denae Ford. 2022. Accessibility in Software Practice: A Practitioner's Perspective. ACM Trans. Softw. Eng. Methodol. 31, 4, Article 66 (July 2022), 26 pages. doi:10.1145/ 3503508 -

      Not checked in the free run.

    • cites [26] [26] Ann-Kathrin Kubullek and Aysegül Dogangün. 2023. Creating Accessibility 2.0 with Artificial Intelligence. In Proceedings of Mensch Und Computer 2023 (Rapperswil, Switzerland) (MuC '23) . Association for Computing Machinery, New York, NY, USA, 437-441. doi:10.1145/3603555.3608541 - source

      Section 2, “The Challenges of Implementing Accessibility” (page not provided), describes numerous standards and guidelines, including WCAG, and says their language is complex and difficult to understand. Sections 3 and 5 discuss accessibility limitations of AI tools and propose a tool to help developers, but they do not establish a lack of pedagogically aligned tools. (LLM, conf=0.87)

      Experimental — accuracy not yet measured
    • cites [42] [42] Rohan Patel, Pedro Breton, Catherine M. Baker, Yasmine N. El-Glaly, and Kristen Shinohara. 2020. Why Software is Not Accessible: Technology Professionals' Perspectives and Challenges. In Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems (Honolulu, HI, USA) (CHI EA '20) . Association for Computing Machinery, New York, NY, USA, 1-9. doi:10.1145/3334480.3383103 - source
  • May combine two claims.

    Premisecitation
    § 2.1 Defining and Implementing Accessibility · p. 2

    Existing resources and standards vary in reliability and usually require users to interpret and adapt the information on their own.

    “These vary in reliability and usually require users to interpret and adapt the information on their own [26, 27].”
    Quote in the paperSubstantial claim1 of 2 sources checked
    • cites [26] [26] Ann-Kathrin Kubullek and Aysegül Dogangün. 2023. Creating Accessibility 2.0 with Artificial Intelligence. In Proceedings of Mensch Und Computer 2023 (Rapperswil, Switzerland) (MuC '23) . Association for Computing Machinery, New York, NY, USA, 437-441. doi:10.1145/3603555.3608541 - source

      Section 2, “The Challenges of Implementing Accessibility” (page unavailable), says developers must review complex standards and identify requirements relevant to a specific application. This supports the need to interpret and adapt the information, but the paper does not say the resources or standards vary in reliability. (LLM, conf=0.85)

      Experimental — accuracy not yet measured
    • cites [27] [27] Ann-Kathrin Kubullek, Sebastian van Ledden, and Aysegül Dogangün. 2024. A Collection of Standards-based Recommendations for Sustainable, Social, Accessible Robots and Systems in Public Spaces - A Systematic Review and Derivation of Unified Equality Requirement Descriptions. In Proceedings of the 12th International Conference on Human-Agent Interaction (Swansea, United Kingdom) (HAI '24) . Association for Computing Machinery, New York, NY, USA, 305-313. doi:10.1145/3687272.3688294 - source
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 2

    E-commerce is a particularly relevant context for teaching digital accessibility, as many design and development students will likely work on web-based platforms such as online shops.

    “E-commerce is a particularly relevant context for teaching digital accessibility, as many design and development students will likely work on web-based platforms such as online shops [2, 7].”
    Quote in the paperNot a substantial claim1 of 2 sources checked
    • cites [2] [2] Patricia Acosta-Vargas, Belén Salvador-Acosta, Luis Salvador-Ullauri, and Janio Jadán-Guerrero. 2022. Accessibility challenges of e-commerce websites. PeerJ Computer Science 8 (2022), e891. - source

      The Introduction (page unavailable) says e-commerce websites have grown considerably and that applying accessibility guidelines to them is essential, supporting their relevance as an accessibility context. The paper does not address teaching digital accessibility or whether design and development students are likely to work on online shops. (LLM, conf=0.83)

      Experimental — accuracy not yet measured
    • cites [7] [7] U.S. Department of Labor Bureau of Labor Statistics. 2025. Occupational Outlook Handbook, Web Developers and Digital Designers. https://www.bls.gov/ooh/ computer-and-information-technology/web-developers.htm Accessed March 30, 2025. -

      Not checked in the free run.

  • May combine two claims.

    Premisecitation
    § ACMReference Format: · p. 2

    Accessibility is still underrepresented in many curricula, and even when it is addressed, it is rarely taught in an applied, example-based way.

    “Accessibility is still underrepresented in many curricula, and even when it is addressed, it is rarely taught in an applied, example-based way [17, 38, 40, 42, 48, 52, 56].”
    Quote in the paperSubstantial claim2 of 7 sources checked
    • cites [17] [17] Yasmine N. Elglaly, Catherine M. Baker, Anne Spencer Ross, and Kristen Shinohara. 2024. Beyond HCI: The Need for Accessibility Across the CS Curriculum. In Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1 (Portland, OR, USA) (SIGCSE 2024) . Association for Computing Machinery, New York, NY, USA, 324-330. doi:10.1145/3626252.3630788 - source

      The Introduction says most computing programs place accessibility in HCI or design courses, if they address it at all, supporting the claim that it is underrepresented. Section 4.2 discusses lectures, projects, games, and proposed programming assignments, but does not establish that applied, example-based teaching is rare when accessibility is taught. (LLM, conf=0.84)

      Experimental — accuracy not yet measured
    • cites [38] [38] Tamanna Motahar, Noelle Brown, Eliane Stampfer Wiese, and Jason Wiese. 2023. Building 'Design Empathy' for People with Disabilities: an Unsolved Challenge in HCI Education. In Proceedings of the 5th Annual Symposium on HCI Education (Hamburg, Germany) (EduCHI '23) . Association for Computing Machinery, New York, NY, USA, 68-71. doi:10.1145/3587399.3587409 - source

      Section 2 says existing accessibility lessons and interventions often fall short of building design empathy, supporting a concern about how accessibility is taught. It does not establish that accessibility is underrepresented across curricula or rarely taught through applied examples; the same section describes assignments and projects used to teach it. Page numbers were not available in our copy. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
    • cites [40] [40] Anna Nishchyk and Weiqin Chen. 2018. Integrating Universal Design and Accessibility into Computer Science Curricula-A Review of Literature and Practices in Europe. Transforming our World Through Design, Diversity and Education 256 (2018), 56-66. -

      Not checked in the free run.

    • cites [42] [42] Rohan Patel, Pedro Breton, Catherine M. Baker, Yasmine N. El-Glaly, and Kristen Shinohara. 2020. Why Software is Not Accessible: Technology Professionals' Perspectives and Challenges. In Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems (Honolulu, HI, USA) (CHI EA '20) . Association for Computing Machinery, New York, NY, USA, 1-9. doi:10.1145/3334480.3383103 - source
    • cites [48] [48] Kristen Shinohara, Saba Kawas, Amy J. Ko, and Richard E. Ladner. 2018. Who Teaches Accessibility? A Survey of U.S. Computing Faculty. In Proceedings of the 49th ACM Technical Symposium on Computer Science Education (Baltimore, Maryland, USA) (SIGCSE '18) . Association for Computing Machinery, New York, NY, USA, 197-202. doi:10.1145/3159450.3159484 - source
    • cites [52] [52] Chia-En Tseng, Seoung Ho Jung, Yasmine N. Elglaly, Yudong Liu, and Stephanie Ludi. 2022. Exploration on Integrating Accessibility into an AI Course. In Proceedings of the 53rd ACM Technical Symposium on Computer Science Education - Volume 1 (Providence, RI, USA) (SIGCSE 2022) . Association for Computing Machinery, New York, NY, USA, 864-870. doi:10.1145/3478431.3499399 - source
    • cites [56] [56] Renata Vinadé and Sabrina Marczak. 2024. Educating for Accessibility: Insights into Knowledge Gaps and Practical Challenges in Software Engineering. In Proceedings of the XXIII Brazilian Symposium on Software Quality (SBQS '24) . Association for Computing Machinery, New York, NY, USA, 646-656. doi:10. 1145/3701625.3701689 - source
  • May combine two claims.

    Premisecitation
    § 3.3 Intended Use Context and Language Choice · p. 5

    Domain-specific English terminology was considered more accurate and familiar to the target group, reducing the risk of misinterpretation.

    “Similar to observations by Vigh et al. (2025)[55], domain-specific English terminology was considered more accurate and familiar to the target group, reducing the risk of misinterpretation.”
    Quote in the paperSubstantial claim1 of 1 sources checked
    • cites Vigh et al. (2025)[55] source

      In the Introduction (page unavailable), Vigh et al. describe translations that lose context or leave room for interpretation, supporting the concern about misinterpretation. Our copy does not say that domain-specific English terminology was more accurate or familiar to a target group, or that using it reduced that risk. (LLM, conf=0.78)

      Experimental — accuracy not yet measured
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § 6 Discussion · p. 13

    The complexity, fragmentation, and abstract language of standards such as WCAG or ISO often hinder practical implementation.

    “The complexity, fragmentation, and abstract language of standards such as WCAG or ISO often hinder practical implementation [5, 26, 32].”
    Quote in the paperNot a substantial claim2 of 3 sources checked
    • cites [5] [5] Tingting Bi, Xin Xia, David Lo, John Grundy, Thomas Zimmermann, and Denae Ford. 2022. Accessibility in Software Practice: A Practitioner's Perspective. ACM Trans. Softw. Eng. Methodol. 31, 4, Article 66 (July 2022), 26 pages. doi:10.1145/ 3503508 -

      Not checked in the free run.

    • cites [26] [26] Ann-Kathrin Kubullek and Aysegül Dogangün. 2023. Creating Accessibility 2.0 with Artificial Intelligence. In Proceedings of Mensch Und Computer 2023 (Rapperswil, Switzerland) (MuC '23) . Association for Computing Machinery, New York, NY, USA, 437-441. doi:10.1145/3603555.3608541 - source
    • cites [32] [32] Aqueasha Martin-Hammond, Ulka Patil, and Barsa Tandukar. 2021. A Case for Making Web Accessibility Guidelines Accessible: Older Adult Content Creators and Web Accessibility Planning. In Proceedings of the 23rd International ACM SIGACCESS Conference on Computers and Accessibility (Virtual Event, USA) (ASSETS '21) . Association for Computing Machinery, New York, NY, USA, Article 34, 6 pages. doi:10.1145/3441852.3476472 - source

      The Introduction and §5.1 say accessibility guidance can be difficult for everyday content creators to understand and apply. Section 4.1 describes difficulty finding a comprehensive explanation in lay terms and the need to combine resources. The paper does not establish that WCAG or ISO standards themselves are fragmented, and it does not discuss ISO standards. (LLM, conf=0.87)

      Experimental — accuracy not yet measured
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingown data
    § Abstract · p. 1

    Several participants expressed interest in future features like AI-driven assistance.

    “Several expressed interest in future features like AI-driven assistance.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.2 First and Overall Impression of the Prototype · p. 10

    Participants' initial impressions of the prototype were generally positive, particularly in terms of its interface clarity and perceived role as a structured reference for accessibility requirements.

    “Participants' initial impressions of the prototype were generally positive, particularly in terms of its interface clarity and perceived role as a structured reference for accessibility requirements.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.1 Previous Knowledge, Curriculum Exposure and Attitudes Towards Accessibility · p. 10

    These tools were generally perceived as helpful, though not always fully reliable.

    “These were generally perceived as helpful, though not always fully reliable (P5: 'Quick and easy, but not always 100% accurate.').”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.2 First and Overall Impression of the Prototype · p. 10

    The minimalist visual design was praised for being distraction-free and readable, and the sidebar layout was frequently described as intuitive and well organised.

    “The minimalist visual design was praised for being distraction-free and readable (P1, P3, P6), and the sidebar layout was frequently described as intuitive and well organised (P6: 'Good overview on the left. Everything is clear so far' ).”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.1 Previous Knowledge, Curriculum Exposure and Attitudes Towards Accessibility · p. 10

    Formal methods for gathering accessibility requirements were largely absent in participants' previous practice; none of the students reported using structured requirements engineering techniques or dedicated accessibility guidelines.

    “Formal methods for gathering accessibility requirements were largely absent in participants' previous practice. None of the students reported using structured requirements engineering techniques or dedicated accessibility guidelines.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.3 Task Performance and Requirement Comprehension · p. 10

    Hearing-related terms were linguistically consistent across the interface and yielded perfect success.

    “In contrast, hearing-related terms were linguistically consistent across the interface and yielded perfect success.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.4 Perceived Strengths, Weaknesses and Improvement Suggestions · p. 11

    Participants identified challenges that limited the tool's effectiveness as a low-threshold orientation aid, including overly long or dense text blocks, difficulties with scanning and finding relevant sections quickly, and unclear distinction between interface elements such as glossary terms and hyperlinks.

    “At the same time, participants identified challenges that limited the tool's effectiveness as a low-threshold orientation aid. These included overly long or dense text blocks (P3, P4), difficulties with scanning and finding relevant sections quickly (P2), and unclear distinction between interface elements such as glossary terms and hyperlinks (P6).”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § 5.4 Perceived Strengths, Weaknesses and Improvement Suggestions · p. 11

    Several strengths were highlighted in the interviews: participants praised the clear navigation structure, the overall concept of structured accessibility information, and the integrated glossary support.

    “Several strengths were highlighted in the interviews. Participants praised the clear navigation structure, the overall concept of structured accessibility information, and the integrated glossary support.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    While the prototype was developed in German for contextual accessibility, untranslated tooltips and headings caused confusion.

    “While the prototype was developed in German for contextual accessibility, untranslated tooltips and headings caused confusion.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    The average clarity rating was 3.4 out of 5, suggesting moderate comprehensibility.

    “The average clarity rating was 3.4 out of 5 , suggesting moderate comprehensibility.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingreasoning
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    While participants correctly prioritised the technically difficult first requirement, the structurally simpler second requirement was often undervalued in importance.

    “While participants correctly prioritised the technically difficult first requirement, the structurally simpler second requirement was often undervalued in importance.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    While most users appreciated tooltips and simplified language, technical phrasing and domain-specific terminology occasionally required extra effort or external lookup.

    “While most users appreciated tooltips and simplified language, technical phrasing and domain-specific terminology occasionally required extra effort or external lookup (P2: 'If the app is intended for experts, they probably wouldn't struggle with the terminology.' ).”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingnone given
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    Everyday-relevant items, such as visual glare, were easier to grasp, and glossary-supported explanations were perceived as helpful.

    “Everyday-relevant items, such as visual glare, were easier to grasp, and glossary-supported explanations were perceived as helpful.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § 6 Discussion · p. 13

    Participants in this study noted difficulties with domain-specific terms and requested better structural and terminological support, even for reformulated requirements.

    “Participants in this study echoed these concerns, noting difficulties with domain-specific terms and requesting better structural and terminological support, even for reformulated requirements.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § 6 Discussion · p. 12

    Participants' prior knowledge, familiarity with terminology, and the structure of information significantly influenced task success and perceived comprehensibility.

    “While general attitudes toward inclusion and accessibility were consistently positive, participants' prior knowledge, familiarity with terminology, and the structure of information significantly influenced task success and perceived comprehensibility.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data
    § 6 Discussion · p. 11

    While students performed well on some locating tasks, others, especially the one related to photosensitivity, revealed significant challenges due to hybrid-language terminology.

    “While students performed well on some locating tasks, others, especially the one related to photosensitivity, revealed significant challenges due to hybrid-language terminology.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingown data
    § 5.4 Perceived Strengths, Weaknesses and Improvement Suggestions · p. 11

    Several participants expressed the need for more entry points and visual guidance, such as a dashboard, better menu subcategories, or illustrative examples.

    “In addition, several participants expressed the need for more entry points and visual guidance, such as a dashboard, better menu subcategories, or illustrative examples.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 6 Discussion · p. 11

    The tool was generally well received in terms of usability and structure (average navigation rating: 4.0/5), whereas clarity of content (average clarity rating: 3.4/5) varied depending on terminology and task context.

    “The results show that the tool was generally well received in terms of usability and structure (average navigation rating: 4.0/5), whereas clarity of content (average clarity rating: 3.4/5) varied depending on terminology and task context.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingnone given
    § 5.3 Task Performance and Requirement Comprehension · p. 10

    The typography task was moderately successful but occasionally affected by terminology unfamiliarity or inefficient strategies.

    “The typography task was moderately successful but occasionally affected by terminology unfamiliarity or inefficient strategies.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    Hybrid language use introduced challenges; in Task 2.2, several errors stemmed from mismatches between German input and English category labels.

    “However, hybrid language use introduced challenges. In Task 2.2, several errors stemmed from mismatches between German input and English category labels.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Findingnone given
    § 6.1 Limitations and Future Work · p. 13

    At present, neither the prototype nor the full set of 592 reformulated requirements are publicly available.

    “At present, neither the prototype nor the full set of 592 reformulated requirements are publicly available.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingown data
    § 6.1 Limitations and Future Work · p. 14

    Several participants recommended integrating a personalised AI assistant to adapt terminology explanations to users' background knowledge.

    “In addition, several participants recommended integrating a personalised AI assistant to adapt terminology explanations to users' background knowledge.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Findingown data
    § 6.1 Limitations and Future Work · p. 13

    Participants proposed several concrete design improvements, including a search function, a dashboard or homepage, collapsible content elements, visual examples, filtering options, and addressing terminology mismatches between German and English labels.

    “Participants also proposed several concrete design improvements, including a search function, a dashboard or homepage, collapsible content elements, visual examples, filtering options (e.g., by WCAG level or legal context), and addressing terminology mismatches between German and English labels, which had led to navigation errors and confusion.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Findingnone given
    § 6.1 Limitations and Future Work · p. 13

    The prototype currently lacks source attribution for individual requirements, with no indication of where a requirement originates from.

    “The prototype currently lacks source attribution for individual requirements.”
    • Also stated in: § 6.1 Limitations and Future Work · p. 13 · plain
      “Although it simplifies and reorganises content, there is no indication of where a requirement originates from.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingnone given
    § 6.1 Limitations and Future Work · p. 13

    The prototype includes 592 reformulated requirements.

    “Although the prototype includes 592 reformulated requirements, only four were evaluated in detail.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingown data
    § 6.1 Limitations and Future Work · p. 13

    Terminology mismatches between German and English labels had led to navigation errors and confusion.

    “Participants also proposed several concrete design improvements, including a search function, a dashboard or homepage, collapsible content elements, visual examples, filtering options (e.g., by WCAG level or legal context), and addressing terminology mismatches between German and English labels, which had led to navigation errors and confusion.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data
    § 6.1 Limitations and Future Work · p. 13

    Both the prototype and the full set of 592 reformulated requirements were developed for a German-language study context and currently lack documentation, metadata, and language variants needed for international reuse.

    “Both were developed for a German-language study context and currently lack documentation, metadata, and language variants needed for international reuse.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 3

    Practitioners struggle to identify which requirements are relevant to their projects and how to apply them effectively.

    “Practitioners struggle to identify which requirements are relevant to their projects and how to apply them effectively [5, 42].”
    Quote in the paperNot a substantial claim0 of 2 sources checked
    • cites [5] [5] Tingting Bi, Xin Xia, David Lo, John Grundy, Thomas Zimmermann, and Denae Ford. 2022. Accessibility in Software Practice: A Practitioner's Perspective. ACM Trans. Softw. Eng. Methodol. 31, 4, Article 66 (July 2022), 26 pages. doi:10.1145/ 3503508 -

      Not checked in the free run.

    • cites [42] [42] Rohan Patel, Pedro Breton, Catherine M. Baker, Yasmine N. El-Glaly, and Kristen Shinohara. 2020. Why Software is Not Accessible: Technology Professionals' Perspectives and Challenges. In Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems (Honolulu, HI, USA) (CHI EA '20) . Association for Computing Machinery, New York, NY, USA, 1-9. doi:10.1145/3334480.3383103 - source
  • Probably not a substantial claim: may not pass S2 (checkable).

    Interpretationreasoning
    § ACMReference Format: · p. 2

    There is a growing need for resources that present accessibility requirements in a way that makes them easier to understand and locate, especially for students working on design and development tasks.

    “As a result, there is a growing need for resources that present accessibility requirements in a way that makes them easier to understand and locate, especially for students working on design and development tasks.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 3

    Time, staffing, and tooling constraints often deprioritise accessibility, and managers frequently overestimate their teams' accessibility performance.

    “Time, staffing, and tooling constraints often deprioritise accessibility. Managers frequently overestimate their teams' accessibility performance [1].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [1] [1] [Level Access. 2023. State of Digital Accessibility Report 2023-2024. https://www.levelaccess.com/wp-content/uploads/2023/12/The-Fifth-AnnualState-of-Digital-Accessibility-Report.pdf](https://www.levelaccess.com/wp-content/uploads/2023/12/The-Fifth-Annual-State-of-Digital-Accessibility-Report.pdf) -

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Interpretationreasoning
    § 2.3 Existing Tools for Accessing Accessibility Requirements · p. 3

    Existing tools for accessibility requirements offer important entry points but fall short in addressing key needs for educational settings: clear structuring, consistent terminology, and scaffolding that connects technical rules to practical relevance.

    “These tools offer important entry points into accessibility requirements but fall short in addressing key needs for educational settings: clear structuring, consistent terminology, and scaffolding that connects technical rules to practical relevance.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § 2.1 Defining and Implementing Accessibility · p. 2

    A review by Freire et al. found that most documented techniques were guideline-driven, reinforcing the dominance of standards-based implementation.

    “A review by Freire et al. found that most documented techniques were guideline-driven, reinforcing the dominance of standards-based implementation [19].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [19] [19] Andre Pimenta Freire, Rudinei Goularte, and Renata Pontin de Mattos Fortes. 2007. Techniques for developing more accessible web applications: a survey towards a process classification. In Proceedings of the 25th Annual ACM International Conference on Design of Communication (El Paso, Texas, USA) (SIGDOC '07) . Association for Computing Machinery, New York, NY, USA, 162-169. doi:10. 1145/1297144.1297177 - source
  • May combine two claims.

    Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 3

    Even professional websites often fail to meet basic accessibility requirements; according to WebAIM's 2025 audit of one million homepages, 94.8% contained WCAG violations.

    “According to WebAIM's 2025 audit of one million homepages, 94.8% contained WCAG violations [58].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [58] [58] WebAIM. 2025. The 2025 report on the accessibility of the top 1,000,000 home pages. https://webaim.org/projects/million/ -

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Interpretationnone given
    § 2.5 Positioning Our Work · p. 4

    Existing tools often focus on compliance validation or offer static checklists with limited contextual support, creating barriers for students and novice practitioners.

    “Existing tools often focus on compliance validation or offer static checklists with limited contextual support. This creates barriers for students and novice practitioners who need accessible, structured entry points into the complex landscape of standards and guidelines.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation
    § 2.1 Defining and Implementing Accessibility · p. 2

    User-centred evaluation and expert consulting can reveal real-world barriers, but these methods demand time, expertise, and careful planning, and are not always accessible to novices.

    “Involving users with disabilities through usability testing or expert reviews can reveal real-world barriers [37]. However, these methods demand time, expertise, and careful planning, and are not always accessible to novices.”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [37] [37] Darliane Miranda and João Araujo. 2022. Studying industry practices of accessibility requirements in agile development. In Proceedings of the 37th ACM/SIGAPP Symposium on Applied Computing (Virtual Event) (SAC '22) . Association for Computing Machinery, New York, NY, USA, 1309-1317. doi:10.1145/3477314.3507041 - source
  • May combine two claims.

    Premisecitation
    § 2.2 Teaching and Practicing Accessibility in HCI Education · p. 3

    Formal accessibility education remains rare and often lacks practical depth; retention is low without hands-on application.

    “Formal accessibility education remains rare and often lacks practical depth. Where it exists, retention is low without hands-on application [36, 37, 59].”
    Quote in the paperNot a substantial claim0 of 3 sources checked
    • cites [36] [36] Christian Meske, Florian Brachten, Ayseguel Doganguen, and Julia Hermann. 2025. Inclusive IT Design in Higher Education. In HCI International 2024 - Late Breaking Papers , Margherita Antona, Constantine Stephanidis, Qin Gao, and Jia Zhou (Eds.). Springer Nature Switzerland, Cham, 54-65. https://doi.org/10.1007/ 978-3-031-76818-7\_5 - source
    • cites [37] [37] Darliane Miranda and João Araujo. 2022. Studying industry practices of accessibility requirements in agile development. In Proceedings of the 37th ACM/SIGAPP Symposium on Applied Computing (Virtual Event) (SAC '22) . Association for Computing Machinery, New York, NY, USA, 1309-1317. doi:10.1145/3477314.3507041 - source
    • cites [59] [59] Qiwen Zhao, Vaishnavi Mande, Paula Conn, Sedeeq Al-khazraji, Kristen Shinohara, Stephanie Ludi, and Matt Huenerfauth. 2020. Comparison of Methods for Teaching Accessibility in University Computing Courses. In Proceedings of the 22nd International ACM SIGACCESS Conference on Computers and Accessibility (Virtual Event, Greece) (ASSETS '20) . Association for Computing Machinery, New York, NY, USA, Article 6, 12 pages. doi:10.1145/3373625.3417013 source
  • May combine two claims.

    Premisecitation
    § 2.4 Broader Trends in Accessibility Research · p. 3

    AI-powered accessibility checkers like WAVE, axe, and Microsoft Accessibility Insights help identify common accessibility issues and offer automated feedback, but their usefulness for beginners remains limited because they assume prior knowledge, provide little context, and do not improve the clarity or structure of the underlying requirements.

    “Accessibility Checkers like WAVE, axe, and Microsoft Accessibility Insights 5 help identify common accessibility issues and offer automated feedback [50, 54]. However, their usefulness for beginners remains limited: they assume prior knowledge, provide little context, and do not improve the clarity or structure of the underlying requirements.”
    Quote in the paperNot a substantial claim0 of 2 sources checked
    • cites [50] [50] Statista. 2024. Number of artificial intelligence (AI) tool users globally from 2020 to 2030. https://www.statista.com/forecasts/1449844/ai-tool-users-worldwide -

      Not checked in the free run.

    • cites [54] [54] Stanford University. 2024. Artificial Intelligence Index Report 2024. -

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S4 (based). May combine two claims.

    Interpretationnone given
    § 2.5 Positioning Our Work · p. 4

    While many existing tools prioritise implementation checks, few focus on comprehension and relevance estimation before design decisions are made.

    “While many existing tools prioritise implementation checks, few focus on comprehension and relevance estimation before design decisions are made.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Premisecitation
    § ACMReference Format: · p. 2

    Many students lack structured opportunities to work with accessibility requirements in applied contexts, and their practical skills in this area are limited despite a generally high awareness of its importance.

    “Consequently, many students lack structured opportunities to work with accessibility requirements in applied contexts, and studies show that their practical skills in this area are limited despite a generally high awareness of its importance [56].”
    Quote in the paperSubstantial claim0 of 1 sources checked
    • cites [56] [56] Renata Vinadé and Sabrina Marczak. 2024. Educating for Accessibility: Insights into Knowledge Gaps and Practical Challenges in Software Engineering. In Proceedings of the XXIII Brazilian Symposium on Software Quality (SBQS '24) . Association for Computing Machinery, New York, NY, USA, 646-656. doi:10. 1145/3701625.3701689 - source
  • Probably not a substantial claim: may not pass S4 (based).

    Interpretationnone given
    § 2.5 Positioning Our Work · p. 4

    Despite growing awareness and legal pressure, accessibility implementation remains fragmented, particularly when it comes to locating and interpreting requirements in early-stage design.

    “Despite growing awareness and legal pressure, accessibility implementation remains fragmented, particularly when it comes to locating and interpreting requirements in early-stage design.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § 3.5 Developing the Content: Requirement Collection, Rewriting and Structuring · p. 5

    Natural language templates adapted from Pohl and Rupp are widely used in requirements engineering to increase consistency and readability.

    “We applied natural language templates adapted from Pohl and Rupp [45], which are widely used in requirements engineering (RE) to increase consistency and readability.”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites Pohl and Rupp [45] [45] Klaus Pohl and Chris Rupp. 2011. Requirements Engineering Fundamentals: A Study Guide for the Certified Professional for Requirements Engineering Exam Foundation Level - IREB compliant . Rocky Nook, Santa Barbara, CA. -

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Study design and conductnone given
    § 4.5 Data Analysis · p. 8

    Partial transcripts were compiled manually by authors two and three, who independently reviewed the sessions and initially identified recurring patterns.

    “Partial transcripts were compiled manually by authors two and three, who independently reviewed the sessions and initially identified recurring patterns.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Study design and conductreasoning
    § 3.3 Intended Use Context and Language Choice · p. 5

    The prototype was developed and evaluated in German to ensure accessibility for the target user group and to avoid unnecessary comprehension barriers during testing.

    “The prototype was developed and evaluated in German to ensure accessibility for the target user group (undergraduate HCI students in Germany) and to avoid unnecessary comprehension barriers during testing.”
    Quote in the paperSubstantial claim
    • The authors state this as an assumption: The English tooltips would not significantly impair comprehension for the academic target group.
  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Study design and conductnone given
    § 4.1 Study Design and Setup · p. 7

    The study complied with applicable ethical and data protection standards.

    “The study complied with applicable ethical and data protection standards.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductnone given
    § 4.1 Study Design and Setup · p. 7

    Eight undergraduate HCI students (P1-P8) participated in moderated, remote sessions via Discord.

    “Eight undergraduate HCI students (P1-P8) participated in moderated, remote sessions via the Discord 9 platform, enabling screen sharing and verbal protocol collection.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Study design and conductnone given
    § 4.1 Study Design and Setup · p. 7

    No personal data were collected or stored.

    “No personal data were collected or stored.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationown data
    § 5.1 Previous Knowledge, Curriculum Exposure and Attitudes Towards Accessibility · p. 10

    The limited integration of accessibility requirements was not due to disinterest, but rather a combination of structural and perceptual barriers: low awareness of formal standards, insufficient curricular emphasis on accessibility, and a perceived lack of relevance for typical design scenarios.

    “This limited integration of accessibility requirements was not due to disinterest, but rather a combination of structural and perceptual barriers: (1) low awareness of formal standards, (2) insufficient curricular emphasis on accessibility, and (3) a perceived lack of relevance for typical design scenarios.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Interpretationown data
    § Abstract · p. 1

    The prototype suggests that accessible presentation of requirements can support early engagement with accessibility and serve as a low-threshold entry point in applied HCI projects.

    “While not a comprehensive educational tool, the prototype suggests that accessible presentation of requirements can support early engagement with accessibility and serve as a low-threshold entry point in applied HCI projects.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Premisecitation
    § 4.3 Tasks · p. 8

    According to recent WebAIM statistics, online shopping websites exhibit the highest average number of accessibility errors across industry sectors (71.2 errors per page on average), significantly above the general benchmark of 51.

    “According to recent WebAIM statistics [58], online shopping websites exhibit the highest average number of accessibility errors across industry sectors (71.2 errors per page on average), significantly above the general benchmark of 51.”
    Quote in the paperSubstantial claim0 of 1 sources checked
    • cites WebAIM statistics [58]

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductnone given
    § 4.1 Study Design and Setup · p. 7

    Participants could withdraw at any point without consequence.

    “Participants could withdraw at any point without consequence.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Study design and conductnone given
    § 4.1 Study Design and Setup · p. 7

    All participants were informed about the study purpose and voluntarily consented to take part.

    “All participants were informed about the study purpose and voluntarily consented to take part.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim.

    Study design and conductnone given
    § 4.2 Participant Profile · p. 8

    Participants were purposefully selected to reflect the intended user group of the tool: undergraduate HCI students with varying levels of prior experience in web development and digital accessibility.

    “They were purposefully selected to reflect the intended user group of the tool: undergraduate HCI students with varying levels of prior experience in web development and digital accessibility.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Interpretationnone given
    § 3.3 Intended Use Context and Language Choice · p. 5

    The prototype was specifically developed for use in a controlled study context and is not optimised for broader deployment or curricular integration at this stage.

    “The prototype was specifically developed for use in a controlled study context and is not optimised for broader deployment or curricular integration at this stage.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductnone given
    § 4.5 Data Analysis · p. 8

    Emerging themes were discussed iteratively with the other authors and reviewed in several alignment meetings to ensure consistency and plausibility, with discrepancies resolved through consensus.

    “Emerging themes (e.g., 'navigation strategies', 'requirement clarity', 'terminology issues') were discussed iteratively with the other authors and reviewed in several alignment meetings to ensure consistency and plausibility. Discrepancies were resolved through consensus.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Interpretationown data
    § 5.1 Previous Knowledge, Curriculum Exposure and Attitudes Towards Accessibility · p. 10

    Although participants generally held positive attitudes towards inclusive design, they often lacked both exposure and guided access to applicable accessibility knowledge, underscoring the value of low-threshold, example-based tools like the prototype A11yGuide for helping HCI students understand and locate accessibility requirements in early design phases.

    “These findings suggest that although participants generally held positive attitudes towards inclusive design, they often lacked both exposure and guided access to applicable accessibility knowledge, underscoring the value of low-threshold, example-based tools like our prototype A11yGuide for helping HCI students understand and locate accessibility requirements in early design phases.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim.

    Study design and conductcitation
    § 4.5 Data Analysis · p. 8

    Qualitative data were analysed using a descriptive thematic summary approach inspired by Braun and Clarke's reflexive thematic analysis.

    “Qualitative data, including verbal statements from the thinkingaloud protocol and responses from post-session interviews, were analysed using a descriptive thematic summary approach inspired by Braun and Clarke's reflexive thematic analysis [6].”
    Quote in the paperSubstantial claim0 of 1 sources checked
    • cites Braun and Clarke [6] [6] Virginia Braun and Victoria Clarke. 2006. Using thematic analysis in psychology. Qualitative research in psychology 3, 2 (2006), 77-101. - source
  • Probably not a substantial claim: may not pass S2 (checkable). May combine two claims.

    Interpretationown data
    § 6 Discussion · p. 11

    These findings underscore the importance of domain scaffolding, consistent terminology, and contextual design support.

    “These findings underscore the importance of domain scaffolding, consistent terminology, and contextual design support.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationreasoning
    § 5.3 Task Performance and Requirement Comprehension · p. 10

    These usability issues are not only indicative of interface friction, but may also reflect broader gaps in participants' conceptual understanding of accessibility domains.

    “These usability issues are not only indicative of interface friction, but may also reflect broader gaps in participants' conceptual understanding of accessibility domains.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S2 (checkable). May combine two claims.

    Interpretationreasoning
    § 6 Discussion · p. 13

    Comprehension alone may not be sufficient; educational tools must also help users understand the rationale behind accessibility measures.

    “Our results suggest that comprehension alone may not be sufficient - educational tools must also help users understand the rationale behind accessibility measures.”
    Quote in the paperNot a substantial claim
  • Classified as probably not a substantial claim.

    Premisecitation
    § 6 Discussion · p. 13

    Scaffolding strategies that frame both the 'how' and the 'why' of accessibility are advocated by pattern-based or example-driven approaches.

    “This reinforces the case for scaffolding strategies that frame both the 'how' and the 'why' of accessibility, as advocated by pattern-based or example-driven approaches [12].”
    Quote in the paperSubstantial claim0 of 1 sources checked
    • cites [12] [12] Cristian Bernareggi Daniela Fogli, Loredana Parasiliti Provenza. 2010. A design pattern language for accessible web sites. In Proceedings of the International Conference on Advanced Visual Interfaces (Roma, Italy) (AVI '10) . Association for Computing Machinery, New York, NY, USA, 307-310. doi:10.1145/1842993. 1843048 - source
  • Probably not a substantial claim: may not pass S2 (checkable). May combine two claims.

    Interpretationown data
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    These results underscore the importance of consistent terminology, intuitive category labelling, and accessible language, especially in tools designed for novice users with limited domain knowledge.

    “These results underscore the importance of consistent terminology, intuitive category labelling, and accessible language, especially in tools designed for novice users with limited domain knowledge.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationreasoning
    § 5.2 First and Overall Impression of the Prototype · p. 10

    Although only one participant explicitly said they would recommend the prototype to peers, the overall feedback suggests that its design and structure offer strong potential to support requirement access and exploration, especially in educational or early-phase design contexts.

    “Although only one participant explicitly said they would recommend the prototype to peers, the overall feedback suggests that its design and structure offer strong potential to support requirement access and exploration, especially in educational or early-phase design contexts.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Interpretationreasoning
    § 5.4 Perceived Strengths, Weaknesses and Improvement Suggestions · p. 11

    The feedback points to concrete design and content improvements that could increase accessibility and reduce effort when retrieving and interpreting requirements.

    “The feedback points to concrete design and content improvements that could increase accessibility and reduce effort when retrieving and interpreting requirements.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationreasoning
    § 5.3 Task Performance and Requirement Comprehension · p. 11

    This limited experience may explain why priority estimation was inconsistent despite clear wording, and why structural or abstract requirements were occasionally misunderstood or underestimated.

    “This limited experience may explain why priority estimation was inconsistent despite clear wording, and why structural or abstract requirements were occasionally misunderstood or underestimated.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim.

    Study design and conductnone given
    § 6.1 Limitations and Future Work · p. 13

    All reading tasks used rewritten content tailored for novice users, focusing on reduced complexity, clearer phrasing, and embedded examples.

    “All reading tasks used rewritten content tailored for novice users, focusing on reduced complexity, clearer phrasing, and embedded examples.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).

    Interpretationreasoning
    § 6.1 Limitations and Future Work · p. 13

    Differences in web development experience may have influenced clarity ratings and task success, particularly in reading tasks requiring prior technical knowledge.

    “Differences in web development experience may have influenced clarity ratings and task success, particularly in reading tasks requiring prior technical knowledge.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Study design and conductown data
    § 6.1 Limitations and Future Work · p. 13

    The study focused on a small and relatively homogeneous sample of 8 participants, all students under 30 enrolled in the same HCI-related bachelor's program.

    “The study focused on a small and relatively homogeneous sample ( 𝑛 = 8), all of whom were students under 30 enrolled in the same HCI-related bachelor's program.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: The sample size is in line with typical qualitative usability and comprehension studies in HCI.
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Study design and conductcitation
    § 6.1 Limitations and Future Work · p. 13

    The sentence template used in reading tasks was adapted from Pohl and Rupp and applied uniformly.

    “The sentence template used in reading tasks was adapted from Pohl and Rupp and applied uniformly.”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites Pohl and Rupp

      Couldn’t be matched to a paper in Crossref, so it can’t be checked.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation
    § 6 Discussion · p. 13

    Lecture-based exposure alone does not ensure long-term competence in accessibility.

    “This echoes findings that lecture-based exposure alone does not ensure long-term competence in accessibility [59].”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [59] [59] Qiwen Zhao, Vaishnavi Mande, Paula Conn, Sedeeq Al-khazraji, Kristen Shinohara, Stephanie Ludi, and Matt Huenerfauth. 2020. Comparison of Methods for Teaching Accessibility in University Computing Courses. In Proceedings of the 22nd International ACM SIGACCESS Conference on Computers and Accessibility (Virtual Event, Greece) (ASSETS '20) . Association for Computing Machinery, New York, NY, USA, Article 6, 12 pages. doi:10.1145/3373625.3417013 source
  • Classified as probably not a substantial claim. May combine two claims.

    Interpretationreasoning
    § 6.1 Limitations and Future Work · p. 13

    The findings are not intended to be generalised to other populations or professional settings, but offer targeted insights for similar learning environments.

    “While findings are therefore not intended to be generalised to other populations or professional settings, they offer targeted insights for similar learning environments.”
    Quote in the paperSubstantial claim
    • Rests on an assumption: The prototype's intended user group is students under 30 enrolled in the same HCI-related bachelor's program.
  • Classified as probably not a substantial claim.

    Interpretationreasoning
    § 6.1 Limitations and Future Work · p. 13

    The sentence template may not be optimal for all types of content.

    “While this showed promise, it may not be optimal for all types of content.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S2 (checkable).

    Interpretationreasoning
    § 7 Conclusion · p. 14

    Prototypes like the one presented here can complement educational efforts by making standards more approachable and actionable.

    “Prototypes like the one presented here can complement educational efforts by making standards more approachable and actionable.”
    Quote in the paperNot a substantial claim
    • Rests on an assumption: Global accessibility legislation continues to evolve.
    • Rests on an assumption: The ability to engage with technical requirements is becoming an essential design skill.
  • May combine two claims.

    Interpretationown data
    § 7 Conclusion · p. 14

    The prototype improved navigation and terminology support, helping participants locate relevant standards more efficiently.

    “The prototype improved navigation and terminology support, helping participants locate relevant standards more efficiently.”
    Quote in the paperSubstantial claim
79 of 79
  • The authors state this as an assumption.

    The English tooltips would not significantly impair comprehension for the academic target group.

    “Given the brevity and familiarity of these terms for the academic target group, we assumed that comprehension would not be significantly impaired.”
  • The paper relies on this without support.

    The 11 selected standards and guidelines are applicable to the inclusive online webshop use case.

    “From these, 11 documents applicable to our fictional use case scenario (an inclusive online webshop) were selected (see additional material).”
  • The paper relies on this without support.

    The natural language templates adapted from Pohl and Rupp are suitable for documenting accessibility requirements.

    “We applied natural language templates adapted from Pohl and Rupp [45], which are widely used in requirements engineering (RE) to increase consistency and readability.”
  • The paper relies on this without support.

    The prototype's intended user group is students under 30 enrolled in the same HCI-related bachelor's program.

    “This matches the prototype's intended user group and enabled in-depth exploration of interpretation strategies and perceived barriers in a relevant educational context.”
  • The paper relies on this without support.

    The sample size is in line with typical qualitative usability and comprehension studies in HCI.

    “The sample size is in line with typical qualitative usability and comprehension studies in HCI.”
  • The paper relies on this without support.

    Global accessibility legislation continues to evolve.

    “As global accessibility legislation continues to evolve, the ability to engage with technical requirements is becoming an essential design skill.”
  • The paper relies on this without support.

    The ability to engage with technical requirements is becoming an essential design skill.

    “As global accessibility legislation continues to evolve, the ability to engage with technical requirements is becoming an essential design skill.”
  • The paper relies on this without support.

    Institutions are still shaping policies on AI use in teaching and assessment, ranging from explicit prohibitions to exploratory guidelines for responsible integration.

    “While potentially valuable, this also points to a broader tension in higher education, where institutions are still shaping policies on AI use in teaching and assessment-ranging from explicit prohibitions to exploratory guidelines for responsible integration.”
8 of 8

Cites

The publisher hasn’t deposited this paper’s reference list.

Research works printed but not linked: 7

  1. [5][5] Tingting Bi, Xin Xia, David Lo, John Grundy, Thomas Zimmermann, and Denae Ford. 2022. Accessibility in Software Practice: A Practitioner's Perspective. ACM Trans. Softw. Eng. Methodol. 31, 4, Article 66 (July 2022), 26 pages. doi:10.1145/ 3503508 -
  2. [9][9] A. Chaboryk. 2025. Easy-to-follow steps for beginners to review website accessibility. https://sa11y.netlify.app/ -
  3. [24][24] [Klarna. 2022. Shopping Pulse. https://www.klarna.com/international/press/ klarna-shopping-pulse-zwei-von-drei-deutschen-bevorzugen-den-einkaufim-laden/](https://www.klarna.com/international/press/klarna-shopping-pulse-zwei-von-drei-deutschen-bevorzugen-den-einkauf-im-laden/) -
  4. [28][28] Jonathan Lazar, Jinjuan Heidi Feng, and Harry Hochheiser. 2017. Research methods in human-computer interaction . Morgan Kaufmann, Burlington, Massachusetts. -
  5. [39][39] Jakob Nielsen. 1994. Usability engineering . Morgan Kaufmann, Burlington, Massachusetts. -
  6. [40][40] Anna Nishchyk and Weiqin Chen. 2018. Integrating Universal Design and Accessibility into Computer Science Curricula-A Review of Literature and Practices in Europe. Transforming our World Through Design, Diversity and Education 256 (2018), 56-66. -
  7. [43][43] Jeff Patton. 2015. User story mapping: Die Technik für besseres Nutzerverständnis in der agilen Produktentwicklung . O'Reilly Media, Sebastopol, California. -

Publisher
ACM
Published
2025-11-28
OpenAlex
W4416237042
Cited by
0
References
0
Type
paratext
Open access
closed
Topics
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
  • Physical Sciences › Computer Science › Human-Computer Interaction › Innovative Human-Technology Interaction
  • Physical Sciences › Computer Science › Human-Computer Interaction › Interactive and Immersive Displays
Keywords
human-computer interaction

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.

Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-25.

Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-25.

Cited sources are checked by gpt-6-sol.

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