Re: [webcomponents] Improve the accessibility of SVG files which are used in the spec (#341)

> Readers don't have to try to understand the tree structure, every parent-child relationship,
> in the image here. That's not essential in understanding what the composed tree is.

True. I agree that a more /descriptive/ description, instead of trying to be precise about the particular details of this image, would be more useful for most uses of the spec.

> Also it's hard to maintain.

Well, not compared to an accessible image. It took me minutes to write the description. It took me days to get the image more or less workable, and if I get the pattern down right I am afraid it will still take hours. And fixing tools like OminGraffle so they don't make it so had to begin with is likely to take a fair bit of work too…

Describing images for use is something of an art, and I'd welcome others doing it with a bit more style than I put into this particular example. It is also important to do for people who are trying to understand the spec - which includes our own colleagues, not just some theoretical "goodness for the universe".

Anyway, when I get to anther image (I'm working on a fair few other things at the same time) I'll have a go at improving how I do the description, and use that to improve the description of this image...

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/341#issuecomment-148850564