The correct answer is Use an IDE with strong screen reader support and confirmed Copilot compatibility.

This choice aligns the developer’s tools with assistive technology and with the way Copilot integrates into editors. A screen reader friendly IDE that is officially supported by Copilot allows keyboard navigation of suggestions and ensures that suggestion popups and inline completions are announced properly. This reduces friction and preserves productivity without removing functionality.

Turn off Copilot for that developer is not appropriate because it removes the assistive capability rather than making it accessible. This would hinder productivity and does not solve the underlying accessibility need.

Move all coding to Google Cloud Shell Editor is not justified because wholesale migration is disruptive and there is no guarantee of full Copilot support and robust screen reader behavior in that environment. The better solution is to pick a supported IDE that is known to work well with screen readers.

Have the engineer reuse code by copying snippets from teammates does not address accessibility and can introduce quality and compliance risks. It also strips the developer of the ability to benefit from real time suggestions that can be made accessible.

Full AWS Practitioner Certification Question