Download to read offline
Uploaded byDamian T. Gordon
A CheckSheet for Inclusive Software Design
A CheckSheet for Inclusive Software Design
More Related Content
Similar to A CheckSheet for Inclusive Software Design
More from Damian T. Gordon
A CheckSheet for Inclusive Software Design
- 1. 08/04/25 Damian Gordon8/04/25 p. 1 Inclusive Software Design A task sheet for students to work through several times and hopefully then internalise. Evaluation criteria Notes Have we considered the needs of users from different cultural, linguistic, and social backgrounds? User Diversity and Representation (ISO 26000, ISO 42001) Have we involved people with lived experience or marginalized voices in the design process? User Diversity and Representation (ISO 26000, ISO 42001) Does the product avoid reinforcing stereotypes or harmful norms? User Diversity and Representation (ISO 26000, ISO 42001) Is the software accessible to users with disabilities (visual, auditory, cognitive, motor)? Accessibility and Usability (ISO/IEC 29138, WCAG Guidelines) Have we tested with screen readers, alternative input methods, and different language settings? Accessibility and Usability (ISO/IEC 29138, WCAG Guidelines) Are usability heuristics inclusive and supportive for novice and expert users alike? Accessibility and Usability (ISO/IEC 29138, WCAG Guidelines) Is the language used in the interface simple, inclusive, and non-discriminatory? Language and Communication (ISO/IEC 25010, ISO 26000) Can users switch to different languages or localize the content easily? Language and Communication (ISO/IEC 25010, ISO 26000) Are tone, terminology, and metaphors respectful across cultural contexts? Language and Communication (ISO/IEC 25010, ISO 26000) Have we checked for bias or underrepresentation in our data sources? Inclusive Data and Design Assumptions (ISO/IEC 42001, TR 24028) Are edge cases (e.g., non-binary identities, indigenous communities) explicitly considered? Inclusive Data and Design Assumptions (ISO/IEC 42001, TR 24028) Have we avoided assuming a ‘default’ user profile? Inclusive Data and Design Assumptions (ISO/IEC 42001, TR 24028) Have end-users been involved in defining problems and testing solutions? Collaborative and Participatory Design (ISO 26000, Human-Centred Design) Is there a mechanism for user feedback from all groups, not just dominant voices? Collaborative and Participatory Design (ISO 26000, Human-Centred Design) Are co-design or participatory methods used where feasible? Collaborative and Participatory Design (ISO 26000, Human-Centerer Design) Can users understand how the system works and how decisions are made? Transparency and Trust (ISO/IEC 42001, ISO 26000) Are data use, terms, and system limitations clearly communicated? Transparency and Trust (ISO/IEC 42001, ISO 26000) Do users have control over their settings and information? Transparency and Trust (ISO/IEC 42001, ISO 26000) Can the software run effectively on low-spec or older devices? Environment and Digital Equity (ISO 26000, ISO 14001) Have we optimized for different bandwidth and offline contexts? Environment and Digital Equity (ISO 26000, ISO 14001) Are we mindful of energy efficiency and environmental sustainability? Environment and Digital Equity (ISO 26000, ISO 14001) Do we revisit inclusion practices during retrospectives and design reviews? Ongoing Inclusion Monitoring (ISO 9001, ISO 29110) Is there a process to assess the inclusivity of updates or new features? Ongoing Inclusion Monitoring (ISO 9001, ISO 29110) Do we actively seek feedback from underrepresented user groups? Ongoing Inclusion Monitoring (ISO 9001, ISO 29110)