Demonstration report / v1.0
A sample report for a fictional demonstration store. It shows how issues, priorities and fixes are documented — it does not contain results from a real client.
The highest risk sits in main-menu operation, form error identification and focus visibility. These issues obstruct the purchase journey for keyboard and assistive-technology users.
Priority before the next release.
Include in the next sprint.
Fix with the related component.
Each finding connects observed user impact with an interface location and reference criterion.
| ID | Priority | Issue and impact | Criterion | Status |
|---|---|---|---|---|
| AO-01 | Critical | Submenu cannot be opened by keyboard Keyboard users cannot reach second-level categories. | 2.1.1 4.1.2 | Open |
| AO-02 | Critical | Error message is not associated with its field The screen reader does not identify which field needs correction. | 3.3.1 3.3.3 | Open |
| AO-03 | Important | Focus disappears on product card The current position is not visible during keyboard navigation. | 2.4.7 2.4.11 | Open |
| AO-04 | Important | Updated product count is not announced Filter results remain unavailable to assistive technology. | 4.1.3 | Backlog |
| AO-05 | Moderate | Wishlist icon has an ambiguous name The name does not include the product or button state. | 2.5.3 4.1.2 | Backlog |
The change is small, but documents both the technical layer and the required interaction.
<button
type="button"
class="menu-trigger"
aria-expanded="false"
aria-controls="category-menu"
>
Products
</button>
// On click or Enter/Space:
// 1. update aria-expanded,
// 2. reveal the panel,
// 3. manage focus using the agreed pattern,
// 4. support Escape and return focus.A prioritised backlog in the agreed format, file changelog, retest results, third-party limitations and a report version without VOIDLAB branding when the engagement is white-label.