Skip to content

fix: add accessibility specific requirements to agents file (#2190) #8888

fix: add accessibility specific requirements to agents file (#2190)

fix: add accessibility specific requirements to agents file (#2190) #8888

Triggered via push April 29, 2026 13:03
Status Failure
Total duration 1h 26m 37s
Artifacts 11

BuildJobs.yml

on: push
Check SHA in GH Actions
8s
Check SHA in GH Actions
Run code quality check
24m 31s
Run code quality check
Read versions file
4s
Read versions file
Plan E2E matrix
44s
Plan E2E matrix
Matrix: build
Matrix: Run automated end-to-end tests
Publish E2E test summary
34s
Publish E2E test summary
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 31 warnings
Run automated end-to-end tests (0)
Process completed with exit code 1.
Run automated end-to-end tests (0)
@mendix/heatmap-chart-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/heatmap-chart-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)
Run automated end-to-end tests (7)
Process completed with exit code 1.
Run automated end-to-end tests (7)
@mendix/accessibility-helper-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/accessibility-helper-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)
Run automated end-to-end tests (4)
Process completed with exit code 1.
Run automated end-to-end tests (4)
@mendix/skiplink-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)
Failed Test: visual comparison: packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js#L0
visual comparison: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.widget-skip-link').first() Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. Snapshot: skiplink-focused.png Call log: - Expect "toHaveScreenshot(skiplink-focused.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.widget-skip-link').first() Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. Snapshot: skiplink-focused.png Call log: - Expect "toHaveScreenshot(skiplink-focused.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js:72:32
Failed Test: skip link becomes visible when focused via keyboard: packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js#L0
skip link becomes visible when focused via keyboard: Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, 0)" Received string: "none" - Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, 0)" Received string: "none" at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js:33:27
Failed Test: skip link is present in DOM but initially hidden: packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js#L0
skip link is present in DOM but initially hidden: Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, -48)" Received string: "none" - Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, -48)" Received string: "none" at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js:21:27
Failed Test: sets target attributes even though target is conditionally shown after being hidden: packages/pluggableWidgets/accessibility-helper-web/e2e/AccessibilityHelper.spec.js#L0
sets target attributes even though target is conditionally shown after being hidden: Test timeout of 30000ms exceeded. - Test timeout of 30000ms exceeded.
Failed Test: updates target attributes using a NF: packages/pluggableWidgets/accessibility-helper-web/e2e/AccessibilityHelper.spec.js#L0
updates target attributes using a NF: Test timeout of 30000ms exceeded. - Test timeout of 30000ms exceeded.
Failed Test: renders heatmap chart with custom color and compares with a screenshot baseline: packages/pluggableWidgets/heatmap-chart-web/e2e/HeatMapChart.spec.js#L0
renders heatmap chart with custom color and compares with a screenshot baseline: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerCustomColor') 13311 pixels (ratio 0.06 of all image pixels) are different. Snapshot: heatmapChartCustomColor.png Call log: - Expect "toHaveScreenshot(heatmapChartCustomColor.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerCustomColor') - locator resolved to <div class="mx-name-containerCustomColor">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 13311 pixels (ratio 0.06 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerCustomColor') - locator resolved to <div class="mx-name-containerCustomColor">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 13311 pixels (ratio 0.06 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerCustomColor') 13311 pixels (ratio 0.06 of all image pixels) are different. Snapshot: heatmapChartCustomColor.png Call log: - Expect "toHaveScreenshot(heatmapChartCustomColor.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerCustomColor') - locator resolved to <div class="mx-name-containerCustomColor">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 13311 pixels (ratio 0.06 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerCustomColor') - locator resolved to <div class="mx-name-containerCustomColor">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 13311 pixels (ratio 0.06 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/heatmap-chart-web/e2e/HeatMapChart.spec.js:22:48
Plan E2E matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run automated end-to-end tests (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Publish E2E test summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run code quality check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Calendar.ts#L10
`./SizeContainer` import should occur after import of `./CalendarLoader`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Calendar.ts#L9
`./Toolbar` import should occur after import of `./CalendarLoader`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Calendar.ts#L6
`react-big-calendar` import should occur after import of `moment`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Calendar.ts#L4
`../utils/namespaces` import should occur after import of `./CalendarLoader`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Calendar.ts#L3
`./Alert` import should occur after import of `react-big-calendar/lib/addons/dragAndDrop`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Calendar.ts#L1
`react` import should occur after import of `moment`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Button.ts#L2
`classnames` import should occur before import of `react`
Run code quality check: packages/customWidgets/calendar-custom-web/src/components/Alert.ts#L2
`classnames` import should occur before import of `react`
Run code quality check: packages/customWidgets/calendar-custom-web/src/Calendar.webmodeler.ts#L6
`./utils/style` import should occur before import of `./utils/validation`
Run release task on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run release task on ubuntu-latest: packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on ubuntu-latest: packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on ubuntu-latest: packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on ubuntu-latest: packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run release task on windows-latest: packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on windows-latest: packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on windows-latest: packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
Run release task on windows-latest: packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`

Artifacts

Produced during runtime
Name Size Digest
ctrf-reports-0
2.1 KB
sha256:ce29726c5a53fe98fa9d084081285af9994c9fff86db2879327007c68267e912
ctrf-reports-1
3.42 KB
sha256:90cd2883ae4595b7a2035ab04e19a12f3e5ef28580f0a0d4edf0aca8ef54c29e
ctrf-reports-2
3.25 KB
sha256:542c6166dc84f2e32a64b277e5c518328fecf0f95629cb1b9a4e3d41641c6e59
ctrf-reports-3
5.33 KB
sha256:7dd21e2eae67bf84295628d448100e28ed86e441c9baa920e13e235ee88cb880
ctrf-reports-4
5.69 KB
sha256:dfb6b8b218225e82cff2bf48d75c34edbfb32fdf67435f4a6b1252a3cca4c123
ctrf-reports-5
4.47 KB
sha256:86b3b5da86dd421676b99472bda7524e9cedf60c00d0384dbac3c3feb8244b3c
ctrf-reports-6
2.98 KB
sha256:f6dda45c24b57aa5b9fcd0239fa9671df5ecd16559424aff7c4b335a8117d53a
ctrf-reports-7
1.88 KB
sha256:2405b5df3208169ad7479c035e69bace579a72659e67bd4f01557dfc9fd7ae3b
test-screenshot-results-0
3.77 MB
sha256:14ff5470c6a4604fc0f54997fbd0088cf8fbbc70851303c63b7136d86f969ba0
test-screenshot-results-4
5.36 MB
sha256:1d464f360ec7a4f7ba4f268ee380595bebfa7926362c6a745901371e52d7584d
test-screenshot-results-7
140 KB
sha256:d422257fc1640eaf8ddb1611afcaa53b9b23ee5e959809e69bbd0e491ccf55f4