Tracking Issue: Accessibility Checks

[bdougie]

We can start with a lighthouse score, but open to suggestions to other tools.

@0-vortex @bdougie @pixelsbyeryc @chadstewart Let's drop our view on the current Select component I created before replacing the Supabase select with it. I'm still not convinced my current implementation is right praypray

I think this component will do for now. I don't see any real glaring issues with it outside of potential accessibility issues. I'd say we can move forward with this once all the necessary changes are completed and we can take a deeper look at all the components after Hacktoberfest.

Originally posted by @chadstewart in #346 (comment)

[eryc-cc]

Something Ted mentioned:

For humans or robots?

For robots it's missing microformats: https://developers.google.com/search/docs/advanced/structured-data/intro-structured-data

In this case I guess it would be: https://schema.org/Person

That could give you some creative ideas about what other props we could use in the previous comment, however data is a bit scarce at the moment!

#354 (comment)

[0-vortex]

@pixelsbyeryc I figured I'd just do all the schemas for SEO purposes if nobody gets on it sooner, I'm pretty fast at adding robot data, the only question is whether the data is whole enough when that moment occurs 🍕

[eryc-cc]

@chadstewart @0-vortex

I see you added this to your list, Chad... I'll assign it to you, then! 🙏