From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: Timothy <orgmode@tec.tecosaur.net>,
Jude DaShiell <jdashiel@panix.com>,
emacs-orgmode@gnu.org
Subject: [HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files))
Date: Sun, 02 Oct 2022 17:42:42 +0800 [thread overview]
Message-ID: <87pmfazhm5.fsf@localhost> (raw)
In-Reply-To: <86pmfeo4os.fsf@gmail.com>
Tim Cross <theophilusx@gmail.com> 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 content
> should always have some text describing the 'element'. However, it is
> also important to be able to not have an alt tag in some situations (for
> example, when using images as 'spacers' for formatting etc, we don't
> want an alt tag. Things to be aware of are things like using single
> characters or symbols (e.g. < and > for previous/next) or using unicode
> and other symbols whose meaning/purpose may seem very obvious when
> viewed, but is less so when 'spoken'.
>
> From an authoring perspective, it probably would be good if org mode was
> able to alert the user to content which lacks an alt attribute but which
> probably should have one e.g. an image with no caption, a link to a
> video/audio file etc.
This sounds like a good idea.
Org currently attempts to be slightly helpful by indicating, for
example, LaTeX compilation warnings. However, it is just done by writing
a simple message in the echo area.
What would be more useful is the kind of buffer displayed by org-lint,
but instead used during export:
- If there are any export issues (LaTeX errors/warnings) they can appear
in the buffer
- If there are any stylistic issues (like lack of alt attributes during
html export), they can also appear
Ideally, we should be able to jump directly to the line containing
error.
org-lint code could be used as a base, but otherwise we need to
implement something generic way to check style/export warnings on
per-backend basis.
This is probably something we need to do before we dive into the
accessibility specifics. AFAIU from the Tim's reply, many of the
accessibility guidelines may need to be decided by the document author.
Tim, let me know if I am wrong and some of the accessible tagging must
be done unconditionally.
I am marking this as a help request.
Let me know what you think.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-10-02 9:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 1:48 org exported pdf files Jude DaShiell
2022-09-27 2:48 ` Ihor Radchenko
2022-09-27 3:15 ` Jude DaShiell
2022-09-27 3:24 ` Ihor Radchenko
2022-09-27 4:31 ` Jude DaShiell
2022-09-27 4:58 ` Ihor Radchenko
2022-09-28 4:36 ` Jude DaShiell
2022-09-28 4:53 ` Timothy
2022-09-28 6:48 ` Jude DaShiell
2022-09-28 8:47 ` Tim Cross
2022-09-28 9:19 ` Timothy
2022-09-28 17:08 ` Tim Cross
2022-09-28 17:39 ` Timothy
2022-09-28 18:23 ` Juan Manuel Macías
2022-09-29 20:58 ` Tim Cross
2022-09-29 4:09 ` Org HTML export accessibility (was: org exported pdf files) Ihor Radchenko
2022-09-29 8:22 ` Tim Cross
2022-09-29 11:43 ` Jude DaShiell
2022-09-29 21:05 ` Apology [was: Re: Org HTML export accessibility (was: org exported pdf files)) Tim Cross
2022-09-30 5:34 ` tomas
2022-10-02 10:59 ` Apology [ Fraga, Eric
2022-10-02 9:42 ` Ihor Radchenko [this message]
2022-10-02 20:52 ` [HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files)) Tim Cross
2022-10-03 3:25 ` Ihor Radchenko
2022-09-29 7:07 ` org exported pdf files Max Nikulin
2022-09-29 21:00 ` Tim Cross
2022-10-01 10:55 ` Max Nikulin
2022-09-28 13:02 ` Jude DaShiell
2022-09-28 16:12 ` Max Nikulin
2022-09-27 11:08 ` Max Nikulin
2022-09-28 3:07 ` Ihor Radchenko
2022-09-28 15:58 ` Max Nikulin
2022-09-29 4:12 ` Add \usepackage{cmap} as default LaTeX class in ox-latex (was: org exported pdf files) Ihor Radchenko
2022-09-29 15:34 ` Max Nikulin
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmfazhm5.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jdashiel@panix.com \
--cc=orgmode@tec.tecosaur.net \
--cc=theophilusx@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).