# 3. Content Accessibility

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. Content Accessibility

### 3.1 Accessible Content Standards Enforcement
**What it does:** The Super Admin enforces accessible content standards so that all published content meets a defined accessibility baseline before it is learner-visible.

**Sub-features:**
- Standards definition: the accessible content standards applied to each content type
- Pre-publication check: an accessibility check run on content before publication
- Standards checklist: the checklist items a content item must satisfy
- Enforcement mode: advisory (flag only) or blocking (publication prevented)
- Standards by content type: the standards applied per content type (lesson, worksheet, video, podcast)
- Standards report: the standards compliance state per content item
- Available on web
- Event logging (action performed)
- Audit logging of accessible content standards enforcement

**Super Admin User Journey:**
1. As a Super Admin, open the accessible content standards configuration.
2. Define the standards and checklist items per content type.
3. Set the enforcement mode (advisory or blocking) per content type.
4. Save and verify a content item failing the standards is flagged or blocked on publication.

**Rules & Edge Cases:**
- In blocking mode, a content item failing the standards cannot be published until the failures are resolved.
- In advisory mode, a failing content item is flagged but can still be published; the flag is visible to reviewers.
- A content type with no standards defined is not checked; it is marked as not subject to standards.
- The pre-publication check runs automatically on every publication attempt.
- A content item re-checked after fixes shows an updated compliance state.
- Standards changes apply to publication attempts after the change; already-published content is not retroactively blocked.
- Standards configuration changes are audit-logged with the actor and timestamp.

### 3.2 Alt-Text Management
**What it does:** The Super Admin manages alternative text (alt-text) for images and media so screen reader users and image-failed views receive a text description.

**Sub-features:**
- Alt-text requirement: alt-text required or optional per content type and media role
- Alt-text entry: alt-text entered or edited per image and media item
- Alt-text review: alt-text reviewed for accuracy before publication
- Alt-text coverage: the share of media items with alt-text per content type
- Missing alt-text list: the media items missing required alt-text
- Bulk alt-text import: alt-text imported in bulk for a set of media items
- Available on web
- Event logging (action performed)
- Audit logging of alt-text management

**Super Admin User Journey:**
1. As a Super Admin, open the alt-text management for a content item.
2. Review the media items and their alt-text state.
3. Enter or edit alt-text for items missing it, or import alt-text in bulk.
4. Review the alt-text for accuracy and mark the review complete.
5. Verify the alt-text coverage and the missing alt-text list update.

**Rules & Edge Cases:**
- A media item with a content role (informative) requires alt-text; a decorative role does not.
- Alt-text is published only after review; an unreviewed alt-text is not learner-visible.
- Alt-text length is bounded; an over-length alt-text is rejected with a validation message.
- A bulk import row with a missing or invalid media reference is skipped and reported.
- A media item with no alt-text and a content role appears in the missing alt-text list.
- Re-entering alt-text for a reviewed item resets its review state to unreviewed.
- Alt-text changes are audit-logged with the actor and timestamp.

### 3.3 Screen Reader Compatibility
**What it does:** The Super Admin manages screen reader compatibility so content is structured and labeled for screen reader output.

**Sub-features:**
- Semantic structure check: a check that content uses semantic headings and landmarks
- ARIA label management: ARIA labels managed for interactive elements
- Reading order definition: the reading order defined for complex layouts
- Screen reader test checklist: the checklist for verifying screen reader output
- Compatibility report: the screen reader compatibility state per content item
- Available on web
- Event logging (action performed)
- Audit logging of screen reader compatibility management

**Super Admin User Journey:**
1. As a Super Admin, open the screen reader compatibility view for a content item.
2. Run the semantic structure check and review the findings.
3. Manage ARIA labels for interactive elements and define the reading order.
4. Complete the screen reader test checklist.
5. Verify the compatibility report reflects the resolved state.

**Rules & Edge Cases:**
- A content item with missing semantic headings is flagged in the compatibility report.
- An interactive element without an ARIA label is flagged; the label is required for publication in blocking mode.
- The reading order must be a valid sequence; an invalid or circular order is rejected.
- A content item not tested against the checklist is marked as untested, not compliant.
- Compatibility findings are resolved individually; the report updates per finding.
- A content item with all findings resolved and the checklist complete is marked compliant.
- Compatibility changes are audit-logged with the actor and timestamp.

### 3.4 Accessible PDF Generation
**What it does:** The Super Admin configures accessible PDF generation so exported documents (worksheets, reports, study material) are usable by screen readers.

**Sub-features:**
- Accessible PDF enablement: accessible PDF generation toggled on or off per export type
- Tagged PDF structure: tagged PDF structure generated for document semantics
- Document language tag: the document language tag set per export
- PDF alt-text: alt-text carried into the PDF for embedded images
- PDF outline: the document outline (bookmarks) generated from headings
- Accessible PDF validation: a validation run on generated PDFs
- Available on web
- Event logging (action performed)
- Audit logging of accessible PDF generation configuration

**Super Admin User Journey:**
1. As a Super Admin, open the accessible PDF generation configuration.
2. Enable accessible PDF generation per export type.
3. Set the document language tag and confirm tagged structure and outline generation.
4. Save and generate a sample PDF.
5. Run the accessible PDF validation and verify the PDF passes.

**Rules & Edge Cases:**
- Accessible PDF generation applies only to enabled export types; other exports produce standard PDFs.
- A generated accessible PDF must include a document language tag; a missing tag fails validation.
- Embedded images without alt-text are flagged in the validation; the PDF is not marked accessible.
- The PDF outline is generated from semantic headings; a document with no headings has no outline.
- A validation failure prevents the PDF from being marked accessible; it can be regenerated after fixes.
- Tagged PDF structure is required for an accessible PDF; an untagged PDF fails validation.
- Configuration changes are audit-logged with the actor and timestamp.