Rather than dry learning, maybe using static tooling + browser testing are great ways to find issues and then learn about why its an issue and whats the possible fix.
I would say one of the best ways, I have learned is from eslint
Using axe chrome plugin for finding accessibility issues
Manual testing like using keyboard and voice over also helps.
Once you know the issue, there are tons of good resources to learn about them. Many times I have seen folks don't even know that there is an issue in the first place.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Rather than dry learning, maybe using static tooling + browser testing are great ways to find issues and then learn about why its an issue and whats the possible fix.
Once you know the issue, there are tons of good resources to learn about them. Many times I have seen folks don't even know that there is an issue in the first place.