On 2015-04-06, at 13:40, Rasmus <ras...@gmx.us> wrote: > Jude DaShiell <jdash...@panix.com> writes: > >> http://www.adobe.com/accessibility/products.html >> is a good place to start. > > It's a list of a bunch of software packages of which most are not (i) free > in any meaning of the word; and (ii) supported on GNU/Linux.
So what? IIUC, the OP wants to have something similar using Emacs and (maybe) free (in a usual sense, or in FSF sense) software. Isn't it a valid request? > What is your point? Maybe it's an answer to my question below? ,---- | > Do those files by default conform to screen reader accessibility standards | > or can such files be made to conform to screen reader accessibility | > standards? Since adobe was responsible for creating pdf files Adobe has | > screen reader accessibility standards on its website. | | Could you point out these standards (direct links)? `---- (No idea why the OP started a new thread, though.) In my browser, on the right there are some links to general accessibility info (or so it seems, I didn't follow them yet). >> When a document gets written in Microsoft Word, its language is made >> part of that document. If that document is later converted to a pdf >> file that language information is taken in by the conversion process >> then becomes the first component that starts to make screen reader >> accessibility of a pdf file possible. > > AFAIK, the language is set as part of the metadata in pdfs in 8.3 based > on #+LANGUAGE. Can you test if that works for you? If not, what will > needed to be changed to make it work? Quick test using #+LANGUAGE: polish or #+LANGUAGE: pl showed it didn't work. (I didn't check the pdf file, though, only grepped the LaTeX source.) > —Rasmus Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University