“[…] it is difficult to scroll in the terminal with a screen reader. Users will have a hard time scrolling across the entire output and reading/copying all the text available to them. Being able to export this into a more accessible format like text or html would be a better user experience. This would allow them to search or navigate more quickly to the content they need.”
This might be a good structure:
<title>epubgrep output</title><sectionaria-labelledby="file_1"><table><captionid="file_1">path/to/file.epub</caption><tr><thid="file_path">File path (in EPUB file)</th><thid="chapter">Chapter</th><thid="page">Page number</th></tr><tr><tdheaders="file_path">OEBPS/file.xhtml</td><tdheaders="chapter">The beginning</td><tdheaders="page">14</td></tr></table></section>
It should respect the option to disable in-epub file paths, but probably ignore the option to disable file path output for the EPUB files?
I'm not so sure about using the full file path as title.
In [Accessibility of Command Line Interfaces](https://storage.googleapis.com/pub-tools-public-publication-data/pdf/8bc5640eb3c5cf22b9c5cc72647c6035d8d92fc7.pdf) it is recommended to provide HTML output for long outputs.
> “[…] it is difficult to scroll in the terminal with a screen reader. Users will have a hard time scrolling across the entire output and reading/copying all the text available to them. Being able to export this into a more accessible format like text or html would be a better user experience. This would allow them to search or navigate more quickly to the content they need.”
This might be a good structure:
``` html
<title>epubgrep output</title>
<section aria-labelledby="file_1">
<table>
<caption id="file_1">path/to/file.epub</caption>
<tr>
<th id="file_path">File path (in EPUB file)</th>
<th id="chapter">Chapter</th>
<th id="page">Page number</th>
</tr>
<tr>
<td headers="file_path">OEBPS/file.xhtml</td>
<td headers="chapter">The beginning</td>
<td headers="page">14</td>
</tr>
</table>
</section>
```
It should respect the option to disable in-epub file paths, but probably ignore the option to disable file path output for the EPUB files?
I'm not so sure about using the full file path as title.
In Accessibility of Command Line Interfaces it is recommended to provide HTML output for long outputs.
This might be a good structure:
It should respect the option to disable in-epub file paths, but probably ignore the option to disable file path output for the EPUB files?
I'm not so sure about using the full file path as title.