W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: Invisible elements for additional link text [SEC=UNOFFICIAL]

From: Harry Loots <harry.loots@ieee.org>
Date: Thu, 13 Sep 2012 12:45:14 +0200
Message-ID: <CA++-QFdbCEAckGrxbAQWJF4mv_kEYQYzLeDpgUCgpZWuTHUSCw@mail.gmail.com>
To: Joe Chidzik <joe.chidzik@abilitynet.org.uk>
Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Joe, as a matter of interest, in the scenario described above, where CSS is
used to make the additional text 'invisible' (and by 'invisible' I'm
assuming that it is simply positioned off-screen, as opposed to
'hidden'/'invisible') in the standard display, would Dragon ignore the
additional text when it displays the 'ambiguous' links, or include it as
part of it's rendering (I would think that JAWS, etc, would read out the
enitre link text including hidden portion).

Kind regards
Harry




On 13 September 2012 08:11, Joe Chidzik <joe.chidzik@abilitynet.org.uk>wrote:

> ** **
>
> What I’m now interested in/ concerned about, having never tested with it,
> is Dragon NaturallySpeakings functionality. If there is a page full of
> article summaries with simply ‘read more’ added how does the user get to
> any of those links? This really makes the guidelines incorrect if this is
> the case. ****
>
> ** **
>
> * *
>
> *[Joe Chidzik] When using Dragon to access links, (one method is) you
> simply read out all, or some, of the link text. If there is any ambiguity,
> Dragon will add a numerical identifier to all the ambiguous links on screen
> allowing you to further clarify by saying the identifier value. *
>
> * *
>
> *So in the case of a page with many read more links, saying “read more”
> to Dragon would overlay a list of numbers on the page, against each
> relevant link. You would then say “Choose 7” to select the 7th link
> displayed, for example. *
>
> * *
>
> *If you have Windows 7, you should have similar functionality with the
> built in Voice Recognition (I’ve not got a headset to test this with
> currently).*
>
> * *
>
> *Joe*****
>
Received on Thursday, 13 September 2012 10:45:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:30 UTC