Grafico

Outcome: Complete the task with Grafico (Chart). User context: Un grafico a linee settimanale rivela un backlog in crescita. Una tabella dà i valori esatti per gli screen reader e i controlli. Recommended pattern: Grafico (Chart). Why it fits: Prima indica la domanda. Poi scegli un grafico che renda chiara la comparazione necessaria. Do not use it when: Evita decorazioni in 3D, grafici con assi fuorvianti, differenze basate solo sul colore e grafici che nascondono numeri semplici. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): Nessun singolo standard ufficiale controlla l'intero termine. Il suo significato può cambiare tra team, piattaforme o framework. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.