The vanilla enumerate environment is compatible with tagging mechanisms, which means that if we add
%!texprogram=lualatex
\DocumentMetadata{
lang=en,
pdfstandard=ua-2,
pdfstandard=a-4f,
tagging=on,
tagging-setup={math/setup=mathml-SE}
}
at the very beginning of the .tex source file, the compilation process passes successfully and the output .pdf file is well-tagged.
However, if we import packages like enumitem to customize layout of enumerate environment, we will not be able to compile the code. For example,
\begin{enumerate}[label=\arabic*.,ref=\arabic*,align=left,leftmargin=\labelwidth,rightmargin=0pt,labelindent=0pt,listparindent=0pt,itemindent=0pt]
...
\end{enumerate}
causes
Package block Error: Some keys specified on the enumerate environment are(block) unknown.
What's more, \usepackage[inline]{enumitem} results in similar problems with enumerate* environment and even possibly freeze the compilation process.
In addition, while other packages, such as tasks, changing typesetting style of lists work fine during compiling, they break tags in produced .pdf files.
It is worth investigating the reason why layout modifications are not compatible with tagging mechanisms.
The vanilla
enumerateenvironment is compatible with tagging mechanisms, which means that if we addat the very beginning of the
.texsource file, the compilation process passes successfully and the output.pdffile is well-tagged.However, if we import packages like
enumitemto customize layout ofenumerateenvironment, we will not be able to compile the code. For example,causes
What's more,
\usepackage[inline]{enumitem}results in similar problems withenumerate*environment and even possibly freeze the compilation process.In addition, while other packages, such as
tasks, changing typesetting style of lists work fine during compiling, they break tags in produced.pdffiles.It is worth investigating the reason why layout modifications are not compatible with tagging mechanisms.