Accessibility and content
Clear content and private examples
Useful, realistic examples without exposing account or learner records.
On this page
Content rules
- Name a concrete outcome: “Make room for your best ideas” has a consistent instructor, curriculum, actions, and workbook.
- Write action items a learner can actually complete, not vague encouragement.
- Use reserved example email domains and fictional people for all account and student records.
- Keep sample counts, prices, ratings, and revenue explicitly identified as fixtures; they are not claims of real results.
- Explain the next recovery step after failure and preserve local work when possible.
- Use descriptive resource labels, honest availability, and readable deadline/timezone context.
HTML and media boundaries
Course descriptions, instructions, and lesson text can contain HTML. Rendering components do not themselves establish sanitization policy; preserve upstream validation. Media alternatives, transcripts, file accessibility, and content rights need their own production review.
Evidence labels
Each capture records route, viewport, theme, density, font evidence, source revision, and checksum. The capture description explicitly identifies fictional data and simulated service responses. Marketing source screenshots are supplementary to new native app captures.
Source references
| File | Responsibility |
|---|---|
| src/components/TrixEditor.tsx | HTML authoring |
| src/components/courses-public/logged-in/CourseInformationTabs.tsx | HTML rendering |
| src/components/EmailCodeAuth.tsx | Recovery copy |
Interface examples
Native TeachKit interfaces with fictional course, account, and learner records. Service responses and media are isolated demonstrations; no customer data or live changes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-22 · Revision 903bbf05ca9d · Documentation v2.0.0