Dyslexia Project — Content Audit | Notion

<aside> 🔥 Skip to the Content Audits per Prototype.

</aside>

🎯 Purpose

Perform a content audit of current deliverables to assess:

What is good (strengths)

What is missing (gaps)

What needs improvement (opportunities)

👥 Assignments

Deliverable	Person Responsible	Deadline	Notes
Cognitive Game Puzzle Screens	Nirali
George	5 May	Nirali: Musa Welcome Screen, Musa Game Story Intro, Game Intro Screens, Training Screens

George: the animals :) | | Prototype Copy Audit (Student Profile) | Vanessa Ashley | 5 May | | | Prototype Copy Audit (Sign Up) | Anya | 5 May | | | Prototype Copy Audit (Dashboard) | Emmanuel | 5 May | |

🛠️ Scope

Documents to Audit:
- UXD B Cognitive Game Puzzle Screens - UXD B Cognitive Game Puzzle Screens
- UXD Prototype (Student Profile, Sign Up, Dashboard) - UXD Prototype with Copy Annotations and Feedback
Reference Documents:
- Content Style Guidelines (Educator Side) - Content Style Guide
- Competitor & Comparator Analysis - Competitor & Comparator Analysis

<aside> 🔥 Content Audit

Master Content Audit

Onboarding Content Audit

Cognitive Game Puzzle Screens

Student Profile (Educator View) - - In Progress -Emmanuel

Student Profile - Dashboard

</aside>

👀 What to Look For

Area	Questions to Ask
Content Quality	Is the language consistent with our style guide? Does it use appropriate language and tone for educators and dyslexic students, focusing on user-centric language?
Inclusivity	Is the content clear and simple for dyslexic users?
Tone of Voice	Does it match the intended tone for our audiences (students/educators)?
Accessibility	Is the content accessible (easy to read, avoids cognitive overload, text-to-voice feature)?
Gaps	Are any flows/screens missing necessary copy?
Feedback Integration	Has previous copy feedback been properly addressed?
Usability	Are the screens optimized for different platforms?
Findability	Can users easily find information, content, or features that they need? Is there a clear hierarchy?

📄 Content Audit Template (for each Deliverable)

Screen/Page	Content Element	Action	Notes (Why?)	Reference to Guidelines?	Suggestions
(e.g., Sign Up - Welcome Screen)	(e.g., Title, Button Label)	Keep ✅:
Remove ❌:
Improve ⚡:	(Brief explanation)	(Which guideline or competitor insight applies)	Maybe add XXX

Quick Example:

Screen/Page	Content Element	Good ✅	Missing ❌	Needs Improvement ⚡	Notes (Why?)	Reference to Guidelines?	Suggestions
Sign Up - Welcome Screen	Button Label "Start"	✅	❌	❌	Clear and simple for dyslexic users	Tone matches style guide (p.3)	XXX
Dashboard	Progress Tracker Label	❌	✅	❌	No label explaining what progress bar shows	Add clarity based on best practices for cognitive load	XXX
Cognitive Game Puzzle	Instruction Text	❌	❌	⚡	Text too dense, hard to scan quickly	Needs chunking (style guide p.5)	XXX

Actions & Their Definitions

Keep: No changes needed; the content is clear and effective.
Remove: Is this feature/item necessary? If not, remove it.
Improve: Make it better (Suggest specific enhancements to make the content clearer, more engaging, or more effective)

Notes:

Ask: Do we have the GO to add new comments and edits on the prototype?
- Once Emmanuel is finished do the content audit one pager. By Wednesday.
- Add all comments in a table based on priority. By end of this week. 1. Previous comments. 2. Consistency.
  - We’ll say (Sprint 2) priority is replacing Lorem Ipsum.
The Games: Student - should have a content guideline. (Sprint 2)
Lorem Ipsum? ok.