Curious about the accessibility aspect

[gilangabdian]

Summary

I'm still using Chrome now, are there any drawbacks to accessibility in the future? I'm just curious why Chrome isn't recommended for screen readers.

Additional information

No response

Example

No response

[barry166]

That recommendation is about screen-reader/browser pairings, not a warning that Chrome will make your site less accessible.

Screen readers depend a lot on the browser accessibility tree, and the most consistently tested pairs are usually NVDA + Firefox on Windows and VoiceOver + Safari on macOS/iOS. You can keep using Chrome for normal development, but for accessibility verification don't rely only on Chrome DevTools or Lighthouse; test with at least one real screen reader/browser pair that your users are likely to use.

[gilangabdian]

Thank you for your answer, but actually we can still do it if we don't download Firefox, right? I’m not really a fan of having too many browser options—it just overwhelms me—and using Chrome with the NVDA Screen Reader works fine too, doesn't it? Although, admittedly, it’s not exactly the recommended combination.

[barry166]

Yes, you can keep using Chrome. The recommendation is not "Chrome is inaccessible"; it is about how much confidence you get from a particular test setup.

Chrome + NVDA is useful, and Chrome DevTools/Lighthouse can catch many basic issues. If the accessibility behavior is important enough to sign off, also test at least one common real-user pairing such as NVDA + Firefox on Windows or VoiceOver + Safari on macOS/iOS. You do not need every browser installed for day-to-day development.