I'm not sure what they do on Windows but it would make sense for
links, when encountered, to be announced either way and all text
inside (flattened, not caring what tags are in it) presented as
the link accessible name.
Spans and <i> and other elements are very very common inside links
and buttons, very often the developer is deliberately trying to
offer accesible text that is not visible (by being moved offscreen
with CSS). The nested <i>s and spans seem to be common with
specifically icon fonts and Bootstrap toggle switches, where they
assume a screen reader, screen magnifyer or something like Dragon
will see the offscreen text.
Developers specifically trying to do the right thing are very
often using spans, however they may not be limited to just spans.
Though just a single node layer down seems to be the most common,
rather than terribly nested.
_mallory
On Tue, Jan 27, 2015 at 12:18:23PM -0200, Fernando Botelho wrote:
> Maybe we can have a toggle option under preferences that lets us
> decide if the performance hit is worth it.
>
> Best,
>
> Fernando
>
> On 01/27/2015 12:10 PM, Joanmarie Diggs wrote:
> >Hi Parham.
> >
> >If it's just spans, that's easy. If it's all elements immediately inside
> >a link, that's easy. If it's all elements that may be nested unknown
> >levels deep, then that's where things get uglier. So how literal should
> >I take your example below?
> >
> >--joanie
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca.
The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
Log bugs and feature requests at http://bugzilla.gnome.org
Find out how to help at http://live.gnome.org/Orca/HowCanIHelp