3 ms·
Feature request: documentation describing the accessibility impact this will have. Any time I'm considering a library like this my number one question is alway
by simonw 4y ago
Feature request: documentation describing the accessibility impact this will have.
Any time I'm considering a library like this my number one question is always the impact it will have on accessibility tech, most specifically screenreaders.
I would love it if libraries could get into the habit of describing this impact in their documentation - and ideally if they could compete on providing the best possible accessibility as one of their promoted features.
- josephernest 4y agoGood question... I haven't thought about it deeply, but I would say that using this lib itself won't have impact on accessibility: if the HTML fragments are carefully crafted to take accessibility into account, then after HTML fragments swapping the DOM will keep this aspect. I would say the construction of the HTML fragments (done by the user of this lib) is the most impactful part. Since the URL can change after a HTML-fragment-swapping with this lib, I can imagine that screenreaders will detect the URL change and take the new layout into consideration, is that right?
- simonw 4y agoI'm not 100% sure myself. My understanding is that if you swap out a piece of the page you need to sleet screenreader users to the change, but I don't know the best way to do that - I presume it involves ARIA attributes.