Loading ...
Sorry, an error occurred while loading the content.

[Fwd: Most wanted feature in Moz]

Expand Messages
  • Bas Cancrinus
    Please review the following post. ... Subject: Most wanted feature in Moz Date: Sat, 29 Jun 2002 18:57:12 +0200 From: Bas Cancrinus
    Message 1 of 2 , Jun 29, 2002
    • 0 Attachment
      Please review the following post.

      -------- Original Message --------
      Subject: Most wanted feature in Moz
      Date: Sat, 29 Jun 2002 18:57:12 +0200
      From: Bas Cancrinus <justsayyes@...>
      Newsgroups: netscape.public.mozilla.accessibility

      Hi,

      Unlike earlier posts I'd like to present 1 feature for Mozilla, which
      could make it a "killer app" for the blind and visual impaired. From my
      own experiences and those of many others I conclude the following:
      screen readers, either standalone or embedded into magnifiers (such as
      DocReader in ZoomText Xtra) fail to process content from web browsers
      correctly.

      In general the above is caused by the following elements within this
      content: table structures, images and frames. Therefore I'd like to
      propose alternative page rendering that disables these elements. The
      following scenario describes how a page that consists of all these
      elements should be processed.

      1. USR: Points SYS to URL.
      2. SYS: Detects frameset.
      3. SYS: Adds tabbed window for each frame.
      4. SYS: [WHILE] Rendering each frame into its tabbed window...
      4.1 PARSER: [IF] img tag detected...
      4.1.1 RENDERER: [THEN] display "Image: " + (alt value [OR] URL)
      4.2 PARSER: [IF] table tag detected...
      4.2.2 RENDERER: Display each tr tag as hr tag; display each th/td tag as
      p&b/p tag respectively.

      Please let me know if the concepts of this scenario are clear.

      Regards,
      Bas


      --
      Bas Cancrinus -> bas@...
      Software Architect
      Cipherware Ltd. -> http://www.cipherware.com
    • Michael Wigle
      Although large print software tends to have a rough time with speech feedback of web pages, screen readers such as Jaws and Window-Eyes already do what is
      Message 2 of 2 , Jun 29, 2002
      • 0 Attachment
        Although large print software tends to have a rough time with speech
        feedback of web pages, screen readers such as Jaws and Window-Eyes already
        do what is mentioned in this e-mail. Using Jaws I can quickly and easily
        switch between frames and when I reach a picture the descriptive tag (if
        any) is already read now. The problem with accessibility of web pages is
        more due to the person writing the web page taking shortcuts. Many web pages
        use are simply missing the textual information or are created using
        technology that uses only graphics to display information on the screen even
        though to the eye it may look like regular text. Convincing web page
        developers to not take shortcuts would be, in my opinion, a greater step
        toward accessible web sites than anything that can be done to a web browser.

        Michael Wigle
        Computer Access Specialist
        Cincinnati Association for the Blind


        ----Original Message Follows----
        From: Bas Cancrinus <bas@...>
        Reply-To: magnifiers@yahoogroups.com
        To: Magnifiers discussion list <magnifiers@yahoogroups.com>
        Subject: [magnifiers] [Fwd: Most wanted feature in Moz]
        Date: Sat, 29 Jun 2002 19:05:19 +0200
        MIME-Version: 1.0
        Received: from [66.218.66.72] by hotmail.com (3.2) with ESMTP id
        MHotMailBEE7355400AD4004325E42DA4248311F201; Sat, 29 Jun 2002 10:18:10 -0700
        Received: from [66.218.67.195] by n17.grp.scd.yahoo.com with NNFMP; 29 Jun
        2002 17:03:09 -0000
        Received: (EGP: mail-8_0_7_4); 29 Jun 2002 17:01:49 -0000
        Received: (qmail 78962 invoked from network); 29 Jun 2002 17:01:49 -0000
        Received: from unknown (66.218.66.218) by m2.grp.scd.yahoo.com with QMQP;
        29 Jun 2002 17:01:49 -0000
        Received: from unknown (HELO smtp08.wxs.nl) (195.121.6.40) by
        mta3.grp.scd.yahoo.com with SMTP; 29 Jun 2002 17:01:49 -0000
        Received: from cipherware.com ([195.121.70.108]) by smtp08.wxs.nl
        (Netscape Messaging Server 4.15) with ESMTP id GYH8MY01.47Y for
        <magnifiers@yahoogroups.com>; Sat, 29 Jun 2002 19:01:46 +0200
        From sentto-1523134-1296-1025370110-michaelwigle Sat, 29 Jun 2002 10:18:16
        -0700
        X-eGroups-Return:
        sentto-1523134-1296-1025370110-michaelwigle=hotmail.com@...
        X-Sender: bas@...
        X-Apparently-To: magnifiers@yahoogroups.com
        Message-ID: <3D1DE8CF.2070202@...>
        Organization: Cipherware Ltd.
        User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0)
        Gecko/20020530
        X-Accept-Language: nl, en-gb
        X-Yahoo-Profile: bascancr
        Mailing-List: list magnifiers@yahoogroups.com; contact
        magnifiers-owner@yahoogroups.com
        Delivered-To: mailing list magnifiers@yahoogroups.com
        Precedence: bulk
        List-Unsubscribe: <mailto:magnifiers-unsubscribe@yahoogroups.com>

        Please review the following post.

        -------- Original Message --------
        Subject: Most wanted feature in Moz
        Date: Sat, 29 Jun 2002 18:57:12 +0200
        From: Bas Cancrinus <justsayyes@...>
        Newsgroups: netscape.public.mozilla.accessibility

        Hi,

        Unlike earlier posts I'd like to present 1 feature for Mozilla, which
        could make it a "killer app" for the blind and visual impaired. From my
        own experiences and those of many others I conclude the following:
        screen readers, either standalone or embedded into magnifiers (such as
        DocReader in ZoomText Xtra) fail to process content from web browsers
        correctly.

        In general the above is caused by the following elements within this
        content: table structures, images and frames. Therefore I'd like to
        propose alternative page rendering that disables these elements. The
        following scenario describes how a page that consists of all these
        elements should be processed.

        1. USR: Points SYS to URL.
        2. SYS: Detects frameset.
        3. SYS: Adds tabbed window for each frame.
        4. SYS: [WHILE] Rendering each frame into its tabbed window...
        4.1 PARSER: [IF] img tag detected...
        4.1.1 RENDERER: [THEN] display "Image: " + (alt value [OR] URL)
        4.2 PARSER: [IF] table tag detected...
        4.2.2 RENDERER: Display each tr tag as hr tag; display each th/td tag as
        p&b/p tag respectively.

        Please let me know if the concepts of this scenario are clear.

        Regards,
        Bas


        --
        Bas Cancrinus -> bas@...
        Software Architect
        Cipherware Ltd. -> http://www.cipherware.com





        _________________________________________________________________
        Send and receive Hotmail on your mobile device: http://mobile.msn.com
      Your message has been successfully submitted and would be delivered to recipients shortly.