Re: [orca-list] Strange behavior when using the role attribute in websites

[Joanmarie Diggs <jdiggs igalia com>]

When a page loads, Orca looks to see if the author (or browser) has
placed focus in a focus-mode (i.e. web application gui) object or form
input. A toolbar is a web application gui object. It is assumed that if
the author has placed you automatically inside of a toolbar, then the
associated web application will be providing the navigation. As a
result, Orca puts you in focus mode.

A question back at you: Why are you putting users inside a toolbar if
you want screen readers to treat it like textual content?

--joanie


On 5/4/19 7:41 AM, Andy Borka via orca-list wrote:
> Hi,
>
>
> Orca master, Ubuntu 19.04.
>
>
> When I design websites, I often use the role attribute with html
> elements. However, Orca presents some interesting behavior when
> interacting with these types of html elements. When Orca is presented
> with one of these controls, it goes into focus mode and doesn't interact
> with the control very well. For example, a div with role="toolbar" puts
> Orca into focus mode on the toolbar, but the only way to interact with
> the controls inside the toolbar is to press TAB rather than using the
> left/right arrows. In another instance, using role="tree" and
> role="treeitem" puts Orca into focus mode on the tree, but I can't
> interact with the tree nodes. Orca will only go into focus mode when an
> element with the role attribute is the first thing on the page. Any
> ideas what might be going on?
>
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide:
> https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org