Add option to run the test with `reducedMotion: 'reduce'`

[Th3S4mur41]

Using view transitions to fade-in content on scroll generates false positives.
The fade-in effect is however disabled when user preference for reduced motion is set to reduce.

I would be great to have an option to be able to toggle the option for the scanner too

[helen]

Yup being able to run with and without reduced motion absolutely makes sense for many reasons. Related: #120

[helen]

Coming back with a question @Th3S4mur41: how do you envision yourself using this, either practically speaking, ideally, or both? That is, are thinking you'd run this manually with input parameters, or as a matrixed job, or something else? That way we can find the best way(s) to support passing options to Playwright and have corresponding docs :)

[Th3S4mur41]

Hey @helen I guess a way to pass well-known options as input parameters would be fine...
This would be similar to what we do with playwright for instance and would also work for light or darkscheme

export default defineConfig({
	use: {
		baseURL: config.baseURL,
		reducedMotion: 'reduce',
	},
	projects: [
		{
			name: 'chromium',
			use: {
				...devices['Desktop Chrome'],
				colorScheme: 'light',
			},
			// Run all tests (a11y and performance) in chromium light mode
		},
	],
});

So this could translate to:

- name: 'Run Accessibility Scanner'
  uses: github/accessibility-scanner@v2
  with:
    urls: ${{ steps.extract-urls.outputs.urls_list }}
    repository: ${{ github.repository }}
    token: ${{ secrets.GH_TOKEN }}
    cache_key: 'accessibility-scan-${{ github.event.workflow_run.head_branch }}-${{ github.event.workflow_run.head_sha }}'
    skip_copilot_assignment: true

    # Scanner settings
    reducedMotion: 'reduce'
    colorScheme: 'light'

Alternatively, if you don't want to add a too many hard coded inputs, as multiline string

- name: 'Run Accessibility Scanner'
  uses: github/accessibility-scanner@v2
  with:
    urls: ${{ steps.extract-urls.outputs.urls_list }}
    repository: ${{ github.repository }}
    token: ${{ secrets.GH_TOKEN }}
    cache_key: 'accessibility-scan-${{ github.event.workflow_run.head_branch }}-${{ github.event.workflow_run.head_sha }}'
    skip_copilot_assignment: true

    # Scanner settings
    settings: |
      reducedMotion=reduce
      colorScheme=light

But if this the preferred way, maybe env variables is the better solution ?

- name: 'Run Accessibility Scanner'
  uses: github/accessibility-scanner@v2
  with:
    urls: ${{ steps.extract-urls.outputs.urls_list }}
    repository: ${{ github.repository }}
    token: ${{ secrets.GH_TOKEN }}
    cache_key: 'accessibility-scan-${{ github.event.workflow_run.head_branch }}-${{ github.event.workflow_run.head_sha }}'
    skip_copilot_assignment: true

  env:
    # Scanner settings
    reducedMotion: 'reduce'
    colorScheme: 'light'

From a user perspective, I guess either solution would work fine and could be used in a matrix environment too.
So, I guess it's more about which one is more secure and easier to maintain when options keep evolving

[helen]

We merged in the ability to do this via an input variable, so once we cut a new release (give it another week or two, the team is currently having an in-person meetup) you should be able to do this!

[lindseywild]

This has been released in v2.10.0 😄 Let us know if you run into any issues or bugs!