Agent-built demo / After audit
Folio
Client portal · Nov 8, 2026
3 measured views. Local app. Design grades compare the actual screen with published product references. N/A means there was no applicable sample. Unverified means evidence was insufficient.
Product specificity and generic signals · A
Both widths identify a client commission workflow through Atlas Foundry, Proof 02, Atlas identity, Review, Due 14 Nov and Review proof. Aperture annual and Field recordings provide distinct neighboring records with different statuses. (/projects)
Visual specificity before deductions A. Weighted design base A. Distinct signal deductions 0.
Product specificity supplies 55% of the base, and the five visual design dimensions share 45%. Round the base to the nearest letter. Each distinct verified generic signal lowers it by one letter, down to F. Foundations are reported separately. The detector ceiling is A. Vision reviewed 1 of 1 measured routes.
- Template copy · not observed
- No instance was identified in the reviewed views.
- Gradient hero · not observed
- No instance was identified in the reviewed views.
- Emoji bullets · not observed
- No instance was identified in the reviewed views.
- Default shadcn grays · not observed
- No instance was identified in the reviewed views.
- Purple on white · not observed
- No instance was identified in the reviewed views.
- Centered everything · not observed
- No instance was identified in the reviewed views.
Compared with the 2026 references
- /projects · Like the supplied OpenProject workspace overview, Folio uses strong headings and modest metadata to establish project context. Folio makes the immediate review decision particularly clear through Atlas’s status and Review proof link. Responsible people are not visible in either Folio capture. OpenProject · project workspace overview
Visual design
- Hierarchy
- B
- At 1440, a large featured Atlas commission precedes two compact records. At 390, Atlas becomes a readable stacked card. The blank rectangle beside All projects draws unexplained attention at both widths. (/projects)
- Typography
- C
- A visible text label renders below 12 px. (/projects, 1440 px.)
- Spacing
- A
- At 1440, generous margins and horizontal rules separate the introduction and commissions. At 390, consistent side margins and stacked records preserve clear grouping; the next record continues below the viewport naturally. (/projects)
- Copy and labels
- C
- Review proof, proof numbers, statuses and due dates support the task at both widths. The prominent blank rectangle has no visible explanation at either width, creating a material labeling gap. (/projects)
- Imagery
- A
- At 1440, Atlas’s typographic identity artwork anchors the featured commission, with distinct book and recording artwork below. At 390, the Atlas crop retains its identity and Aperture’s thumbnail remains recognizable. (/projects)
Foundations · D
Contrast, responsive layout and keyboard reach are sampled separately. The foundations grade is the lowest verified result in this group.
- Color contrast
- D
- Opaque text measures 1.13:1 against its solid background (3:1 target). (/projects, 1440 px.)
- Responsive layout
- A
- All sampled viewports fit without horizontal overflow and contained readable text. Verified across 3 measured views.
- Keyboard access
- A
- Tab reached two visibly focused controls and Shift+Tab returned to the first. Verified across 3 measured views.
Fix these first
- Adjust the foreground or its solid background, then remeasure this label.Color contrast · /projects · 1440 px
- Increase the label size and check its wrapping at phone width.Typography · /projects · 1440 px
Evidence from the screens
Gray blocks conceal form values or sensitive text. Numbered outlines identify measured issues.
- A visible text label renders below 12 px.
- Opaque text measures 1.13:1 against its solid background (3:1 target).
- A visible text label renders below 12 px.
- Opaque text measures 1.13:1 against its solid background (3:1 target).
- A visible text label renders below 12 px.
- Opaque text measures 1.13:1 against its solid background (3:1 target).
Independent task review
The reviewer assesses each route against its user task using desktop and phone evidence. Its task grades describe the interaction evidence available for that route.
/projects
Audit of Folio’s /projects client workspace at 1440×900 and 390×844. Find Atlas identity, Proof 02, marked Review and due 14 Nov, then select Review proof.
Reviewed at 1440 × 900 and 390 × 844.
- Task hierarchy
- B
- At 1440, Atlas identity dominates the project list with large artwork and a Review proof link. At 390, its image, status and action remain together above the other commissions. The large unlabeled rectangle beside All projects competes with the clear review path at both widths.
- Landing message
- N/A
- This is an internal client workspace. Client commissions and the supporting sentence explain its working purpose at both widths.
- Interaction feedback
- Unverified
- Neither supplied check activates Review proof. Destination, loading feedback, failure handling and return-state persistence remain unobserved.
- Access and recovery
- C
- At both widths, a prominent control-shaped rectangle has no visible label, leaving its purpose unclear. Checks establish that a visible Tab target was reached at each width, but not full keyboard reach or accessible names. At 390, Atlas’s action remains visible; recovery paths were not exercised.
- Release evidence
- Unverified
- The supplied local captures show /projects at both widths. Checks report one primary heading, eight visible controls and a reached Tab target per width. Successful proof navigation, recovery behavior and deployed release conditions are not established.
First action
Resolve the unlabeled rectangle beside All projects: give it a visible, purpose-specific label if interactive, or remove its control-like appearance if decorative. Keep Atlas identity’s Review proof action prominent.
How to verify At 1440 and 390, confirm the rectangle’s purpose is visually clear and any interactive element has an accessible name and visible keyboard focus. Activate Atlas identity’s Review proof with Enter and confirm it opens Proof 02. Contrast measurements, complete keyboard traversal and recovery checks remain outstanding.
What a repair could look like
Folio is an agent-built client portal demo. Both captures show the same task.
