## Appendix A Full Questionnaire (Updated Version--60 Questions)
### Test Debt--Questions 48 to 54
#### Accessibility Debt--Questions 58 to 60  
Question 58: Have you conducted usability testing to identify and address potential barriers in the platform setup process?  
Stakeholder: Organizers  
Score: 5  
Justification: Conducting usability testing is critical to uncover and address accessibility issues that can impede participants' engagement. By identifying these barriers early, organizers can make necessary adjustments to enhance the platform's usability and ensure a smooth user experience.  
Example: If usability testing reveals that participants struggle with the initial setup due to unclear instructions, organizers can simplify the process and provide more intuitive guidance, thereby reducing Accessibility Debt and improving participant retention.  
Question 59: Have you implemented adaptive user interfaces that tailor the setup experience based on participants' skill levels and preferences?  
Stakeholder: OrganizersJustification: Implementing adaptive user interfaces can greatly improve usability by customizing the setup experience according to each participant's skill level and preferences. A personalized approach minimizes user frustration and enhances engagement by delivering guidance and support that align with individual needs and levels of expertise.  
Example: For instance, a novice user might benefit from a simplified setup path with additional explanations and contextual help, whereas a more experienced participant could be offered a faster, less guided version. This differentiation fosters a more positive onboarding experience and helps reduce drop-off due to unnecessary complexity.  
Question 60: Have you implemented feedback mechanisms that allow participants to report accessibility issues and suggest improvements?  
Stakeholder: Organizers  
Score: 3  
Justification: The implementation of feedback mechanisms by the organizers enables continuous improvement of the platform, based on the direct input of users. By proactively responding to participant requests and suggestions, they are able to resolve issues more effectively and enhance the overall usability of the platform.  
Example: If participants can easily report setup difficulties or suggest enhancements, organizers can quickly implement changes, thereby minimizing Accessibility Debt and fostering a more user-friendly environment.  
\begin{table}
\begin{tabular}{c c c c} \hline
**Source Debt Type** & **Affected Debt Type(s)** & **Relationship Type** & **Explanation** \\ \hline Documentation Debt & Accessibility Debt & Causal & Lack of clear or multilingual documentation hinders access for non-native or novice users. Poor infrastructure restricts the deployment, scalability, and integrity of models and data. Opaque or informal processes often lead to versioning inconsistencies and traceability loss. \\ Test Debt & Defect Debt & Amplifying & Insufficient testing increases the likelihood of undetected bugs or model failures. \\ \hline \end{tabular}
\end{table}
Table 2: Inter-rater agreement matrix: technical debt labeling for 30 papers cause–effect relationships between selected technical debt types.