public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Thomas Byskov Dalgaard
	<tbdlist-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Table of contents in HTML-document can not be used with screenreaders when using markdown_phpextra
Date: Mon, 14 Oct 2019 08:29:26 -0700	[thread overview]
Message-ID: <m2wod7uyzt.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <BF8FCB7C-0EF4-4387-9108-5E61A914014C-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>


Try with

-f markdown_phpextra+auto_identifiers

Thomas Byskov Dalgaard <tbdlist-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org> writes:

> Hello!
>
> I have tested the --toc argument with Pandoc which produced a very nice looking table of contents in a html document. When I open this document in my browsers (Safari 13 or Google Chrome) I see the toc with VoiceOver which is the screenreader, but the links does not take me to the heading which it refers to from the toc. If change format to markdown it all works as expected...
> I have tested with Pandoc 2.7.3 on Mac OS Mojave.
>
> Best regards Thomas
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/BF8FCB7C-0EF4-4387-9108-5E61A914014C%40coolfortheblind.dk.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m2wod7uyzt.fsf%40johnmacfarlane.net.


      parent reply	other threads:[~2019-10-14 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14  7:46 Thomas Byskov Dalgaard
     [not found] ` <BF8FCB7C-0EF4-4387-9108-5E61A914014C-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
2019-10-14 15:29   ` John MacFarlane [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2wod7uyzt.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=tbdlist-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).