Accessibility and content
Content and edge cases
Write actionable product copy and test the content conditions that ideal screenshots omit.
On this page
Copy rules
| Context | Rule | Example |
|---|---|---|
| Project | Name an outcome or useful deliverable | Atlas customer portal |
| Task | Begin with a concrete action and sufficient context | Review the account settings prototype |
| Space | Name an ongoing area of responsibility | Client work |
| Action | Describe the result of activation | Create project |
| Error | Explain the constraint and useful correction | The block must end after it starts. |
| Removal | Name the affected object and provide recovery | Atlas customer portal removed from this day |
| Read-only | Explain why editing is unavailable | Past agenda · Read only |
Content stress cases
- Long project names and two-line next actions; full content must remain available in detail views.
- Several tasks with similar titles; supporting project context should distinguish them.
- No projects, no Spaces, no Inbox items, no search matches, and no assigned schedule days.
- Invalid URLs, absent descriptions, past events, overlapping time, and an end before the start.
- Local loading or save failure; do not present missing data as confirmed emptiness.
- Alternative languages, system font differences, longer date formats, and browser zoom.
Honest product language
Use Changes saved only where the actual persistence contract supports it. In the current profile/preferences source, that message is local UI feedback. Do not invent user research quotes, retention improvements, or accessibility outcomes to strengthen the portfolio narrative.
Fixture policy
All captured record content is fictional and intentional. example.org links and addresses identify demo content. Screens showing unsupported or unverified outcomes should be omitted or clearly labeled instead of filled with invented success.
Examples from the app
Actual Radarist components with fictional data. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision 0103e2549959 · Documentation v0.1