u/paul_h the DOM is used by screenreaders, but purely in a programmatic sense,no positional information in the DOM as CSS is ignored for the most part.

I'll admit I'm not super up to date on how SVG works; not sure if you can attach alt="" to particular portions of the SVG. Your SVG's output for a screenreader is:

\> we can’t easily do capacity planning

we are not accurate with our story estimates

our average story size is large and difficult to estimate accurately

technologies we use do not lend themselves to small story sizes

other reasons

each iteration has a large variance for completed work vs others

(we’re a no iterations team)

our average story size is too close to our iteration length

we can’t easily do release commitments

technologies we use do not lend themselves to small story sizes

we can’t easily do capacity planning

because

because

and because

because

because

or because

and/or because

because

because

​

As you can see, we have all the text, but none of the individual relationships. They can be inferred, but not without room for error..

I'm not sure why you keep referring to PNG images? those don't work with screenreaders either unless you give them an alt attribute :)

OCR can read the text, but it will read it sporadically and possibly in an incorrect order because of the spacing. You could write a description, like a decision tree. (e.g. 1 splits into 2a and 2b. 2a splits into 3a and 3b. 2b splits into 3c and 3d. 3a splits into 4a and 4b. 3b stops. 3c stops. 3d splits into 4c and 4d.)