Re: [webcomponents] clearer, more accessible code (#336)

Omnigraffle could do a lot better at supporting accessibility, which I guess we should report. But the problem isn't just Omnigraffle.

I agree that we don't want to manually edit images every time you export them - that's a crazy waste of time. I'm not sure how easily we can make an automatically reproducible repair though. Some of the fixes could be automated, but some of the stuff is likely to be difficult - especially the things I haven't fixed yet.

And I don't have omnigraffle so I am not sure how easy it is to change what it is doing in a way that is scalable for you to do in reality...

...hence the suggestion that I manually work up "shadow" versions of the images (in a parallel directory?), and rely on you to tell me which seem stable and which seem likely to change. I could always watch github to see which images actually *do* change, right?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/pull/336#issuecomment-146134721