Hi, Laura, I'm trying to understand the accessibility issues that DERBY-1842 wants to address. After a quick search I found the "Section 508" web site for the U.S. govt, which looks like it has great links to all sorts of resources:
http://www.section508.gov/ would this be a good starting point for understanding the issues? Or do you have any favorite web sites you could point us to? At any rate, I think the main objective of DERBY-1842 from its description is to enable screen readers, right? Are the line break / line feed issues and window sizing you mentioned especially important to screen readers? Or are you trying to also enhance image information for those of us who are not visually impaired -- sort of hit two birds with one stone? I'm kind of confused about the goal here, but am pretty clueless about accessibility issues so welcome any info (or pointers to info). thanks, -jean Laura Stewart (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/DERBY-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466894 > ] > > Laura Stewart commented on DERBY-1842: > -------------------------------------- > > > The tool that I use does not show the line feed characters. However > when I open the file in Notepad, the places where the line breaks > coinsides with the line feed characters. While I can manually remove > the line breaks, I would prefer to find a way in dita tagging to force > either the size of the window to be larger or some other solution so > that we don't have to worry about the authoring tool adding the line > feeds. > > Incidently, when I use IE to view the text, the text breaks more often > than the where the line feed characters are. For example, in the file > ctundepth32379.html, the text appears in IE as: > > This figure shows one connection > with multiple execution of the same PreparedStatement, > which uses the same > statement execution plan > > So for text that appears on one line in Notepad is truncated if it is > too long for the default size of the text box in IE. This is a > separate problem from the line feed character problem. >
