We've had a vf:uri property in the ttl file for some time, which can appear in any domain. But we've never explicitly included it anywhere else in the doc, and it mostly sits forgotten.
Review and decide if this is useful or not, and remove or include everywhere.
Lynn Foster (caf55aef) at 21 Mar 18:38
tweaks to old VF pie story
add presentations, other cleanup
Lynn Foster (922c875e) at 27 Feb 18:28
add presentations, other cleanup
Lynn Foster (57913b12) at 16 Feb 15:33
Update v0.10
Lynn Foster (57913b12) at 16 Feb 15:30
Update v0.10
Lynn Foster (f4370c40) at 16 Feb 15:06
Lynn Foster (f4370c40) at 16 Feb 15:05
move all_vf.html, build
Lynn Foster (b0865aff) at 16 Feb 14:43
PYLODE one version back, but very close fix on diagram text page build
PYLODE one version back, but very close fix on diagram text page build
Lynn Foster (b0865aff) at 16 Feb 14:41
tweaks, build
Lynn Foster (520f3439) at 14 Feb 16:15
We got some feedback on the Valueflows Pie Story (a pdf generated from LibreOffice) that there were a lot of diagrams, but no way for a low vision person to understand them. There are a lot of diagrams in the main site too.
From the chat:
An immediate improvement is to provide an alternative representation of each diagram, as best as possible.
On useful links, I think this article is a very good introduction: https://www.incobs.de/articles/items/diagram-a11y.html Somewhat with a more specific application, by the same author, is http://www.oturn.net/top/index.html. And a website with very good resources on a broader approach would be https://inclusivedesign.ca/.
Also: https://fossheim.io/writing/posts/accessible-dataviz-d3-intro/
Background: https://support.microsoft.com/en-us/office/create-accessible-pdfs-064625e0-56ea-4e16-ad71-3aa33bb4b7ed Possibly LibreOffice has something comparable Positive: https://wiki.documentfoundation.org/Accessibility/Creating_Accessible_LibreOffice_Files
Usually written into the metadata.
A request from the Welcome chat:
If you walk over the documentation anyway, please try to avoid „here“ as a link text. Screenreaders and other assistive technology often have a mode that allows them to jump from one link to another. „here“ isn't very expressive on the target to them.
Review and correct existing examples for recent changes in relationship direction and other things. Add new examples as needed for further explanation. Some more developed use case based examples would be helpful, possibly in a different format, not sure.
Also, after this and #719 , re-run yaml validation on all examples.