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

[meta] Accessibility tests #51456

Open
55 of 77 tasks
bhavyarm opened this issue Nov 22, 2019 · 7 comments
Open
55 of 77 tasks

[meta] Accessibility tests #51456

bhavyarm opened this issue Nov 22, 2019 · 7 comments
Assignees
Labels

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Nov 22, 2019

This is a meta issue for adding tests for accessibility

Kibana
Base tests and infrastructure
PR: #51893

OSS

Default Distribution

Management

Stack management

Ingest

Data
#79374

Alerts and Insights

Stack monitoring

Dev tools

Other solutions

Observability

Security ( see the comment section )

Machine learning

Enterprise search

Fleet

Add a table for skipped a11y tests

@bhavyarm
Copy link
Contributor Author

bhavyarm commented Mar 6, 2020

@rayafratkina @LeeDr

@bhavyarm
Copy link
Contributor Author

@bhavyarm to add skipped tests table and tracking.

@rashmivkulkarni
Copy link
Contributor

For the Security Solution a11y tests : here is what the team says
Gloria - Hey! before I left for vacation the a11y subject came back to me as a requirement from Kibana QA, I did a POC of using Cypress to write a11y tests to let the managers know how complex could be for us to start working on it and present the subject. My understanding so far is that a11y is not top priority right now since we have other challenges we need to face first, so for now things are going be on-hold.
https://github.com/elastic/kibana/blob/main/x-pack/test/accessibility/apps/security_solution.ts

@cuff-links
Copy link
Contributor

@rashmivkulkarni If the a11y tests for security solutions are the only ones left, I think that we should look at closing this issue and having another issue with just their tasks open and either assign it to them or we hang onto it but we shouldn't block this issue from being closed on account of those issues since it seems that it's deprioritized on their end.

@rashmivkulkarni
Copy link
Contributor

Except for Security Solution Accessibility Tests, rest all others are covered . I agree, this should not be blocking us from closing this issue. I have opened this issue to track security solution tests and have tagged the team. Closing this Meta issue.

cc @elastic/kibana-accessibility

@bhavyarm
Copy link
Contributor Author

bhavyarm commented Nov 7, 2022

@cuff-links @rashmivkulkarni re-opening this as there are two of my PRs linked to this not completed yet because it needs developer help. Thanks!

@bhavyarm bhavyarm reopened this Nov 7, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 7, 2022
@dmlemeshko dmlemeshko added the Team:QA Team label for QA Team label Nov 25, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-qa (Team:QA)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants