elastic/kibana

`Home` > `Cases` > `Create a case`- Tools in toolbar are not presented as a group

Open

#194,954 建立於 2024年8月9日

在 GitHub 查看
 (7 留言) (0 反應) (1 負責人)TypeScript (19,065 star) (8,021 fork)batch import
KibanaPlatEngineKTLOProject:AccessibilityTeam:CasesWCAG Abugdefect-level-2good first issueobs-accessibilty

描述

Point of contact

@petrklapka

Description

Home > Project Settings > Integrations- Radio buttons (Recommended, Elastic Agent, Beats) do not have context conveyed via screen reader

Steps to recreate

Pre-requisite: Screen reader is activated

  1. Navigate to the Serverless Observability Solution instance.
  2. Click Cases in Left Nav
  3. Select Create a case (blue button in upper-right)
  4. Keyboard navigate to Description field and navigate through the text toolbar

Expected Result: -When tabbing to the tools menu, user tabs to the first tool and is informed that it is a group of tools for text input. User then navigates and selects the toolbar via arrow keys. The next tab event moves out of the toolbar to the next focusable element.

Actual Result: -Tab key moves focus through each tool in the toolbar.

Screenshots or Trace Logs

cases_create_text_field_toolbar

Proposed solution

Acceptance criteria

  • Axe tests do not report violations
  • e2e test suite passes with zero violations

WCAG or Vendor Guidance (optional)

貢獻者指南

技術棧
typescriptreacthtmlcss
領域
frontendaccessibility
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of ARIA toolbar roleFamiliarity with React and Kibana codebaseBasic knowledge of screen reader behavior
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Investigate the Cases plugin's toolbar component (likely in x pack/plugins/cases/public/components) to understand its current implementation. The toolbar should use role='toolbar' and support arrow key navigation between tools. Review existing e2e tests for accessibility violations and ensure the fix aligns with WCAG SC 1.3.1. Check the referenced issue for similar patterns in other Kibana toolbars.