Bug 28578 - accessibility of pdf document using pdftohtml
Summary: accessibility of pdf document using pdftohtml
Status: RESOLVED INVALID
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-16 22:44 UTC by leena
Modified: 2010-06-18 11:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description leena 2010-06-16 22:44:23 UTC
For a person with perfect vision, no issues in reading pdfcontent in html format using pdftohtml. But to ensure that the complex html format is as much as similar to pdf document displayed using any document viewer and to make html format more accessible and usable by a blind person, we found that following issues need to be resolved. If a blind person reads file.html then following are some issues :

   1. Because file.html uses frameset/frame so orca is not able to shift control from 1 frame to another. it shifted after reading full content of one frame (with tab). Normal person can shift from frame to frame with the help of mouse, but with tab it is not possible to skip no. of tabs.
   2. If a blind person want to read/shift to another page, it opens in new tab, it will be confusing for her/him to handle no of tabs (1 for each page).
   3.Some more issues related with content format are:
     a)Header and footer of page are not accessible to screen reader
     b)Some character combinations are displayed as garbage like 'ft', 'tt' 
     c)Content in table format is displayed properly but not accessible to screen reader.

Solution : Using pdftohtml one single html connecting to all pages can be generated.
Comment 1 Albert Astals Cid 2010-06-18 11:26:22 UTC
We are discussing this on the mailing list already, no need to open a bug


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.