Failing test: X-Pack Accessibility Tests - Group 3.x-pack/test/accessibility/apps/group3/security_solution·ts - X-Pack Accessibility Tests - Group 3 Security Solution Accessibility Detections Create Rule Flow Custom Query Rule Define Step preview section meets a11y requirements

[kibanamachine]

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
ElementClickInterceptedError: element click intercepted: Element <button disabled="" type="button" class="euiButton euiSuperUpdateButton css-fq595v-euiButtonDisplay-m-isDisabled-fill-disabled" data-test-subj="previewSubmitButton" style="min-inline-size: 118px;">...</button> is not clickable at point (1485, 295). Other element would receive the click: <span class="euiToolTipAnchor css-jcaat8-euiToolTipAnchor-inlineBlock">...</span>
  (Session info: chrome=123.0.6312.58)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:510:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:443:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Task.exec (prevent_parallel_calls.ts:28:20)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:84:7)
    at RetryService.try (retry.ts:51:12)
    at Proxy.clickByCssSelector (find.ts:419:5)
    at TestSubjects.click (test_subjects.ts:164:5)
    at CommonPageObject.clickAndValidate (common_page.ts:553:5)
    at DetectionsPageObject.preview (index.ts:123:5)
    at Context.<anonymous> (security_solution.ts:57:15)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

[elasticmachine]

Pinging @elastic/security-detection-engine (Team:Detection Engine)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[banderror]

@yctercero Do you know who originally created this test file and who currently maintains it? All tests inside of it open the Rule Creation page and run some accessibility checks. The file is not mapped in CODEOWNERS to any team.

[yctercero]

@banderror I don't know. I think these were added by the accessibility team for us to maintain, but I'm not certain.

@peluja1012 do you remember the origin of these tests?

[kibanamachine]

New failure: kibana-on-merge - main

[kibanamachine]

New failure: kibana-on-merge - main

[kibanamachine]

New failure: kibana-on-merge - main