Using the NVDA screenreader to read a webpage in Firefox under Windows 10, NVDA is announcing "link" whenever it comes across a linked word or phrase. I can't find a way to turn that feature off. I've turned the "Punctuation/Symbol Level" preference to "none", but it still announces links. Is there a way to stop announcing links?
I am unable to get this work, even after closing and re-opening NVDA, so perhaps I am misunderstanding this feature. Maybe you will have better luck:
https://www.nvaccess.org/files/nvda/documentation/userGuide.html?#DocumentFormattingSettings
9.1.12. Document Formatting Settings (NVDA+control+d)
This dialog box is found in the Preferences menu, under "Document Formatting...".
Most of the checkboxes in this dialog are for configuring what type of formatting you wish to have reported as you move the cursor around documents. For example, if you check the report font name checkbox, each time you arrow onto text with a different font, the name of the font will be announced.
[…]
Elements
Headings
Links
Lists
Block quotes
Landmarks
Frames
Clickable
Related
I have a complex multi-column form that the NVDA screen reader reads perfectly well after the page loads, including aria-labels, fields, order of elements, etc. In this working scenario, the form is fully visible when the page loads.
However, I need to hide this form by default when the page loads. This form should only appear if the user clicks a "Show form" link on the page, setting the form from "display: none" to "display: block".
By default, the reader won't automatically read the form after I click "Show form".
So I added aria-live="polite" to the form. The reader will read the form when I click the "Show form" link, but the reading is very poor - things gets mixed, aria-labels get ignored, the reading flow breaks, etc.
So my question is, using a screen reader like NVDA, how do I get a clean and accurate reading of an element that goes from display: none to display: block (based on some user interaction) after the page is loaded?
As I mentioned above, I get a perfect reading only if the form is visible when the page loads.
Aria live regions are only read in two occasions:
When they are added in the DOM
When their content changes
IN all other cases, it isn't officially specified if they must be read or not. They are with some browsers + screen readers combinations, but not with some others.
IN any way, it isn't a good idea to read an entire form section.
If the user can quite well expect something to appear, it's much more important to make it naturally reachable, than to announce the fact that it appeared. By naturally reachable, I mean both by tab and by browser cursor commands like arrow keys or navigation from form element to form element.
In particular, it means that you should for example avoid adding new content at the end of the body, but rather add it in the DOM where it is really expected instead.
Once this is correctly done, at that moment you may think about announcing that the form section appeared. You shouldn't make the whole new section being read, but stick to a simple general message, like "Personal information section appeared below general information". This kind of message has to be in an aria live region.
If that form section appears quite unexpectedly from the user point of view, this announcement can be really useful. If what happens is quite expected, that announcement is relatively optional, if you have made it appear at the right place.
At our company, we use chrome and have the 3CX chrome extension.
This extension is quite eager to transform any sequence of number into a clickable link to pass a phone call.
How to prevent the 3CX extension from converting sequences of numbers into clickable links on specific pages ?
So far we figured out that enclosing numbers in a <pre> or <code> tag does the trick. But we need something to disable 3CX as a whole on a webpage.
Does a special meta tag exists for this purpose ?
So I ran into the same problem my company uses 3cx extension, but it keeps modifying our page to add "click to call" links where it shouldn't.
I found this thread on the official forum which says that apparently they have no options to force the extension to ignore a specific website or field:
https://www.3cx.com/community/threads/disable-the-chrome-extension-for-my-website.79302/
But on the bright side, I implemented a hack on my field to force the extension to ignore numbers on my string, I added zero-width space after each number like this:
str.split(/(\d+)/g).join('<zero-width-space>');
the editor does not let me paste the code for the zero-width space, it can be acquired here: https://codepen.io/chriscoyier/pen/AwVNjg%E2%80%8B%E2%80%8B
Try this
Admin Panel>Extensions>Click to Talk> untick the box labeled "Click2Talk"at the top of the page.
Does anyone know if the aria authoring web page is keyboard accessible(https://www.w3.org/TR/wai-aria-practices-1.1/) ? Looking for keyboard interaction assistance to move focus between the left and right pane.
It'd be nice if browsers took advantage of landmarks so that keyboard users would benefit. Currently, only screen reader users benefit from them. Most applications on a PC allow the F6 key to navigate to different areas. Try it in Word, Excel, browsers, whatever desktop apps. It even sort of works on the authoring practice page, but not completely (at least not in firefox).
We had to implement our own landmarks dialog that we invoked with Ctrl+F6 (so it'd be similar to F6) and we'd query the page for landmark roles and display them in a dialog to allow you to quickly jump to a section of the page.
Skip links are about as close as you can get now, but even that wouldn't help on a page like the authoring practice. If I had tabbed through half the links in the left nav panel and then decided I wanted to move the main contents in the right panel, a skip link wouldn't help. I'd have to navigate back to the skip link in order to jump to the main section. It'd be nice to hit a key while I was in the middle of the left nav to jump me to the right side.
You could use the accesskey attribute to allow a shortkey to move between the two, but those are hard to discover. JAWS will tell you about the accesskey but NVDA and VoiceOver will not. If you don't have any indication on the screen that there's a shortcut/accesskey, then how will people know it's there. Once they know about it, it's great. For example, wikipedia has an accesskey='f' on the search field, but you might not know that. Once you do know it, it's great to be in the middle of a wiki article and hit alt+shift+f (on firefox and chrome) or alt+f (internet explorer) to quickly jump to the search field.
You could do the same with a left panel / right panel configuration if you had an accesskey on an object in the left panel and a different accesskey on an object in the right panel. Just make sure users know about it.
I'm trying to test the screenreader dialogue on my application for 508 compliance. It works mostly how it should except a problem I'm running into is when I navigate element to element the screenreader reads each keystroke like so "TAB" when I want to traverse through my application. How can I turn this off while testing? I'm running JAWS 17.
You can't and you shouldn't. Different verbosity settings like functional keys announcement, punctuation reading, repeated characters announcement, treatment of dialog controls and so on, and so forth, — all of these are entirely up to the screen reader and the user who adjusts these settings. Just like, for example, speech rate or pitch. As a JAWS user, I wouldn't be happy, and more than that, I would be angry if some app developer forced me to turn off my Tab announcement or changed my punctuation level.
Update: If you just want to turn off keystrokes announcement for yourself, do the following:
Press Insert+6 on the number row to go to JAWS Settings Center. You can do this from the JAWS main menu, but the single keystroke is much faster.
If you want to make your change by default for all apps, press Ctrl+Shift+D to open the default file.
In the search box type labels and search for Key Labels.
In the dialog that appears turn off the announcement for all of the keystrokes you don't want to hear. Note that if you mute Tab, all of the keystrokes like Shift+Tab and Ctrl+Tab will be muted automagically.
click OK several times to leave Settings Center and save your settings.
It's just a user setting options.
If you do that in your jaws, it's coild bé different for an other person !
I'm using visual editor as Widget, and i create google fonts in order to choose the letter, color , basically control the fonts.
But i'm not understanding why do I have so many space between lines. How you can see in the picture, I have a lot of space Between Morada and Rua da Praça. And again between 7645 Vila Mova.
can you explain me where and how can I control that space?
Open the page with a browser. See what tags you are having there and what is their styling. For instance, if you open the page with Chrome and open the browser console, by right-clicking and clicking on Inspect Element, then you see the generated html. Click on the tags where you have the problem and see the CSS rules. Try to untick some of the rules until you manage to get rid of the problem. Your last untick is on the CSS rule which yields the problem. If you still did not find the solution, see whether there are tags, like <br/> and click on them still in the console, press backspace. If you manage to reduce the gap, then those tags are to blame. If you still did not find the source of the problem, then see the parent of the tags and check their stylings. And so forth, until you find the exact issue.