You are here:
(13 Apr 2016,
<noautolink> %TOC% ---+!! Online Access This area contains explorations into online access for the blind. ---++ Motivation A variety of assistive technologies are available for the blind readers, including [[%WP_RBD% ][refreshable braille displays]] and [[%WP_SS%][speech synthesis]] software. These technologies share a variety of limitations when used with document presentation systems (e.g., text editors, web browsers). I'd like to understand (and ideally, help to mitigate) some of these limitations. ---++ 2D Structures Many online documents, whether implicitly or explicitly, contain instances of two-dimensional (2D) structures (e.g., graphs, tables, trees). Computer source code, in particular, makes heavy use of indentation to show hierarchical program structure. It is also common practice to use white space to delineate informal tables, etc. Systems should help blind users to be aware of these structures, support exploration of them, etc. ---++ Styling Markup The vast majority of online documents (e.g., [[%WP_EPUB%][EPUB]], [[%WP_HTML%][HTML]], [[%WP_PDF%][PDF]]) contain styling markup. This is used to convey document structure, emphasize words, etc. Unfortunately, this markup is commonly removed when the documents are read aloud, displayed in braille, etc. This is a completely needless loss of semantic information. For example, the styling could be converted into printed markup. A blind reader would then be able to specify which kinds of styling s/he wishes to "hear about" at a given moment, e.g.: * high level (lists, sections, tables, ...) * low level (*bold*, _italic_, =teletype=, ...) ---+++ HTML and CSS Web pages and EPUB documents rely heavily on HTML and CSS markup. It seems quite feasible to capture this information (e.g., in a web browser or text editor extension) and reinterpret it in an explicit format. Here, as a starting point, are some test files: * [[Test_1][Test Cases (Base)]] * [[Test_1A][Test Cases (Variant A)]] - comprehensive * [[Test_1B][Test Cases (Variant B)]] - selected tags The [[SW_Notes][Software Notes]] page is a start on tabulating the results from different software stacks. The [[CSS_hax][CSS Hacks]] page contains some plausible (but untested!) [[%WP_CSS%][CSS]] code to transform HTML tags. ---++ SVG Content <blockquote> Scalable Vector Graphics (SVG) is an XML-based vector image format for two-dimensional graphics with support for interactivity and animation. The SVG specification is an open standard developed by the World Wide Web Consortium (W3C) since 1999. SVG images and their behaviors are defined in XML text files. This means that they can be searched, indexed, scripted, and compressed. As XML files, SVG images can be created and edited with any text editor, but are more often created with drawing software. -- [[%WP_SVG%][Scalable Vector Graphics]] (WP) </blockquote> It seems plausible that certain types of SVG content could be processed into blind-accessible versions. For example, plots could be summarized by tables, diagrams could be converted into nodes and arcs, etc. <!-- * Set WP_CSS = %WP%/CSS * Set WP_EPUB = %WP%/EPUB * Set WP_HTML = %WP%/HTML * Set WP_PDF = %WP%/Portable_Document_Format * Set WP_RBD = %WP%/Refreshable_braille_display * Set WP_SS = %WP%/Speech_synthesis * Set WP_SVG = %WP%/Scalable_Vector_Graphics --> %ZB%
ore topic actions
Topic revision: r36 - 13 Apr 2016,
Copyright © by the contributing authors. All material on this wiki is the property of the contributing authors.
, Plugin API version
Ideas, requests, problems regarding CFCL Wiki?
Send us email