# 4. Accessibility Compliance — Test Cases

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: accessibility_compliance.md — every feature, sub-feature, and rule covered

## Test Execution Policy

- Zero tolerance: any deviation from the documented behavior is a defect.
- Every failed test is logged with a Bug ID, the feature, the sub-feature, the expected vs actual result, and the severity; 100% of bugs are fixed before the group passes.
- 100% pass rate is required for the group to be marked complete.

## Coverage Matrix

| Feature | Sub-feature / Rule | Test IDs |
|---------|--------------------|----------|
| 4.1 WCAG Compliance Tracking | WCAG version selection: the WCAG version tracked | TC-SA-ACC-04-001 |
| 4.1 WCAG Compliance Tracking | Conformance level: the target conformance level | TC-SA-ACC-04-002 |
| 4.1 WCAG Compliance Tracking | Success criteria catalog: the criteria with their compliance state | TC-SA-ACC-04-003 |
| 4.1 WCAG Compliance Tracking | Compliance score: the overall score per area and platform-wide | TC-SA-ACC-04-004 |
| 4.1 WCAG Compliance Tracking | Compliance trend: the score over time | TC-SA-ACC-04-005 |
| 4.1 WCAG Compliance Tracking | Criteria detail: the evidence and state per criterion | TC-SA-ACC-04-006 |
| 4.1 WCAG Compliance Tracking | Rule: the score is computed over applicable criteria only | TC-SA-ACC-04-007 |
| 4.1 WCAG Compliance Tracking | Rule: a not-applicable criterion is excluded, not a failure | TC-SA-ACC-04-008 |
| 4.1 WCAG Compliance Tracking | Rule: a criterion with no evidence is unverified, not compliant | TC-SA-ACC-04-009 |
| 4.1 WCAG Compliance Tracking | Rule: a level/criteria mismatch is flagged | TC-SA-ACC-04-010 |
| 4.1 WCAG Compliance Tracking | Rule: an empty trend window shows no trend | TC-SA-ACC-04-011 |
| 4.1 WCAG Compliance Tracking | Rule: a state change updates the score immediately | TC-SA-ACC-04-012 |
| 4.1 WCAG Compliance Tracking | Rule: tracking configuration changes are audit-logged | TC-SA-ACC-04-013 |
| 4.2 Accessibility Audit Scheduling | Audit creation: an audit created with scope and criteria | TC-SA-ACC-04-014 |
| 4.2 Accessibility Audit Scheduling | Audit scheduling: audits scheduled for a date and recurrence | TC-SA-ACC-04-015 |
| 4.2 Accessibility Audit Scheduling | Audit assignment: audits assigned to an auditor or team | TC-SA-ACC-04-016 |
| 4.2 Accessibility Audit Scheduling | Audit scope: the areas and content types included | TC-SA-ACC-04-017 |
| 4.2 Accessibility Audit Scheduling | Audit status: the audit state | TC-SA-ACC-04-018 |
| 4.2 Accessibility Audit Scheduling | Audit list: the audits with schedule, scope, and status | TC-SA-ACC-04-019 |
| 4.2 Accessibility Audit Scheduling | Rule: an audit requires a non-empty scope | TC-SA-ACC-04-020 |
| 4.2 Accessibility Audit Scheduling | Rule: an unassigned audit is held in draft | TC-SA-ACC-04-021 |
| 4.2 Accessibility Audit Scheduling | Rule: a past uncompleted audit is marked overdue | TC-SA-ACC-04-022 |
| 4.2 Accessibility Audit Scheduling | Rule: an invalid recurrence is rejected | TC-SA-ACC-04-023 |
| 4.2 Accessibility Audit Scheduling | Rule: an audit cannot be completed until all items are assessed | TC-SA-ACC-04-024 |
| 4.2 Accessibility Audit Scheduling | Rule: a completed audit feeds the compliance tracking | TC-SA-ACC-04-025 |
| 4.2 Accessibility Audit Scheduling | Rule: audit changes are audit-logged | TC-SA-ACC-04-026 |
| 4.3 Issue Tracking and Resolution | Issue creation: an issue created with description, location, and severity | TC-SA-ACC-04-027 |
| 4.3 Issue Tracking and Resolution | Issue assignment: issues assigned to an owner | TC-SA-ACC-04-028 |
| 4.3 Issue Tracking and Resolution | Issue severity: the severity level | TC-SA-ACC-04-029 |
| 4.3 Issue Tracking and Resolution | Issue status: the issue state | TC-SA-ACC-04-030 |
| 4.3 Issue Tracking and Resolution | Issue resolution: the resolution note and fix reference | TC-SA-ACC-04-031 |
| 4.3 Issue Tracking and Resolution | Issue list: the issues with severity, status, and owner | TC-SA-ACC-04-032 |
| 4.3 Issue Tracking and Resolution | Issue aging: the time open per severity | TC-SA-ACC-04-033 |
| 4.3 Issue Tracking and Resolution | Rule: an issue requires a description and location | TC-SA-ACC-04-034 |
| 4.3 Issue Tracking and Resolution | Rule: an issue requires an owner before in progress | TC-SA-ACC-04-035 |
| 4.3 Issue Tracking and Resolution | Rule: an issue cannot be closed until resolved and verified | TC-SA-ACC-04-036 |
| 4.3 Issue Tracking and Resolution | Rule: a resolved issue with no note is flagged | TC-SA-ACC-04-037 |
| 4.3 Issue Tracking and Resolution | Rule: a closed issue stops aging | TC-SA-ACC-04-038 |
| 4.3 Issue Tracking and Resolution | Rule: a critical issue beyond its window is escalated | TC-SA-ACC-04-039 |
| 4.3 Issue Tracking and Resolution | Rule: an issue linked to an audit carries the audit reference | TC-SA-ACC-04-040 |
| 4.3 Issue Tracking and Resolution | Rule: issue changes are audit-logged | TC-SA-ACC-04-041 |
| 4.4 Compliance Reporting | Compliance report generation: a report generated for a period | TC-SA-ACC-04-042 |
| 4.4 Compliance Reporting | Audit result reporting: audit results included in the report | TC-SA-ACC-04-043 |
| 4.4 Compliance Reporting | Issue summary reporting: the open and resolved issue summary | TC-SA-ACC-04-044 |
| 4.4 Compliance Reporting | Conformance statement: the statement per WCAG level | TC-SA-ACC-04-045 |
| 4.4 Compliance Reporting | Report export: the report exported (PDF, CSV) | TC-SA-ACC-04-046 |
| 4.4 Compliance Reporting | Report history: the generated reports with period and state | TC-SA-ACC-04-047 |
| 4.4 Compliance Reporting | Rule: a report requires a valid period | TC-SA-ACC-04-048 |
| 4.4 Compliance Reporting | Rule: only completed audits are included; in-progress listed separately | TC-SA-ACC-04-049 |
| 4.4 Compliance Reporting | Rule: the conformance statement reflects the highest fully met level | TC-SA-ACC-04-050 |
| 4.4 Compliance Reporting | Rule: a failed export is reported; the report is not marked exported | TC-SA-ACC-04-051 |
| 4.4 Compliance Reporting | Rule: a report is immutable; a corrected report is new | TC-SA-ACC-04-052 |
| 4.4 Compliance Reporting | Rule: the issue summary counts by severity and status at period end | TC-SA-ACC-04-053 |
| 4.4 Compliance Reporting | Rule: report generation is audit-logged | TC-SA-ACC-04-054 |

### TC-SA-ACC-04-001 — WCAG version selection: the WCAG version tracked
**Type:** Positive
**Covers:** 4.1 → WCAG version selection: the WCAG version tracked (e.g., 2.1, 2.2)
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, open the WCAG compliance tracking and select a WCAG version.
2. Save the selection.
3. Observe the result and verify the full behavior: the criteria catalog reflects the selected version.
**Expected Result:** The version selection works — the catalog reflects the version, delivered exactly as documented.
**Priority:** Critical

### TC-SA-ACC-04-002 — Conformance level: the target conformance level
**Type:** Positive
**Covers:** 4.1 → Conformance level: the target conformance level (A, AA, AAA)
**Preconditions:** A Super Admin account is active; a WCAG version is selected.
**Steps:**
1. As a Super Admin, set the target conformance level to AA and save.
2. Observe the result and verify the full behavior: the tracked criteria match the AA level.
**Expected Result:** The conformance level is applied — the criteria match the level, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-003 — Success criteria catalog: the criteria with their compliance state
**Type:** Positive
**Covers:** 4.1 → Success criteria catalog: the WCAG success criteria with their compliance state
**Preconditions:** A Super Admin account is active; a version and level are selected.
**Steps:**
1. As a Super Admin, open the success criteria catalog.
2. Observe the result and verify the full behavior: the criteria are shown with their compliance state.
**Expected Result:** The catalog is shown — the criteria with their state are visible, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-004 — Compliance score: the overall score per area and platform-wide
**Type:** Positive
**Covers:** 4.1 → Compliance score: the overall compliance score per area and platform-wide
**Preconditions:** A Super Admin account is active; criteria have compliance states.
**Steps:**
1. As a Super Admin, open the compliance score view.
2. Observe the result and verify the full behavior: the score is shown per area and platform-wide.
**Expected Result:** The compliance score is shown — the per-area and platform-wide scores are visible, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-005 — Compliance trend: the score over time
**Type:** Positive
**Covers:** 4.1 → Compliance trend: the compliance score over time
**Preconditions:** A Super Admin account is active; score history exists.
**Steps:**
1. As a Super Admin, open the compliance trend view.
2. Observe the result and verify the full behavior: the score over time is shown.
**Expected Result:** The trend is shown — the score over time is visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-006 — Criteria detail: the evidence and state per criterion
**Type:** Positive
**Covers:** 4.1 → Criteria detail: the evidence and state per success criterion
**Preconditions:** A Super Admin account is active; a criterion has evidence.
**Steps:**
1. As a Super Admin, open a criterion's detail.
2. Observe the result and verify the full behavior: the evidence and state are shown.
**Expected Result:** The criteria detail is shown — the evidence and state are visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-007 — Rule: the score is computed over applicable criteria only
**Type:** Positive
**Covers:** 4.1 → Rule: the compliance score is computed only over criteria applicable to the selected version and level
**Preconditions:** A Super Admin account is active; a version and level are selected.
**Steps:**
1. As a Super Admin, review the compliance score computation.
2. Observe the result and verify the full behavior: only applicable criteria are included in the score.
**Expected Result:** The score is computed correctly — only applicable criteria are included, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-008 — Rule: a not-applicable criterion is excluded, not a failure
**Type:** Positive
**Covers:** 4.1 → Rule: a criterion marked not applicable is excluded from the score, not counted as a failure
**Preconditions:** A Super Admin account is active; a criterion is marked not applicable.
**Steps:**
1. As a Super Admin, review the compliance score.
2. Observe the result and verify the full behavior: the not-applicable criterion is excluded, not a failure.
**Expected Result:** The criterion is excluded — it is not counted as a failure, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-009 — Rule: a criterion with no evidence is unverified, not compliant
**Type:** Positive
**Covers:** 4.1 → Rule: a criterion with no evidence is treated as unverified, not compliant
**Preconditions:** A Super Admin account is active; a criterion has no evidence.
**Steps:**
1. As a Super Admin, open the criterion's state.
2. Observe the result and verify the full behavior: the criterion is marked unverified, not compliant.
**Expected Result:** The criterion is unverified — it is not marked compliant, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-010 — Rule: a level/criteria mismatch is flagged
**Type:** Negative
**Covers:** 4.1 → Rule: the conformance level must be at or above the criteria being tracked; a mismatch is flagged
**Preconditions:** A Super Admin account is active; a level below the tracked criteria is set.
**Steps:**
1. As a Super Admin, set a mismatched conformance level.
2. Observe the result and verify the full behavior: the mismatch is flagged.
**Expected Result:** The mismatch is flagged — the level must match the criteria, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-011 — Rule: an empty trend window shows no trend
**Type:** Positive
**Covers:** 4.1 → Rule: the compliance trend is computed over a fixed window; an empty window shows no trend
**Preconditions:** A Super Admin account is active; the trend window has no data.
**Steps:**
1. As a Super Admin, open the compliance trend view.
2. Observe the result and verify the full behavior: no trend is shown for the empty window.
**Expected Result:** No trend is shown — the empty window is handled, delivered exactly as documented.
**Priority:** Low

### TC-SA-ACC-04-012 — Rule: a state change updates the score immediately
**Type:** Positive
**Covers:** 4.1 → Rule: a change in a criterion's state updates the score immediately
**Preconditions:** A Super Admin account is active; a criterion's state can change.
**Steps:**
1. As a Super Admin, change a criterion's state to compliant.
2. Open the compliance score.
3. Observe the result and verify the full behavior: the score is updated immediately.
**Expected Result:** The score is updated — the change is reflected immediately, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-013 — Rule: tracking configuration changes are audit-logged
**Type:** Positive
**Covers:** 4.1 → Audit logging of WCAG compliance tracking
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, change the tracking configuration and save.
2. Open the audit log.
3. Observe the result and verify the full behavior: the change is recorded with the actor and timestamp.
**Expected Result:** The configuration change is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-014 — Audit creation: an audit created with scope and criteria
**Type:** Positive
**Covers:** 4.2 → Audit creation: an accessibility audit created with scope and criteria
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, create an audit with a scope and criteria.
2. Save the audit.
3. Observe the result and verify the full behavior: the audit is created and appears in the audit list.
**Expected Result:** The audit is created — it appears in the audit list, delivered exactly as documented.
**Priority:** Critical

### TC-SA-ACC-04-015 — Audit scheduling: audits scheduled for a date and recurrence
**Type:** Positive
**Covers:** 4.2 → Audit scheduling: audits scheduled for a date and recurrence
**Preconditions:** A Super Admin account is active; an audit is created.
**Steps:**
1. As a Super Admin, schedule the audit for a date with a monthly recurrence.
2. Save the schedule.
3. Observe the result and verify the full behavior: the audit is scheduled with the recurrence.
**Expected Result:** The scheduling works — the audit is scheduled with the recurrence, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-016 — Audit assignment: audits assigned to an auditor or team
**Type:** Positive
**Covers:** 4.2 → Audit assignment: audits assigned to an auditor or team
**Preconditions:** A Super Admin account is active; an audit is created; an auditor exists.
**Steps:**
1. As a Super Admin, assign the audit to the auditor.
2. Save the assignment.
3. Observe the result and verify the full behavior: the audit is assigned to the auditor.
**Expected Result:** The assignment works — the audit is assigned, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-017 — Audit scope: the areas and content types included
**Type:** Positive
**Covers:** 4.2 → Audit scope: the areas and content types included in an audit
**Preconditions:** A Super Admin account is active; an audit is created.
**Steps:**
1. As a Super Admin, set the audit scope to specific areas and content types.
2. Save the scope.
3. Observe the result and verify the full behavior: the scope is recorded for the audit.
**Expected Result:** The scope is recorded — the areas and content types are set, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-018 — Audit status: the audit state
**Type:** Positive
**Covers:** 4.2 → Audit status: the audit state (scheduled, in progress, completed, overdue)
**Preconditions:** A Super Admin account is active; audits exist in various states.
**Steps:**
1. As a Super Admin, open the audit list.
2. Observe the result and verify the full behavior: the status is shown per audit.
**Expected Result:** The status is shown — the state per audit is visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-019 — Audit list: the audits with schedule, scope, and status
**Type:** Positive
**Covers:** 4.2 → Audit list: the audits with their schedule, scope, and status
**Preconditions:** A Super Admin account is active; multiple audits exist.
**Steps:**
1. As a Super Admin, open the audit list.
2. Observe the result and verify the full behavior: the audits are shown with schedule, scope, and status.
**Expected Result:** The audit list is shown — the audits with their details are visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-020 — Rule: an audit requires a non-empty scope
**Type:** Negative
**Covers:** 4.2 → Rule: an audit requires a non-empty scope; an audit with no scope cannot be created
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, attempt to create an audit with no scope.
2. Observe the result and verify the full behavior: the creation is blocked with a validation message.
**Expected Result:** The creation is blocked — a non-empty scope is required, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-021 — Rule: an unassigned audit is held in draft
**Type:** Positive
**Covers:** 4.2 → Rule: an audit requires an assignee; an unassigned audit is held in draft, not scheduled
**Preconditions:** A Super Admin account is active; an audit is created with no assignee.
**Steps:**
1. As a Super Admin, attempt to schedule the unassigned audit.
2. Observe the result and verify the full behavior: the audit is held in draft and not scheduled.
**Expected Result:** The audit is held in draft — it is not scheduled without an assignee, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-022 — Rule: a past uncompleted audit is marked overdue
**Type:** Positive
**Covers:** 4.2 → Rule: a scheduled audit in the past with no completion is marked overdue
**Preconditions:** A Super Admin account is active; a scheduled audit is in the past and uncompleted.
**Steps:**
1. As a Super Admin, open the audit list.
2. Observe the result and verify the full behavior: the past uncompleted audit is marked overdue.
**Expected Result:** The audit is marked overdue — the state is correct, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-023 — Rule: an invalid recurrence is rejected
**Type:** Negative
**Covers:** 4.2 → Rule: an audit recurrence must be a valid interval; an invalid recurrence is rejected
**Preconditions:** A Super Admin account is active; an audit is created.
**Steps:**
1. As a Super Admin, attempt to set an invalid recurrence interval.
2. Observe the result and verify the full behavior: the recurrence is rejected with a validation message.
**Expected Result:** The invalid recurrence is rejected — a valid interval is required, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-024 — Rule: an audit cannot be completed until all items are assessed
**Type:** Negative
**Covers:** 4.2 → Rule: an audit cannot be completed until all in-scope items are assessed
**Preconditions:** A Super Admin account is active; an audit has unassessed items.
**Steps:**
1. As a Super Admin, attempt to complete the audit with unassessed items.
2. Observe the result and verify the full behavior: the completion is blocked.
**Expected Result:** The completion is blocked — all items must be assessed first, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-025 — Rule: a completed audit feeds the compliance tracking
**Type:** Positive
**Covers:** 4.2 → Rule: a completed audit produces a result that feeds the compliance tracking
**Preconditions:** A Super Admin account is active; an audit is completed.
**Steps:**
1. As a Super Admin, complete the audit.
2. Open the WCAG compliance tracking.
3. Observe the result and verify the full behavior: the audit result is reflected in the compliance tracking.
**Expected Result:** The result feeds tracking — the compliance tracking is updated, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-026 — Rule: audit changes are audit-logged
**Type:** Positive
**Covers:** 4.2 → Audit logging of accessibility audit scheduling
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, change an audit's schedule.
2. Open the audit log.
3. Observe the result and verify the full behavior: the change is recorded with the actor and timestamp.
**Expected Result:** The audit change is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-027 — Issue creation: an issue created with description, location, and severity
**Type:** Positive
**Covers:** 4.3 → Issue creation: an accessibility issue created with description, location, and severity
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, create an issue with a description, location, and severity.
2. Save the issue.
3. Observe the result and verify the full behavior: the issue is created and appears in the issue list.
**Expected Result:** The issue is created — it appears in the issue list, delivered exactly as documented.
**Priority:** Critical

### TC-SA-ACC-04-028 — Issue assignment: issues assigned to an owner
**Type:** Positive
**Covers:** 4.3 → Issue assignment: issues assigned to an owner
**Preconditions:** A Super Admin account is active; an issue exists; an owner exists.
**Steps:**
1. As a Super Admin, assign the issue to the owner.
2. Save the assignment.
3. Observe the result and verify the full behavior: the issue is assigned to the owner.
**Expected Result:** The assignment works — the issue is assigned, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-029 — Issue severity: the severity level
**Type:** Positive
**Covers:** 4.3 → Issue severity: the severity level (critical, high, medium, low)
**Preconditions:** A Super Admin account is active; an issue exists.
**Steps:**
1. As a Super Admin, set the issue severity to critical.
2. Save the severity.
3. Observe the result and verify the full behavior: the severity is recorded for the issue.
**Expected Result:** The severity is recorded — the level is set, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-030 — Issue status: the issue state
**Type:** Positive
**Covers:** 4.3 → Issue status: the issue state (open, in progress, resolved, verified, closed)
**Preconditions:** A Super Admin account is active; issues exist in various states.
**Steps:**
1. As a Super Admin, open the issue list.
2. Observe the result and verify the full behavior: the status is shown per issue.
**Expected Result:** The status is shown — the state per issue is visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-031 — Issue resolution: the resolution note and fix reference
**Type:** Positive
**Covers:** 4.3 → Issue resolution: the resolution note and fix reference per issue
**Preconditions:** A Super Admin account is active; an issue is in progress.
**Steps:**
1. As a Super Admin, add a resolution note and fix reference and mark the issue resolved.
2. Save the resolution.
3. Observe the result and verify the full behavior: the resolution note and fix reference are recorded.
**Expected Result:** The resolution is recorded — the note and fix reference are saved, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-032 — Issue list: the issues with severity, status, and owner
**Type:** Positive
**Covers:** 4.3 → Issue list: the issues with their severity, status, and owner
**Preconditions:** A Super Admin account is active; multiple issues exist.
**Steps:**
1. As a Super Admin, open the issue list.
2. Observe the result and verify the full behavior: the issues are shown with severity, status, and owner.
**Expected Result:** The issue list is shown — the issues with their details are visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-033 — Issue aging: the time open per severity
**Type:** Positive
**Covers:** 4.3 → Issue aging: the time an issue has been open per severity
**Preconditions:** A Super Admin account is active; issues have been open for varying times.
**Steps:**
1. As a Super Admin, open the issue aging view.
2. Observe the result and verify the full behavior: the time open is shown per issue and severity.
**Expected Result:** The aging is shown — the time open per severity is visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-034 — Rule: an issue requires a description and location
**Type:** Negative
**Covers:** 4.3 → Rule: an issue requires a description and a location; an issue missing either cannot be created
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, attempt to create an issue with no location.
2. Observe the result and verify the full behavior: the creation is blocked with a validation message.
**Expected Result:** The creation is blocked — a description and location are required, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-035 — Rule: an issue requires an owner before in progress
**Type:** Negative
**Covers:** 4.3 → Rule: an issue requires an owner before it can move to in progress
**Preconditions:** A Super Admin account is active; an issue has no owner.
**Steps:**
1. As a Super Admin, attempt to move the unowned issue to in progress.
2. Observe the result and verify the full behavior: the transition is blocked.
**Expected Result:** The transition is blocked — an owner is required first, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-036 — Rule: an issue cannot be closed until resolved and verified
**Type:** Negative
**Covers:** 4.3 → Rule: an issue cannot be closed until it is resolved and verified
**Preconditions:** A Super Admin account is active; an issue is in progress.
**Steps:**
1. As a Super Admin, attempt to close the issue without resolution and verification.
2. Observe the result and verify the full behavior: the close is blocked.
**Expected Result:** The close is blocked — resolution and verification are required, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-037 — Rule: a resolved issue with no note is flagged
**Type:** Negative
**Covers:** 4.3 → Rule: a resolution requires a resolution note; a resolved issue with no note is flagged
**Preconditions:** A Super Admin account is active; an issue is resolved with no note.
**Steps:**
1. As a Super Admin, open the resolved issue.
2. Observe the result and verify the full behavior: the issue is flagged for the missing note.
**Expected Result:** The issue is flagged — the missing note is reported, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-038 — Rule: a closed issue stops aging
**Type:** Positive
**Covers:** 4.3 → Rule: issue aging is computed from the open timestamp; a closed issue stops aging
**Preconditions:** A Super Admin account is active; an issue is closed.
**Steps:**
1. As a Super Admin, open the issue aging view.
2. Observe the result and verify the full behavior: the closed issue's aging is frozen.
**Expected Result:** The aging is frozen — the closed issue stops aging, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-039 — Rule: a critical issue beyond its window is escalated
**Type:** Positive
**Covers:** 4.3 → Rule: a critical issue open beyond its target window is escalated automatically
**Preconditions:** A Super Admin account is active; a critical issue is open beyond its window.
**Steps:**
1. As a Super Admin, open the issue list.
2. Observe the result and verify the full behavior: the critical issue is escalated automatically.
**Expected Result:** The issue is escalated — the automatic escalation occurs, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-040 — Rule: an issue linked to an audit carries the audit reference
**Type:** Positive
**Covers:** 4.3 → Rule: an issue linked to an audit carries the audit reference
**Preconditions:** A Super Admin account is active; an issue is linked to an audit.
**Steps:**
1. As a Super Admin, open the issue.
2. Observe the result and verify the full behavior: the audit reference is shown on the issue.
**Expected Result:** The audit reference is shown — the link is carried, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-041 — Rule: issue changes are audit-logged
**Type:** Positive
**Covers:** 4.3 → Audit logging of accessibility issue tracking and resolution
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, change an issue's status.
2. Open the audit log.
3. Observe the result and verify the full behavior: the change is recorded with the actor and timestamp.
**Expected Result:** The issue change is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-042 — Compliance report generation: a report generated for a period
**Type:** Positive
**Covers:** 4.4 → Compliance report generation: a compliance report generated for a period
**Preconditions:** A Super Admin account is active; compliance data exists for a period.
**Steps:**
1. As a Super Admin, generate a compliance report for a period.
2. Observe the result and verify the full behavior: the report is generated and appears in the report history.
**Expected Result:** The report is generated — it appears in the report history, delivered exactly as documented.
**Priority:** Critical

### TC-SA-ACC-04-043 — Audit result reporting: audit results included in the report
**Type:** Positive
**Covers:** 4.4 → Audit result reporting: audit results included in the report
**Preconditions:** A Super Admin account is active; completed audits exist in a period.
**Steps:**
1. As a Super Admin, generate a compliance report for the period.
2. Open the report.
3. Observe the result and verify the full behavior: the audit results are included.
**Expected Result:** The audit results are included — they appear in the report, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-044 — Issue summary reporting: the open and resolved issue summary
**Type:** Positive
**Covers:** 4.4 → Issue summary reporting: the open and resolved issue summary in the report
**Preconditions:** A Super Admin account is active; issues exist in a period.
**Steps:**
1. As a Super Admin, generate a compliance report for the period.
2. Open the report.
3. Observe the result and verify the full behavior: the open and resolved issue summary is included.
**Expected Result:** The issue summary is included — it appears in the report, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-045 — Conformance statement: the statement per WCAG level
**Type:** Positive
**Covers:** 4.4 → Conformance statement: the conformance statement per WCAG level
**Preconditions:** A Super Admin account is active; compliance data exists.
**Steps:**
1. As a Super Admin, generate a compliance report.
2. Open the report.
3. Observe the result and verify the full behavior: the conformance statement per level is included.
**Expected Result:** The conformance statement is included — it appears per level, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-046 — Report export: the report exported (PDF, CSV)
**Type:** Positive
**Covers:** 4.4 → Report export: the report exported (PDF, CSV)
**Preconditions:** A Super Admin account is active; a report is generated.
**Steps:**
1. As a Super Admin, export the report as PDF.
2. Observe the result and verify the full behavior: the report is exported as a PDF file.
**Expected Result:** The export works — the PDF file is produced, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-047 — Report history: the generated reports with period and state
**Type:** Positive
**Covers:** 4.4 → Report history: the generated reports with their period and state
**Preconditions:** A Super Admin account is active; multiple reports are generated.
**Steps:**
1. As a Super Admin, open the report history.
2. Observe the result and verify the full behavior: the reports are shown with their period and state.
**Expected Result:** The report history is shown — the reports with their details are visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-048 — Rule: a report requires a valid period
**Type:** Negative
**Covers:** 4.4 → Rule: a report requires a valid period; a report with no period cannot be generated
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, attempt to generate a report with no period.
2. Observe the result and verify the full behavior: the generation is blocked with a validation message.
**Expected Result:** The generation is blocked — a valid period is required, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-049 — Rule: only completed audits are included; in-progress listed separately
**Type:** Positive
**Covers:** 4.4 → Rule: a report includes only completed audits in its period; in-progress audits are listed separately
**Preconditions:** A Super Admin account is active; completed and in-progress audits exist in a period.
**Steps:**
1. As a Super Admin, generate a compliance report for the period.
2. Open the report.
3. Observe the result and verify the full behavior: completed audits are in the results; in-progress audits are listed separately.
**Expected Result:** The separation is correct — completed in results, in-progress separate, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-050 — Rule: the conformance statement reflects the highest fully met level
**Type:** Positive
**Covers:** 4.4 → Rule: the conformance statement reflects the highest level fully met; a partially met level is stated as partial
**Preconditions:** A Super Admin account is active; a level is partially met.
**Steps:**
1. As a Super Admin, generate a compliance report.
2. Open the conformance statement.
3. Observe the result and verify the full behavior: the highest fully met level is stated; the partial level is stated as partial.
**Expected Result:** The statement is correct — the highest fully met level and partial state are shown, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-051 — Rule: a failed export is reported; the report is not marked exported
**Type:** Negative
**Covers:** 4.4 → Rule: a report export must succeed; a failed export is reported and the report is not marked exported
**Preconditions:** A Super Admin account is active; a report export fails.
**Steps:**
1. As a Super Admin, attempt to export the report when the export fails.
2. Observe the result and verify the full behavior: the failure is reported and the report is not marked exported.
**Expected Result:** The failure is reported — the report is not marked exported, delivered exactly as documented.
**Priority:** High

### TC-SA-ACC-04-052 — Rule: a report is immutable; a corrected report is new
**Type:** Positive
**Covers:** 4.4 → Rule: a report is immutable once generated; a corrected report is a new report referencing the original
**Preconditions:** A Super Admin account is active; a report is generated.
**Steps:**
1. As a Super Admin, attempt to correct the generated report.
2. Observe the result and verify the full behavior: a new report is created referencing the original; the original is unchanged.
**Expected Result:** The report is immutable — the correction is a new report, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-053 — Rule: the issue summary counts by severity and status at period end
**Type:** Positive
**Covers:** 4.4 → Rule: the issue summary counts issues by severity and status at the report period end
**Preconditions:** A Super Admin account is active; issues exist in a period.
**Steps:**
1. As a Super Admin, generate a compliance report for the period.
2. Open the issue summary.
3. Observe the result and verify the full behavior: the counts are by severity and status at the period end.
**Expected Result:** The counts are correct — by severity and status at period end, delivered exactly as documented.
**Priority:** Medium

### TC-SA-ACC-04-054 — Rule: report generation is audit-logged
**Type:** Positive
**Covers:** 4.4 → Audit logging of accessibility compliance reporting
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, generate a compliance report.
2. Open the audit log.
3. Observe the result and verify the full behavior: the generation is recorded with the actor and timestamp.
**Expected Result:** The report generation is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High