Not sure if I'm in favor of this...

I just updated the Kibana guide to do a few things:

• right at the top it points to EUI's guide
• then it talks about running the a11y tests which isn't covered in the EUI guide because it's Kibana specific (you could say this is redundant because I also talk about the a11y tests wherever we talk about functional tests but it's usually good to have docs wherever people will go looking for them imo)
• then it talks about ID generation (again, not sure if this is worthwhile for people or not but, again, it is Kibana specific)

Good points. I am still worried the more developers need to read, the less likely any of it will be read :D

What would you think about moving the a11y testing guide into the development guide in the repository (beside the other testing paragraphs), and the HTML generation into the top level STYLEGUIDE.md file, since it shouldn't clutter it to much, and then instead link into the EUI styleguide? Or do you feel we'd still be losing to much in that case?

Sure, sounds like a good plan. I'm happy to consolidate our files.

If you don't want to touch so much, I'm happy to take this as a to-do myself.