Collaborative Discussion 1: Codes of Ethics and Professional Conduct

Collaborative Discussion 1: Codes of Ethics and Professional Conduct (Units 1-3)

Initial Post: Ethical Analysis of Accessibility Failures: Applying ACM and BCS Codes of Conduct to Software Development

Posted: Thursday, 7 August 2025, 2:12 PM

Case Overview

AllTogether’s collaboration tool implemented hidden edit controls that failed accessibility standards, despite company Web Content Accessibility Guidelines (WCAG) policies. Leadership released the inaccessible feature under schedule pressure, creating barriers for disabled users and forcing customer rollbacks.

Analysis

This case shows how overlooking ethical principles in software development creates cascading failures across professional, legal, and social domains. Despite having established accessibility policies aligned with WCAG standards, the development team’s rush to implement hidden controls violated fundamental ethical obligations outlined in both ACM and BCS codes of conduct.

Professional Competence Failures

The team’s oversight of accessibility requirements during design demonstrates a breach of professional competence standards. The BCS Code mandates that members “only undertake to do work within your professional competence” (BCS, 2022), while ACM Principle 2.3 requires adherence to existing professional standards (Gotterbarn et al., 2018). Their failure to integrate WCAG compliance from inception reveals inadequate professional preparation.

Discriminatory Impact

Leadership’s dismissive attitude toward disabled users directly violated non-discrimination principles. The BCS Code explicitly prohibits discrimination “on the grounds of…disability” (BCS, 2022, s.1.c), while ACM Principle 1.4 emphasizes fair treatment. This created potential legal liability under disability legislation and reinforced systemic exclusion of disabled users (Ladner, 2015).

Reputational and Financial Consequences

The decision generated increased support costs, customer rollbacks, and reputational damage, demonstrating how ethical failures translate into business risks. As Horton (2025) notes, accessibility defects cost more to remediate post-release than addressing requirements during development.

Conclusion

This case ultimately demonstrates that ethical compliance in software development is not merely regulatory obligation but essential professional practice that prevents discrimination, reduces costs, and upholds the computing profession’s integrity.

References

BCS (2022) Code of Conduct for BCS Members. British Computer Society. Available at: https://www.bcs.org/membership/become-a-member/bcs-code-of-conduct/
Gotterbarn, D., Wolf, M.J. and Flick, C. (2018) ‘ACM Code of Ethics’, Communications of the ACM, 61(1), pp. 121–128. Available at: https://doi.org/10.1145/3173016
Horton, S. (2025) ‘Case Study: Accessibility in Software Development’, ACM Code of Ethics.
Ladner, R.E. (2015) ‘Design for user empowerment’, Communications of the ACM, 58(8), pp. 33-37.

Peer Responses Received

Response 1: Md Chowdhury

Posted: Sunday, 10 August 2025, 10:55 AM

Hi Abdulhakim,

Your analysis effectively applies both ACM and BCS codes to the AllTogether accessibility failure, clearly linking ethical obligations to professional competence (BCS, 2022; Gotterbarn, Wolf and Flick, 2018). The focus on non-discrimination principles and WCAG alignment is well-supported, and the connection you make between ethical lapses and business risks is compelling.

To strengthen your argument, you could briefly outline preventive measures such as accessibility reviews in sprint planning or automated WCAG compliance testing. This would bridge the gap between identifying the ethical breach and demonstrating how professional practice can ensure compliance. In addition, referencing legal frameworks like the Equality Act 2010 or the Americans with Disabilities Act could reinforce the legal implications you mention.

Overall, your post highlights that accessibility is not only a regulatory and ethical mandate but also a sound business practice that safeguards reputation, reduces rework costs, and upholds the integrity of the computing profession.

References:

BCS (2022) Code of Conduct for BCS Members. Available at: https://www.bcs.org/membership/become-a-member/bcs-code-of-conduct/
Gotterbarn, D., Wolf, M.J. and Flick, C. (2018) ‘ACM Code of Ethics’, Communications of the ACM, 61(1), pp. 121–128. Available at: https://doi.org/10.1145/3173016

Response 2: Yousif Ali Karam Yousif Almaazmi

Posted: Sunday, 10 August 2025, 6:01 PM

Your breakdown of the accessibility lapse by AllTogether is thorough. It reflects solid knowledge of how ethical lapses in software development can carry over to the legal, social, and professional spheres. You effectively relate the violation of accessibility to professional codes, which proves your argument to be more realistic and organized.

Mentioning that deadlines were followed more often than compliance by leadership, you demonstrate a frequent yet hazardous conflict between the pressure of providing delivery and a moral obligation (Gautam et al., 2024). The way in which you have connected this to discrimination against disabled users supports the significance of viewing inclusivity as a non-negotiable in design processes.

I especially like that you focused on the business risks that ethical failures involve. By noting how accessibility can be costly to support, rolled back, and even reputationally damaging, ignoring accessibility is immoral and a poor strategy. This moral and business framing is doubly robust in making the case to focus on accessibility at the outset (Koplin et al., 2025).

Further elaborating on your defense would be worth looking at how these ethical breaches can be avoided by creating superior governance modes or incorporating testing methods. You might also emphasize the importance of constant education of developers so they do not forget about accessibility. You can add a brief discussion on the role accessibility plays in innovation and expanding market coverage to solidify further the pre-built business case (Wong, 2021).

References:

Gautam, A., Kulkarni, A., Hug, S., Lehr, J., & Yoon, I. (2024) ‘Socially responsible computing in an introductory course’. In Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1, pp. 373-379. Available at: https://doi.org/10.1145/3626252.3630926
Koplin, J. J., Johnston, M., Webb, A. N., Whittaker, A., & Mills, C. (2025) ‘Ethics of artificial intelligence in embryo assessment: mapping the terrain’. Human Reproduction, 40(2), pp. 179-185. Available at: https://doi.org/10.1093/humrep/deae264
Wong, R. Y. (2021) ‘Tactics of soft resistance in user experience professionals’ values work’. Proceedings of the ACM on Human-Computer Interaction, 5(CSCW2), pp. 1-28. Available at: https://dl.acm.org/doi/10.1145/3479826

Peer Posts I Responded To

Marie Levesque’s Initial Post: Automated Active Response Weaponry Case Analysis

Posted: Wednesday, 6 August 2025, 6:11 AM

Marie analyzed Q Industries’ progression from defensive to offensive autonomous weaponry, examining the ethical implications through ACM and BCS codes. Her post highlighted the tension between corporate interests and public welfare in autonomous weapons development.

Key Points from Marie’s Analysis:

Q Industries’ evolution from bomb-defusing robots to lethal autonomous weapons
Application of ACM Principle 1.2 (harm minimization) and 1.1 (human rights)
Engineers’ ethical dilemma regarding whistleblowing vs. confidentiality agreements
BCS Code’s explicit legal compliance requirements vs. ACM’s broader public good emphasis
Facial recognition technology used for targeting protesters

My Response to Marie Levesque

Posted: Thursday, 7 August 2025, 2:24 PM

Marie, your analysis of the Q Industries case captures the ethical complexity of autonomous weaponry development. Your distinction between the ACM and BCS codes regarding legal compliance is particularly astute—the BCS’s explicit requirement for jurisdictional legal framework adherence does indeed strengthen arguments against developing weapons for governments with poor human rights records.

I’m intrigued by your treatment of the engineers’ whistleblowing dilemma. While you correctly identify their actions as consistent with ACM Principles 1.7 and 2.7, I’d argue this case also highlights tensions within professional codes themselves. The conflict between respecting intellectual property (Principle 2.3) and serving public good demonstrates how ethical obligations can compete, requiring professionals to prioritize principles hierarchically.

Your point about facial recognition targeting protesters raises questions about dual-use technology. How do we draw ethical boundaries when defensive technologies evolve into offensive ones? The progression from bomb-defusing to lethal weaponry suggests a slippery slope that both codes struggle to address adequately—especially in the current pace of AI acceleration.

Given that both ACM and BCS codes emphasize public welfare, should there be clearer guidelines about when professionals have not just the right, but the obligation to break confidentiality agreements?

References:

ACM (2018) Code of Ethics and Professional Conduct. Association for Computing Machinery.
BCS (2022) Code of Conduct for BCS Members. British Computer Society.

Summary Post

Posted by Abdulhakim Bashir - Saturday, 6 September 2025, 6:40 PM

This collaborative discussion has provided valuable insights into the practical application of professional ethical frameworks in computing. The exchange highlighted critical tensions between competing ethical obligations and business pressures in software development contexts.

The peer feedback from Md Chowdhury and Yousif reinforced the importance of integrating preventive measures into development processes, rather than treating accessibility as a post-hoc consideration. Chowdhury’s suggestion to incorporate legal frameworks like the Equality Act 2010 and Americans with Disabilities Act strengthens the argument that ethical compliance extends beyond professional codes to encompass broader societal obligations (Gotterbarn et al., 2018).

Yousif’s observation about the recurring conflict between delivery pressure and moral obligations resonates with current research on socially responsible computing practices (Gautam et al., 2024). The dual framing of accessibility as both moral imperative and business necessity demonstrates how ethical practice can align with organizational sustainability rather than compete with it.

My response to Marie Levesque’s autonomous weapons analysis revealed additional complexities in professional ethics, particularly regarding dual-use technologies and the hierarchical prioritization of competing principles. This highlights how professional codes must evolve to address emerging technologies that challenge traditional ethical boundaries (Wong, 2021).

The discussion ultimately demonstrates that ethical frameworks in computing require continuous interpretation and application rather than simple rule-following. Professional competence must include the ability to navigate competing obligations while maintaining commitment to public welfare and human dignity.

References:

Gautam, A., Kulkarni, A., Hug, S., Lehr, J., & Yoon, I. (2024) ‘Socially responsible computing in an introductory course’. Proceedings of the 55th ACM Technical Symposium on Computer Science Education, pp. 373-379.
Gotterbarn, D., Wolf, M.J. and Flick, C. (2018) ‘ACM Code of Ethics’, Communications of the ACM, 61(1), pp. 121–128.
Wong, R.Y. (2021) ‘Tactics of soft resistance in user experience professionals’ values work’. Proceedings of the ACM on Human-Computer Interaction, 5(CSCW2), pp. 1-28.

← Back to RMPP Module