Testing accessibility issues at components level is a good first step to make your product accessible.
@hdvHidde shares 5 quick tests you can run:
- test component keyboard accessibility
- test tokens: color contrast, spacing to have big enough target sizes, responsiveness to avoid scroll and hidden content issues
- names for controls (buttons, links, form elements)
- zoom and user preferences
- screen reader compability
zeroheight.com/blog/5-accessib

0

If you have a fediverse account, you can quote this note from your own instance. Search https://front-end.social/users/stephaniewalter/statuses/116052355193082824 on your instance and quote it. (Note that quoting is not supported in Mastodon.)