Hi!  
My team is trying out Blazor on a prototyping project, and we're loving it so far!  We're hoping to continue using this framework, it seems very robust, and it's been incredibly easy for our .NET developers to pick up front-end work.  

We've been trying out a few component libraries like Sync Fusion and Mud Blazor, and each seem to have some shortcomings in meeting WGAC 2.1 AA compliance specifications. Some components are not keyboard accessible, some are missing accurate ARIA labels, and it seems that manual tab-index overrides are common-place. From what we've explored so far, it feels like most components meet basic criteria, but there are challenges with some specific components.  Because our products are in the K-12 EdTech space, A11Y is one of our highest priorities. 

I was wondering if anyone here had any advice on how they've overcome A11Y idiosyncrasies in component libraries, or if there are component libraries that focus on accessibility?  

One of the approaches that we thought might be nice would be to lean into an open-source solution so we could submit some PR for A11Y updates, but I wanted to see if there are other solutions that work well for others. Additionally, if anyone's got a sense of how accepting the maintainers are to PRs from a group of Blazor newbs, we're eager to get involved, but still focused on framework fundamentals.  Overall, the learning curve for Blazor has been pretty shallow for our team, and we'd rather not have to build out all of our UI components from scratch if we don't have to.  

Thanks in advance for any advice or insight!
- Alan