Most curricula treat ethics as a module: a week near the end, a case study about a company everyone already agrees behaved badly, an assignment nobody reads twice.
That framing fails because it puts ethics after the design is finished, when the only honest options left are to ship it or throw it away. Real constraints go in at the start, alongside latency budgets and browser support.
What we ask every learner to do
Before a project is considered complete, the learner runs two assessments on their own work. The first is data privacy: what personal data does this collect, why, where does it live, who can reach it, how long is it kept, and what happens when someone asks for it back. The second is accessibility: can this be operated with a keyboard, does it survive a screen reader, does it survive being read by someone with low vision or in bright sunlight on a cheap phone.
Both are written up. Both are questioned. Neither is optional.
What changes
Learners start designing differently well before the assessment. They stop collecting a phone number they have no use for. They stop building a form that only works with a mouse. The constraint moves upstream, which is the entire point.
And there is a hiring dimension nobody mentions: a junior candidate who can talk about data retention or contrast ratios without being prompted is instantly distinguishable from one who cannot. It is a small thing that reads as seniority.
The premise underneath
Tomorrow's technology and design leaders cannot build solely for short-term conversion metrics. If we are training people to enter rooms where these decisions get made, sending them in without the vocabulary would be its own kind of failure.
