#59 scrlttr2 not compatible with tagged PDF

[Gerhard Mauser]

I try to create an accessible tagged PDF letter.

The letter class scrlttr2 is not (yet) compatible with the new tagged PDF options. The following minimal example throws errors:

\DocumentMetadata{testphase = {phase-III}}
\documentclass{scrlttr2}

\begin{document}
\begin{letter}{Mrs Mabel Canary\\24 The Street\\Some Village}
  \opening{Dear Mrs~Canary}

  This is an imaginary letter.

  This is the second paragraph of the letter.

  \closing{Yours sincerely}

\end{letter}
\end{document}

The error message is "! Package tagpdf Error: The number of automatic begin (27) and end (23)
(tagpdf) text-unit para hooks differ!"

However if I use letter class instead of scrlttr2 there is no error thus there is something in komascript that causes it.

[Markus Kohm]

Do you know, that phase-III is currently work in progress?

Do you know, that letter is much simpler than scrlttr2?

Do you know, that letter is from the same team, that also works on phase-III?

Do you know, that The LaTeX Team is really a team?

If not, you know now.

I'm currently alone in development. Yes, tagging is important, but keeping KOMA-Script compatible with all the other changes in LaTeX is more important. So, compatibility with phase-III and even with phase-II is not the highest priority and you should not expect it in KOMA-Script 3.42 and even not in another 3.xx version. If you really need it, I recommend to use book, report, article and letter.

If there will be a developer or even more than one, who will concentrate to add tagging support to KOMA-Script, the priorities could change.

[Gerhard Mauser]

@Markus: I already knew all of those points and I did not mean to insult you. Nor did I intend to say that letter is better than scrlttr2. In fact it's the disclaimer in this bugtracker which requests to check wether the issue does not occur with standard classes. I just think this should be listed as a todo item.
Unfortunately my skills do not enable me to solve this myself.

[Markus Kohm]

Maybe you misunderstood: If you need automatic tagging, it is me, who says, the standard classes are better.

But also know, that with each package you additionally load the reliability of automatic tagging fades. Sometimes broken tagging can be corrected very easy after someone found the cause. For example, month ago I've changed some box commands after Ulrike requested to do so to fix tagging. But before every change you first have to find the cause and an idea to correct the problem and also have to think about side effects.

Beside manpower, these all are reasons I've decides to change the milestone.