Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Search:WebCrawlers:ViewCrawler:Manage Domains page]Domain URL field missing name and help text from announcement #198900

Open
L1nBra opened this issue Nov 5, 2024 · 2 comments
Assignees
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team:Search WCAG A

Comments

@L1nBra
Copy link

L1nBra commented Nov 5, 2024

Description
All field names and their help text has to be accessible for the users. Especially for the ones using assistive technology as they cannot see what is on the screen.

Preconditions
Stateful Web Crawlers -> View Crawler -> Manage Domains page is opened.
Web crawler is added.
Use Screen Reader (NVDA).

Steps to reproduce

1.Navigate to Domain URL field while using only keyboard by pressing Tab key.
2.Observe screen reader.

UI elements + NVDA Speech Viewer
Image

Actual Result

  • The type of field is announced and what is already written in it.

Expected Result

  • The name of the field is announced, help text present for this field (below it) is announced and the type of the field with what is written in it.

Meta Issue

Kibana Version: 8.17.0-SNAPSHOT

OS: Windows 11 Pro

Browser: Chrome Version 130.0.6723.70 (Official Build) (64-bit)

Screen reader: NVDA

WCAG or Vendor Guidance (optional)

Related to: https://github.com/elastic/search-team/issues/8256

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-accessibility (Project:Accessibility)

@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 5, 2024
@L1nBra L1nBra added WCAG A impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Search defect-level-2 Serious UX disruption with workaround labels Nov 5, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 5, 2024
@L1nBra
Copy link
Author

L1nBra commented Nov 5, 2024

Same behavior observed on

  • Manage Domains page, Entry points tab for input field which appears when user activates Add entry point button.

UI elements + NVDA Speech Viewer
Image

  • Manage Domains page, Site maps tab for input field which appears when user activates Add sitemap button.

UI elements + NVDA Speech Viewer
Image

  • Manage Domains page (domain is added), for Copy button.

UI elements + NVDA Speech Viewer
Image

  • Manage Domains page (domain is added), Crawl rules tab. After adding crawl rule, fields in the table are missing names or labels.

UI elements + NVDA Speech Viewer
Image

  • Manage Domains page (domain is added), Extraction rules tab. When adding content field rule and selecting URL checkbox in Source section - URL pattern field is missing name or label.

UI elements + NVDA Speech Viewer
Image

  • Playground page. When adding AI connector and selecting Anthropic option for Service field, most of the newly appeared fields are announced without names when navigating to them (in a print screen only a few added).

UI elements + NVDA Speech Viewer
Image

  • Search Applications page. When creating Search application. In the flyout below Select indices title - field is announced without name.

UI elements + NVDA Speech Viewer
Image

@alexwizp alexwizp self-assigned this Nov 5, 2024
@L1nBra L1nBra changed the title [Stateful:WebCrawlers:ViewCrawler:Manage Domains page]Domain URL field missing name and help text from announcement [Search:WebCrawlers:ViewCrawler:Manage Domains page]Domain URL field missing name and help text from announcement Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect-level-2 Serious UX disruption with workaround impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Project:Accessibility Team:Search WCAG A
Projects
None yet
Development

No branches or pull requests

5 participants