Tim Cross writes:
> I had a very similar idea wrt lint like functionality to alert user to
> possible 'stylistic' and/or other problems in exported content. Adding
> accessibility to that would then be the next step.
>
> I'm very much against enforcing standards. Experience has taught me that
>
Ihor Radchenko writes:
> Tim Cross writes:
>
>> From an org-mode perspective, the key things which need to be maintained
>> (and which perhaps we could make even easier or possibly have
>> 'defaults') is the ability to add the alt attribute to any non-text
>> element. For example, images,
Tim Cross writes:
> From an org-mode perspective, the key things which need to be maintained
> (and which perhaps we could make even easier or possibly have
> 'defaults') is the ability to add the alt attribute to any non-text
> element. For example, images, videos, sound files etc. All such
On 29/09/2022 00:08, Tim Cross wrote:
2. Technically, Org mode cannot be used in any organisation (specifically
government
funded) where ther are policies which require that documents be
accessible. For example, technically, this means we cannot use org mode
in Australian government
On Fri, Sep 30, 2022 at 07:05:40AM +1000, Tim Cross wrote:
>
> Dear all,
>
> I think I owe everyone an apology [...]
> For those interested and because it might help with understanding in
> this area, I thought I'd outline the actual cause of my frustration [...]
No, I for one are grateful for
Dear all,
I think I owe everyone an apology. I have allowed frustration from
another area of life colour my response here and as a result, my tone
and assessment was too negative.
While it is correct that we cannot use org mode to generate accessible
PDFs and that does mean in environments
Max Nikulin writes:
> On 29/09/2022 00:08, Tim Cross wrote:
>> 1. Org mode cannot be used to create accessible PDF documents as long as
>> it depends on the latex environment to generate those documents.
>
> Are there free tools that can generate accessible PDF documents? Perhaps,
> when it
Juan Manuel Macías writes:
> Hi, Tim
>
> Tim Cross writes:
>
>> An unfortunate situation really - especially given Emacs has one of the
>> most powerful and advanced accessibility options available via
>> emacspeak.
>>
>> I also won't hold my breath for a new latgex core. THe latex3 initiative
On 29/09/2022 11:12, Ihor Radchenko wrote:
Max Nikulin writes:
On 28/09/2022 10:07, Ihor Radchenko wrote:
Max Nikulin writes:
- What TeX engine do you use? E.g. for PdfLaTeX it may be necessary to
add \usepackage{cmap} immediately after \documentclass. Unicode engines
like LuaTeX likely do
One thing I vividly remember doing Navy mandatory trainings was several
instances when providers had mouse cursor and keyboard disabled so the
only way to proceed was to have a sighted person position and click the
physical mouse!
Jude "There are four boxes to be used in
defense of liberty:
Ihor Radchenko writes:
> Tim Cross writes:
>
>> Note that org also lacks any accessibility support for HTML generated
>> documents as well. However, this is less problematic as authors do have
>> some ability to add the necessary attributes that can improve
>> accessibility - an option not
On 29/09/2022 00:08, Tim Cross wrote:
1. Org mode cannot be used to create accessible PDF documents as long as
it depends on the latex environment to generate those documents.
Are there free tools that can generate accessible PDF documents?
Perhaps, when it is mandatory requirement, export
Max Nikulin writes:
> On 28/09/2022 10:07, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>
>>> - What TeX engine do you use? E.g. for PdfLaTeX it may be necessary to
>>> add \usepackage{cmap} immediately after \documentclass. Unicode engines
>>> like LuaTeX likely do not require such trick.
>>
Tim Cross writes:
> Note that org also lacks any accessibility support for HTML generated
> documents as well. However, this is less problematic as authors do have
> some ability to add the necessary attributes that can improve
> accessibility - an option not available with Latex.
Can we do
Hi, Tim
Tim Cross writes:
> An unfortunate situation really - especially given Emacs has one of the
> most powerful and advanced accessibility options available via
> emacspeak.
>
> I also won't hold my breath for a new latgex core. THe latex3 initiative
> seems to have failed or at least
Hi Tim,
> None of what yuo wrote is a surprise. Unfortunately, it does mean two
> things
>
> 1. Org mode cannot be used to create accessible PDF documents as long as
> it depends on the latex environment to generate those documents.
It means that Org mode cannot /currently/ be used…
I have hope
Timothy writes:
> Hi Tim,
>
>> It would probably be good to add the two above packages as part of the
>> ’default’ package preamble, but this would require considerable testing
>> as it isn’t known if there will be adverse effects when mixed with other
>> packages.
>
> Those packages are early
On 28/09/2022 10:07, Ihor Radchenko wrote:
Max Nikulin writes:
- What TeX engine do you use? E.g. for PdfLaTeX it may be necessary to
add \usepackage{cmap} immediately after \documentclass. Unicode engines
like LuaTeX likely do not require such trick.
I am wondering if having cmap should be
On 28/09/2022 13:48, Jude DaShiell wrote:
I don't make pdf files or make pdf files available for
anyone else.
Then what is the origin of "these" PDF files you mentioned in your first
post?
If you actually use pdftotext, I am unsure concerning effect of setting
language for you.
> Adobe
I've never done anything with latex. The closest I got to latex was using
groff for a little bit of time a long time ago. On this one I'm in way
over my head without scuba gear. Apparently html and adobe left latex in
the dust in so far as accessibility is concerned.
Jude "There are four
Jude DaShiell writes:
> It was one of the messages from this list that got me that reply. For
> now, when I get a pdf file I try extracting it with pdftotext and read the
> extracted text. I don't make pdf files or make pdf files available for
> anyone else. How adobe accessibility
Hi Tim,
> It would probably be good to add the two above packages as part of the
> ’default’ package preamble, but this would require considerable testing
> as it isn’t known if there will be adverse effects when mixed with other
> packages.
Those packages are early accessibility experiments,
It was one of the messages from this list that got me that reply. For
now, when I get a pdf file I try extracting it with pdftotext and read the
extracted text. I don't make pdf files or make pdf files available for
anyone else. How adobe accessibility recommendations for pdf files will
Hi Jude,
> I have done nothing with exporting to pdf from orgmode since several years
> ago I was told orgmode pdf’s were not accessible.
Do you know where this information came from? And what do you use now?
All the best,
Timothy
I checked that out and putting the example text into my .emacs file
generates a warning when emacs starts up I put the parens and everything
between the parens in the .emacs file and that caused the warning to be
thrown.
What may work and circumvent all of this would be to add:
#+LANGUAGE: en
Max Nikulin writes:
> - What TeX engine do you use? E.g. for PdfLaTeX it may be necessary to
> add \usepackage{cmap} immediately after \documentclass. Unicode engines
> like LuaTeX likely do not require such trick.
I am wondering if having cmap should be a good default in general.
Not just
On 27/09/2022 11:31, Jude DaShiell wrote:
Having examined 13.10.2, with the polyglossia package installed and
accessible to orgmode putting set-language into the right place would
default to English and other languages would need to specify their
language for a pdf export. On Linux I have
Jude DaShiell writes:
> Having examined 13.10.2, with the polyglossia package installed and
> accessible to orgmode putting set-language into the right place would
> default to English and other languages would need to specify their
> language for a pdf export.
The default can be changed in
Having examined 13.10.2, with the polyglossia package installed and
accessible to orgmode putting set-language into the right place would
default to English and other languages would need to specify their
language for a pdf export. On Linux I have espeak-ng running as default
and I run orca as
Jude DaShiell writes:
>> Have you tried Org-exported pdfs on screen-reader?
>> (I haven't, so I am curious to see if there are any improvements we can
>> make in this area).
>>
> Not yet, but that will be on my list. Is that latex template
> automatically used by orgmode when doing a pdf export
Jude
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
.
On Tue, 27 Sep 2022, Ihor Radchenko wrote:
> Jude DaShiell writes:
>
> > can these files include the language attribute like what happens
Jude DaShiell writes:
> can these files include the language attribute like what happens in
> microsoft word?
AFAIK, yes. See org-latex-hyperref-template
> If yes, and the contents are text that would go a long
> way to making those pdf files screen-reader accessible.
Have you tried
can these files include the language attribute like what happens in
microsoft word? If yes, and the contents are text that would go a long
way to making those pdf files screen-reader accessible.
Jude "There are four boxes to be used in
defense of liberty:
soap, ballot, jury, and ammo. Please
Hi Jude,
Jude DaShiell jdash...@panix.com writes:
Do those files by default conform to screen reader accessibility
standards or can such files be made to conform to screen reader
accessibility standards?
I don't actually know anything about this, but the quick answer is: Org
uses LaTeX to
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.
-- Twitter:
On 2015-04-04, at 19:15, Jude DaShiell jdash...@panix.com wrote:
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
36 matches
Mail list logo
