Work on an simplified accesible version?

[Darkade]

Hi! I recently published an adventure using this template. Along with the exported PDF i used the article class to export my content as a friendlier version for screen readers. But it also implied dropping the DndReadAloud DndSidebar DndComment \DndDropCapLine and of course DndMonster helpers.

I'm considering working on a fork that would render these in simplified ways for screen readers so that all you need to do is change class from dndbook to dndsimplified or even dnddyslexic so, is anyone working on such a thing? would anyone be interested?

The objective of course, is making it easier for we as writers to publish in accessible ways without the trouble of modifying .tex files with each export

Thanks!

[BrianCriswell]

Well done, and I am glad you added it to the list of products on our wiki!

I don't know what would be involved in making those functions more accessible to screen readers, but I am interested in hearing about it. Unfortunately I do not have time to help with it at this time. Once you have a firm grasp on what would be involved in this simpler version, we could look at what it would take to merge it into the main class.

[Darkade]

Got it. I'll begin checking this as soon as I am able then!

I did had an unrelated question. Is there a preferred way to include the project on credits?

[BrianCriswell]

Hm, I had not given that a lot of thought. You might want to take a look at a colophon. O'Reilly reference books have them, and they talk about what tools were used to make the book, what the animal is on the cover, etc.
https://en.wikipedia.org/wiki/Colophon_(publishing)

I don't even do it for my products, but I was thinking about adding it for the hardcover omnibus.

[OnePageMage]

hey there! I'm also interested in figuring out accessibility. I'm writing one-shot adventures in LaTeX and want them to be used by as many people as possible, including visually impaired GMs. Two notes on this subject:

1. I tried creating a High Contrast "night mode" version of the package, but I ran into a snag. After copying the folder and re-naming the files, pretty much everything works except the font didn't stick. Any ideas? I can create a separate issue for that if that's best.

2. Accessibility in LaTeX is a fickle thing. As far as I found, there isn't a solid solution to adding tags for PDF documents for screen readers to use. Many people end up tagging PDFs in a premium version of Adobe after exporting. The best I have found so far is the tagpdf package (https://github.com/u-fischer/tagpdf) but isn't perfect, and adding tags and structure flags in the middle of things like a DND style table sometimes throws errors.

[Darkade]

HI! I'm still interested in this. I'm soon to publish my next adventure, I just haven't had time to get around to it (and my tex knowledge itself is limited)

I expect to at least, make some proof of concept during the christmas break.