# 4. Accessibility Compliance User Type: **Super Administrator** Source: *Mi Digital Academy - Education CRM Features Document* --- ## 4. Accessibility Compliance ### 4.1 WCAG Compliance Tracking **What it does:** The Super Admin tracks the platform's compliance with the Web Content Accessibility Guidelines (WCAG) across success criteria, so the overall compliance posture is always visible. **Sub-features:** - WCAG version selection: the WCAG version tracked (e.g., 2.1, 2.2) - Conformance level: the target conformance level (A, AA, AAA) - Success criteria catalog: the WCAG success criteria with their compliance state - Compliance score: the overall compliance score per area and platform-wide - Compliance trend: the compliance score over time - Criteria detail: the evidence and state per success criterion - Available on web - Event logging (action performed) - Audit logging of WCAG compliance tracking **Super Admin User Journey:** 1. As a Super Admin, open the WCAG compliance tracking view. 2. Select the WCAG version and target conformance level. 3. Review the success criteria catalog and their compliance state. 4. Check the compliance score and trend. 5. Open a criterion to review its evidence and state. **Rules & Edge Cases:** - The compliance score is computed only over criteria applicable to the selected version and level. - A criterion marked not applicable is excluded from the score, not counted as a failure. - A criterion with no evidence is treated as unverified, not compliant. - The conformance level must be at or above the criteria being tracked; a mismatch is flagged. - The compliance trend is computed over a fixed window; an empty window shows no trend. - A change in a criterion's state updates the score immediately. - Tracking configuration changes are audit-logged with the actor and timestamp. ### 4.2 Accessibility Audit Scheduling **What it does:** The Super Admin schedules accessibility audits so the platform is periodically assessed against the accessibility standards. **Sub-features:** - Audit creation: an accessibility audit created with scope and criteria - Audit scheduling: audits scheduled for a date and recurrence - Audit assignment: audits assigned to an auditor or team - Audit scope: the areas and content types included in an audit - Audit status: the audit state (scheduled, in progress, completed, overdue) - Audit list: the audits with their schedule, scope, and status - Available on web - Event logging (action performed) - Audit logging of accessibility audit scheduling **Super Admin User Journey:** 1. As a Super Admin, open the accessibility audit scheduling view. 2. Create an audit with a scope, criteria, and schedule. 3. Assign the audit to an auditor or team. 4. Save and verify the audit appears in the audit list with its status. 5. Verify the audit transitions to in progress when started and completed when finished. **Rules & Edge Cases:** - An audit requires a non-empty scope; an audit with no scope cannot be created. - An audit requires an assignee; an unassigned audit is held in draft, not scheduled. - A scheduled audit in the past with no completion is marked overdue. - An audit recurrence must be a valid interval; an invalid recurrence is rejected. - An audit cannot be completed until all in-scope items are assessed. - A completed audit produces a result that feeds the compliance tracking. - Audit changes are audit-logged with the actor and timestamp. ### 4.3 Issue Tracking and Resolution **What it does:** The Super Admin tracks accessibility issues found during audits and day-to-day use, and manages their resolution to closure. **Sub-features:** - Issue creation: an accessibility issue created with description, location, and severity - Issue assignment: issues assigned to an owner - Issue severity: the severity level (critical, high, medium, low) - Issue status: the issue state (open, in progress, resolved, verified, closed) - Issue resolution: the resolution note and fix reference per issue - Issue list: the issues with their severity, status, and owner - Issue aging: the time an issue has been open per severity - Available on web - Event logging (action performed) - Audit logging of accessibility issue tracking and resolution **Super Admin User Journey:** 1. As a Super Admin, open the accessibility issue tracking view. 2. Create an issue with a description, location, and severity. 3. Assign the issue to an owner and set its status. 4. Track the issue through in progress to resolved. 5. Verify the resolution and close the issue, and check the issue aging. **Rules & Edge Cases:** - An issue requires a description and a location; an issue missing either cannot be created. - An issue requires an owner before it can move to in progress. - An issue cannot be closed until it is resolved and verified. - A resolution requires a resolution note; a resolved issue with no note is flagged. - Issue aging is computed from the open timestamp; a closed issue stops aging. - A critical issue open beyond its target window is escalated automatically. - An issue linked to an audit carries the audit reference. - Issue changes are audit-logged with the actor and timestamp. ### 4.4 Compliance Reporting **What it does:** The Super Admin generates accessibility compliance reports so the compliance posture, audit results, and issue state can be reviewed and shared. **Sub-features:** - Compliance report generation: a compliance report generated for a period - Audit result reporting: audit results included in the report - Issue summary reporting: the open and resolved issue summary in the report - Conformance statement: the conformance statement per WCAG level - Report export: the report exported (PDF, CSV) - Report history: the generated reports with their period and state - Available on web - Event logging (action performed) - Audit logging of accessibility compliance reporting **Super Admin User Journey:** 1. As a Super Admin, open the accessibility compliance reporting view. 2. Generate a compliance report for a period. 3. Review the audit results, issue summary, and conformance statement. 4. Export the report. 5. Verify the report appears in the report history. **Rules & Edge Cases:** - A report requires a valid period; a report with no period cannot be generated. - A report includes only completed audits in its period; in-progress audits are listed separately. - The conformance statement reflects the highest level fully met; a partially met level is stated as partial. - A report export must succeed; a failed export is reported and the report is not marked exported. - A report is immutable once generated; a corrected report is a new report referencing the original. - The issue summary counts issues by severity and status at the report period end. - Report generation is audit-logged with the actor and timestamp.