Re: Accessibility of Generated Docx

[Devin Prater <r.d.t.prater-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 3604 bytes --]

As a blind user, I find that mostly everything reads well for screen reader users, even headings, and definition lists—at least on Pages for Mac— are read well. If you make a table like this, I believe screen readers well read it a bit better:

| number | day |
|——|——|
| 1 | Sunday |
| 2 | Monday |
| 3 | Wednesday |

Note that I use Org-mode, so Markdown’s table creation make need to look different. The main thing is, give table columns a title, any way you can, and screen readers will try to read the title before the row’s content, like “Number, 1, row 2 column 1. Day, Sunday, Row 2 column 2.” This helps a lot with following tables, because screen readers always read content in a linear fashion.


Also note that I’m a simpleton, using Org to create well marked up documents, and exporting to HTML either using Markdown or Org’s own exporter.

The “compatibility mode” thing in Word is probably because it sees that Word didn’t make the file, so it does compatibility mode to, probably, make its interpretation of the file more relaxed, to accommodate any errors in Pandoc’s form of DOCX.

> On Sep 12, 2019, at 4:21 PM, Conrad Cunningham <hcc.olemiss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> I use pandoc to convert Pandoc-flavored Markdown documents to HTML (primarily), Word docx, PDF (via LaTeX), etc. I am currently using pandoc 2.7.3. Microsoft Word for Mac 16.16.14, and MacTeX 2019 on MacOS 10.14.6 (Mojave).
> 
> According to the tests I have run using the WebAIM WAVE tool, the accessibility of the generated HTML is reasonable. (I need to give some attention to places in the Markdown input where I use tables and alt text.)
> 
> For the generated docx, I am using Word for Mac's builtin accessibility checker. I found that the generated docx is in compatibility mode. Word for Mac's accessibility checker cannot process that kind of file. If I load the file into Word and then save as a normal docx, the checker will run.
> 
> Is there a less inconvenient way to get the generated output into the normal docx mode? I would like to get the final output by running a shell script on the Markdown input.
> 
> The issues I have found so far in my limited tests are warnings about insufficient color contrasts and sequences of blank characters. Some of these (e.g., colors in section headers and hyperlinks) seem to be fixable by using a custom reference document with modified styles. The warnings associated with code blocks, highlighting, etc., seem more problematic.
> 
> 
> -- 
> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/677959fb-29b8-4eaa-837f-c53e5ea5ab51%40googlegroups.com <https://groups.google.com/d/msgid/pandoc-discuss/677959fb-29b8-4eaa-837f-c53e5ea5ab51%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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/5BE53D02-D6CC-41F6-BF87-1D3F35162CC6%40gmail.com.

[-- Attachment #2: Type: text/html, Size: 5051 bytes --]