A11y testing for mobile

[ScharfViktor]

// Mobile
{
      name: 'a11y-mobile-chrome',
      use: { 
        ...devices['Pixel 5'] 
      },
    },
    {
      name: 'a11y-mobile-safari',
      use: { 
        ...devices['iPhone 12'] 
      },
    },
    
    // Tablet
    {
      name: 'a11y-tablet',
      use: { 
        ...devices['iPad Pro'] 
      },

[kulmann]

This would make sense not only for a11y but also in general. Checking if the web ui works on various viewport sizes is a good idea. We had that in the past, was quite useful. However, it also multiplies our test compute time by the number of browsers and viewports. Of course they could run in parallel, but still, that's a lot of compute... do you have an idea or an opinion on this?

[ScharfViktor]

Yes, of course, maybe we don't need to run all the tests, just some of them.
I suggest starting with the a11y tests, then connecting the smoke tests, and so on.