When editing a view with Javascript enabled and the JAWS screen-reader I cannot access anything under the h3 "Advanced". After Jaws reads this heading the next line is te checkbox toggle for Auto Preview.

When I disable Javascript and use Views UI to edit a view I can access the Contextual filters, Relationships, etc. which come after the Advanced heading.

CommentFileSizeAuthor
#3 1165104-advance-link-role.patch844 bytesdawehner

Comments

dawehner’s picture

dawehner
Primary language German
commented

This makes sense to certain extends.

Per default the "advanced settings" are hidden via display: none. Once you click on the h3 the settings appear again and you can edit them. Are there any kind of help to define for you that it's a toggle element?

If you want to have it open all the time you could run the drush commando "drush views-dev" which sets up some variables for you.

Hopefully this was helpful for you.

Everett Zufelt’s picture

Everett Zufelt commented

We can try setting role="link" on the h3 and making sure that it can be activated from the keyboard along with from the mouse.

See: http://www.w3.org/TR/wai-aria/roles#link

dawehner’s picture

dawehner
Primary language German
commented
StatusFileSize
new 1165104-advance-link-role.patch844 bytes

So does this patch helps you?

Do you have other suggestions where to place some special markup?

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Needs review

Wrong status

Everett Zufelt’s picture

Everett Zufelt commented

Thanks for the patch. I didn't apply it, but did look at it.

This patch will help with making sure that the link is recognized by AT, but won't make it function from the keyboard.

Actually one thing for the link is that it should be either:

<h3><a href="">Advanced</a></h3>

or

<h3><span role="link">Advanced</span></h3>

This is so that AT recognizes it as a link within a heading, with <h3 role="link">Advanced</h3> AT will not recognize the H3.

Everett Zufelt’s picture

Everett Zufelt commented

So, in general, since this is a control, it needs:

1. To receive focus
2. To visually show that it has received focus
3. To have a semantic role (either through using an anchor or role="link"
4. To be able to be activated via keyboard and pointing device

dawehner’s picture

dawehner
Primary language German
commented

Okay i tryed out the first solution you posted and manually testing it by using "Tab" worked fine.

So it receives focus. Commited to 7.x-3.x. Can you have a look whether this is fine for you?

merlinofchaos’s picture

merlinofchaos commented
Status: Needs review » Fixed

Automatically closed -- issue fixed for 2 weeks with no activity.