Short answer: a medical condition does not exempt a staff member from completing the security awareness training your organisation has decided to run, but it does change how they complete it — the format, the deadline and the assessments can all be adjusted. Australian workplaces run cyber security training as a policy obligation, not a clinical one, and a policy obligation can be met in more than one way without losing the substance of the programme.
TL;DR
- A medical condition changes the delivery format of training, not whether it is completed.
- Screen-based exemptions cover migraine, photosensitive epilepsy and severe eye strain — audio, paper-based and facilitator-led formats keep the same content accessible.
- A trusted colleague completing training on a person's behalf is a documented policy accommodation, not a workaround.
- Phishing simulations can use role-based or alias addresses instead of a staff member's personal mailbox while still measuring team-level risk.
- The goal is risk reduction and evidence of it, not forcing an individual through a specific pixel-based format.
Why this matters
Mandatory training that ignores a genuine medical condition creates two problems at once: an avoidable employment-law exposure for the employer, and a quiet erosion of trust in the whole programme. If people believe the training is applied inflexibly, the cynical ones disengage and the conscientious ones stay silent about what they actually need. A clear accommodation path costs little and buys compliance from everyone.
Under the Disability Discrimination Act 1992, employers must make reasonable adjustments so a person with disability is not disadvantaged in their employment. The duty applies to workplace training as much as to recruitment or duties, and it does not require the employer to provide training that is less effective — only that the outcome is achieved in a way the person can actually use.
Can staff be exempted from mandatory training for medical reasons?
Direct answer: no full exemption, and no need for one. What the law and good practice point to is an adjusted route to the same outcome.
A typical security awareness curriculum has three components, and each can be adjusted independently:
| Component | Standard format | Common medical concern | Typical adjustment |
|---|---|---|---|
| Awareness lessons | Short screen-based modules | Migraine, epilepsy, eye strain, PTSD | Audio version, transcript, or facilitated session |
| Knowledge check | Timed on-screen quiz | Cognitive fatigue, anxiety | Untimed, verbal, or paper-based check |
| Phishing simulations | Emails to each staff member | Severe anxiety, PTSD from real incidents | Role-based or alias address, or simulation exclusion for that person |
None of these adjustments removes the training. Each one changes the channel, not the content.
What the law actually requires
In Australia the obligation on the employer comes from the Disability Discrimination Act 1992 and, for some conditions, work health and safety law. The standard is a reasonable adjustment — a change that lets the person meet the same requirement as everyone else, not a different requirement. A verbal quiz instead of an on-screen one, an audio version of a lesson, or a simulation sent to a shared team address instead of an individual mailbox are all reasonable adjustments in this sense.
What the law does not require is an automatic exemption. There is no provision that says a person with a medical condition is excused from a workplace policy — the employer's duty is to adapt the delivery, and the person's duty is to engage with the adapted route.
How to write the accommodation policy
A good accommodation policy for security awareness training has four parts:
- A named contact. Someone in HR, a manager, or a nominated privacy point person who receives accommodation requests and does not broadcast them.
- A private conversation, not a form that's visible to the team. The request should never travel through a shared ticket queue.
- A documented decision, recorded once. What was requested, what was decided, what format was agreed. No medical diagnosis stored with the training record — the adjustment is what matters, not the condition.
- A scheduled review. Conditions change; a decision made in January may not fit in September.
The aim is to record what was adjusted, not why, and to keep the adjustment out of the training completion data that gets exported to auditors.
Adjustments for specific conditions
- Migraine and photosensitive epilepsy: screen exposure, animation and flashing content are the triggers. Provide an audio version or a transcript, and remove any animated content from the adapted version. The content itself does not change.
- Severe eye strain or visual impairment: a screen-reader compatible version, or an audio narration of the lesson, with a verbal knowledge check.
- Post-traumatic stress after a real phishing incident: the training content itself is usually fine; the simulation is the trigger. Exclude that person from simulations or send them to a monitored alias instead.
- Severe anxiety: untimed assessments, one module at a time, and simulations sent to an alias address rather than a personal mailbox.
- Chronic pain or conditions needing rest breaks: split the curriculum across weeks instead of one sitting — which is what the training pacing question addresses for everyone, not just staff with a medical reason.
What a phishing simulation does with an accommodation in place
If simulations run to a role-based or alias address instead of a person's own mailbox, the measurement changes but the programme does not lose its value:
- Team-level risk is still measured. A shared mailbox still receives the simulation, and the team's report rate and click rate are still recorded.
- The individual is protected from a known trigger. The point of the simulation is to build a reflex, not to test one person's stress response.
- Coaching flows to the whole team. If the alias clicker is identified only as “shared mailbox”, the follow-up lesson goes to everyone on that address.
The risk reporting layer — how the programme shows who is clicking what — still works on aggregate numbers, which is the level that matters for the organisation's risk picture and the evidence auditors ask for. See human risk reporting for what those aggregates look like.
What not to do
- Do not ask for a diagnosis. The condition itself is private; the adjustment is the only thing the programme needs to know.
- Do not keep a running list of exempted staff on a shared drive. The list itself is a privacy problem.
- Do not treat an accommodation as a permanent pass from the programme. Review it on the schedule you set.
- Do not let a manager make the call ad hoc. The decision goes through the named contact so it is consistent and documented.
Why does this come up in security awareness specifically?
Because the programme is the one workplace obligation that touches every staff member personally and repeatedly. A fire warden course happens once; awareness training recurs monthly or quarterly, and it measures individual behaviour — clicking, reporting, completing. Recurrence plus measurement is exactly where a rigid one-size-fits-all format starts to hurt someone.
How does this interact with completion tracking and audits?
Completion data is the artefact auditors, insurers and enterprise clients ask to see. An accommodation shows up there in one of three shapes, all acceptable:
- Completed via adjusted format — the record shows a completion, and the format flag sits in the accommodation record, not the training record.
- Simulated-phishing-exempt with training completed — the awareness lessons are done; the simulation component is excluded for that person.
- Delegated completion — a trusted colleague completes the same modules on the person's behalf, and the record notes the arrangement.
All three preserve the evidence trail: the programme ran, people completed it, and the exceptions were handled by policy rather than by silence. The completion records export question covers what auditors expect to see in the export itself.
Related questions
Is a medical exemption the same as a medical accommodation? No. An exemption removes the obligation; an accommodation keeps the obligation and changes how it is met. Australian practice and the DDA both point to the accommodation route.
Who decides whether an accommodation is reasonable? The employer, informed by what the staff member requests and what the training provider can actually deliver. Audio versions, transcripts and alias-based simulations are all deliverable without changing the underlying curriculum.
Does an accommodation weaken the security programme? No — it moves the measurement. A person excluded from personal simulations is still covered by team-level reporting, still completes the awareness content, and still counts towards the completion rate auditors want.
How does Cyber Aware handle it?
Cyber Aware's security awareness training supports the adjusted routes this article describes: modules can be completed in whatever format the accommodation agreed, phishing simulations can run to shared mailboxes and aliases as well as individuals, and completion reporting stays at the level auditors and insurers expect to see.
One last thing
If your organisation has never written the accommodation path down, the first real request will arrive through an awkward conversation nobody has rehearsed. A one-page policy naming a contact, the agreed adjustments and the review cycle removes that — and it doubles as evidence of a mature programme if an auditor asks how exceptions are handled.
FAQ
Can a staff member refuse training because of a medical condition? No. The obligation stays; the format adjusts. The employer adapts delivery, and the staff member engages with the adapted route.
Do we need a medical certificate to grant an accommodation? Not for a simple format change. A brief statement of the functional limitation is enough for most adjustments, and privacy law says the employer should collect only what the decision actually needs.
Can we exclude someone from phishing simulations entirely? Yes, as an accommodation. The team-level simulation still runs, so the programme keeps its measurement value without targeting the individual.
What if the accommodation is abused? Review the accommodation on the schedule you set, and base any change on the programme's actual outcomes, not on suspicion. The audit trail shows what was agreed and when.
Does an accommodation affect our compliance reporting? Not adversely. The completion evidence stays intact, and a documented accommodation policy is itself evidence of a well-run programme.