jfine2358 / stem-access

1 stars 0 forks source link

10 June 2021: Information architecture and accessible PDF #7

Open jfine2358 opened 3 years ago

jfine2358 commented 3 years ago

The video for this clip is here (YouTube).

Here's the transcript (in a raw form). The task is done when we've done enough to check, improve and share the content.

pdf uh the next thing i'm just going to throw out this one of these keywords along with self-voicing is information architecture um so information architecture is a bit like database structure and the o'reilly published a standard book on it i think they went through a number of additions and it got fatter and faster as time went by and i think it was that nobody knew that they what information architecture was or why they needed it and now people sort of take it for granted but information architecture is really important because that gives you the structure of your data and it constrains what you can and can't do with the data if you like the next thing is that there's um [Music] an organization which has annual conferences called write the docs and it's for people that write documentation and they have conferences and they do talk a bit about accessibility the only talk on latex or mathis i recall actually read the docs write the docs conference was by jim carson who's been here many times and that's how i got to know about him so there's the missing connection is technical documentation and the right to docs community uh i'm i'm sort of saying these things because i'm sort of saying well there's actually a lot of connections out there and somehow establishing those connections and getting a community of practice it's something really really important but it has to grow you can't sort of take a seed and it becomes a tree i know enough about biology to say that the first thing is that it's proud then the sure comes up out of the ground and then you get the first leaf and sometimes the initial growth is quite slow in a crowded environment jonathan i have a question oh please so i'm curious if you guys think that the way forward given that pdf has limitations is to create an accessible form of your document in something such as html and then either just know that the pdf is not going to be accessible but that there's always two options or that we as a community should not require users to make their pdf accessible but provide the capability to translate from an html to pdf where the accessibility is done behind the scenes automatically or if there's another option going forward this shirt is made out of fabric flat sheets of fabric and it's cut and it's sewn and it's stitched and burns put on and it becomes as such it becomes a shirt um the same sheet of fabric could be used to make something else what you can't do really is take your shirt pull it to pieces and make active it a pair of trousers or even a shirt of a different size and i'm sort of staying as the abstract format which is useless and the concrete formats which are useful but there are many concrete performance so html is a useful concrete format pdf is a useful concrete format xml and html are only useful for what you can create out of them you know people tend not to read them directly out of themselves uh to use the i know it's politically incorrect or to discriminate but in the chemical industry you talk about feedstocks you have resource you have oil-based chemicals that are useful for making things wrong and i think what arthur is saying is we we'd like authors to create documents that can be rendered in multiple ways and the person gets whatever is appropriate for what they're doing and in some situations such as law um the need to be archival is very important and the traditions and i say the traditions i mean the practice is also very important and so it's hard to change one of the reasons why legal secretaries all use word is because when you hire a legal secretary you want to hire something somebody who's a bit like a commodity you want to sort of make it easy to know that you you want to be able to interview somebody and find out that they got the right skills and if so you sort of get settled on a common denominator just like the qwerty conv keyboard becomes a common denominator and i think in many areas pdf are the is the common denominator and will be for a long time but if we can not be so fixated on one outcome on one group of readers and that's really what accessibility is about when you think about it from the sort of legal point of view of making all reasonable adaptions so taking a xml document and producing epub from it should be a reasonable adaption and if we can make xml pdf the preferred way of creating pdf then xml to epub becomes a reasonable adaption i've sort of answered that question on on on the fly i haven't thought it through