IE11; Dragon Speech recognition
a. The “Click link” command does not work on all pages. Inconsistent behavior.
b. On pages that do work, Dragon indicates there are too many links to generate voice commands and so users are unable to proceed.
IE11; Dragon Speech recognition
a. The “Click link” command does not work on all pages. Inconsistent behavior.
b. On pages that do work, Dragon indicates there are too many links to generate voice commands and so users are unable to proceed.
Comments
Comment #2
andrewmacpherson commented@travis.d.peltier - thanks for filing this issue.
Can you provide more detail about which pages fall into (A) or (B) ?
Ouch! This could be a tough thing to address.
Comment #3
mgiffordJust echoing Andrew's comment & extending it a bit. We need more DNS testing. Thanks for these observations. Are there any best practices that you can suggest in the DNS community?
Comment #4
travis.d.peltier commentedWill retest the pages to try and find consistencies and more details. I will also try to get some user experiences that can be used to help.
Comment #5
mgiffordThanks Travis!
Comment #6
psbooks_32 commentedHello,
I'm a Dragon NaturallySpeaking user to use version 14. I've had this issue on other websites as well one of the things that I found that can work is that if you simplify the number of links on a page it allows Dragon to make up its mind. So when constructing a page it's best to not have too many links or for that matter links on top of each other. I would say roughly if there are more than 60 links on any given screen, Dragon can get a little bit confused.
Hopefully this helps.
Comment #7
mgifford@psbooks_32 is there an open bug for this in the Dragon NaturallySpeaking community? I know that Freedom Scientific recently opened up their issue queue for greater transparency. Hopefully this is the case for DNS.
Comment #8
andrewmacpherson commentedSo what we need to ask is: how many links is too many for DragonNS? @psbooks_32 suggests around 60.
What might help here is to know if there are particular pages this happens on...
Take the admin/content listing for instance. Once a site has lots of content, you can have 50 rows in the table. Each row has 3 links: node title, node author, and edit operation. Add the sortable table headers, pagination, breadcrumb, primary tabs, and toolbar - you're in the region of 200 links. (I'm assuming that links which are concealed by display:none, like in the dropbuttons, aren't available to DragonNS.)
Then look at the Views UI settings page for that content listing. The main views settings area has about 50 links, in addition to showing a preview of the entire content listing. So now we have ~250 links on that page.
On the front-end website, a node listing might have read-more, "2 comments", add new comment, image field links, and taxonomy term links. The standard profile only shows 10 nodes, but site builders can easily increase that. Forums pages can have just as many links, because they have node titles, authors, new/unread comments, add new comment, etc.
The original report here isn't clear about whether the site being tested was a fresh install of Drupal core, or a fully fledged project in the real world. If it's the latter then all bets are off - there's no telling how many links a site builder might configure into a page.
Comment #9
andrewmacpherson commentedIdea: what if the admin/content view showed 25 items per page, instead of 50? That would reduce the total there by 75 links right away.
And maybe we wouldn't have to treat the author name as a link - the purpose of the page is to review a list of content, not provide quick access to user profiles. That would take off another link per row, saving a further 25 links.
Comment #10
andrewmacpherson commentedAnother thing I'm not sure about, is whether it's just the number of links on the page, or the total number of clickable controls. Because if checkboxes and buttons factor into this, there are another 2 "clickables" per row on the admin/content listing, so it's more like 300 in total.
Comment #11
andrewmacpherson commentedFor the first part...
It would be good to know which links fail to work.
We have some buttons that are styled to look like links: blue text, no border. So maybe that's why "click link fails to work - because they're actually buttons? Some examples I'm thinking of are:
Comment #12
andrewmacpherson commentedI found a couple of references to how many links might be too many for DragonNS:
Source: KnowBrainer Speech Recognition Forums - Too many links on page? (Forum post from 2008)
Source: Naturally Speaking Quick Tips (as of 05/04/2018)
There are some interesting things in these references:
I think we've got enough information here to make the issue active again, and some ideas for how we could address part B from the issue summary. I'm going to suggest the ideas from comment #9 to the usability team.
Comment #13
andrewmacpherson commentedAsked @yoroy in the #ux Slack channel...
That reduces it from 3 links to 2 links per row, eliminating 50 links from the maximum
Comment #21
smustgrave commentedThis came up as a daily BSI target
The first think I saw was this mentioned IE11 which is no longer supported. Is this still an issue in other browsers?
Comment #23
smustgrave commentedWanted to follow up one more time before closing.
Comment #24
mgiffordWe can always re-open it. I don't know if we have someone who can test with Dragon.
Comment #25
smustgrave commentedThanks lets do that!
Assigning credit though.