If you go through the specs they're quite overwhelming, the basics are ok and perhaps that is essential to include on any design, but once you step a bit outsid

If you go through the specs they're quite overwhelming, the basics are ok and perhaps that is essential to include on any design, but once you step a bit outside of hyper text it's really complex (or just want some degree of interactivity), as an example, hidden aria elements can't have focusable elements inside them, so if you have panels that hide/show content you have to change the aria elements as you go, hey js, not sure also how it plays out for a screen reader, does it just abruptly stop and starts on the new panel once it goes to a shown state? Then you need tools, specific ones to test it, then you need to understand all the nuances between html and specifics of aria tags, and how it all plays together, and then css, that has to play visually with what the accessibility requirements are to make it consistent, then you need JS for anything interactive to change those things. Then form invalidations, input patterns, and titles, and outside of the form errors (returned on validation by the backend), then dropdowns, buttons that link, or do actions. And then localisation. Probably there's more. No idea how to solve those to be honest, but as it's it definitively looks like a full time role with enough domain specific knowledge needed to do a decent job.