In-Process is out - featuring news on NVDA 2024.4.2, our new add-on survey, a very successful SPEVI 2025 conference, and a User's guide: What to do if your add-on breaks?
Read the full issue now at:
nvaccess.org/post/in-process-2…
and remember, you can now subscribe to receive In-Process via email at: eepurl.com/iuVyjo
#NVDA #NVDAsr #Blog #News #Newsletter #WhatsOn #ScreenReader #Accessibility
In-Process 20th January 2025
Welcome to 2025! And to those subscribed to receive In-Process via email, welcome to the first edition direct to your inbox! We hope you all had a bit of a break and some time with loved ones. We a…NV Access
Tamas G reshared this.
James Scholes
in reply to NV Access • • •NV Access
in reply to James Scholes • • •James Scholes
in reply to NV Access • • •NV Access
in reply to James Scholes • • •James Scholes
in reply to NV Access • • •NV Access
in reply to James Scholes • • •@jscholes Do the links other than the first one (ie add-on survey, SPEVI conference etc) - Looking at w3schools.com/html/html_id.asp what I've done should work, ie:
<a href="#C4">Jump to Chapter 4</a> which links to
<h2 id="C4">Chapter 4</h2>
BUT I noticed in there "The id name ... cannot start with a number". The first TOC entry for the 2024.4.2 update has a number for the ID. I've never noticed an issue before, apparently it SHOULD work fine with HTML, but CSS may not: benfrain.com/when-and-where-yo…
W3Schools.com
www.w3schools.comNV Access
in reply to NV Access • • •@jscholes I'm not sure if Windows / Chrome / Firefox / NVDA are happy to work with my numerical ID, and for some reason IOS / Safari / VoiceOver is not?
I just updated it to ensure ALL the ID's start with letters now. I'd be interested to know if it works now? If not, maybe there is an iOS / Safari / VoiceOver bug?
James Scholes
in reply to NV Access • • •NV Access
in reply to James Scholes • • •James Scholes
in reply to NV Access • • •A `tabindex` value of `"-1"` either:
1. removes an element from the tab order; or
2. makes an element programmatically focusable when it isn't already.
The second category is what applies here, because a heading isn't focusable by default. If you want focus to move to it (in this case by clicking a link) as opposed to the browser only scrolling the page, it should be made focusable via `tabindex="-1"`.
webaim.org/techniques/keyboard…
WebAIM: Keyboard Accessibility - Tabindex
webaim.orgJames Scholes
in reply to James Scholes • • •Here's an example page which does work correctly with VoiceOver, where the "Tuesday", "Wednesday" and "Thursday" links cause the corresponding headings to be correctly focused because the `<h2>` elements have `tabindex="-1"`.
m4c.space/convening24/program/
Program – Mosaic Convening – Mosaic
m4c.spaceJames Scholes
in reply to James Scholes • • •I'll also note that the links on the In-Process page don't actually work correctly in Chrome on Windows either, even though NVDA gives the impression that they do. If you activate e.g. "Add-on survey" and then press NVDA+Tab, you hear:
"NV Access | In-Process 20th January 2025 document focused read only"
... instead of:
"Add-on survey heading focused"
In other words, the page scrolls and NVDA announces the heading, but keyboard focus doesn't actually move there. `tabindex="-1"` will also fix this.
Marco Zehe
in reply to James Scholes • • •James Scholes
in reply to Marco Zehe • • •Jamie Teh
in reply to James Scholes • • •James Scholes
in reply to Jamie Teh • • •We still run into instances where skip links targeting headings fail to provide an equitable experience without the target being focusable. It's possible that in such cases, there is something else wrong on the page. At the same time, adding the tabindex fixes the problem, allows SR users to determine the new focus point instead of it being on the body, and provides a visible indication of focus for people who benefit from that (particularly if coupled with :focus-visible).
I think it's good to know if a given technique should no longer technically be required especially if it leads to knowledge of an Apple bug (that they won't fix), but I maintain that there's an easy way to improve this situation with no negative side effects, and so whether it should need the workaround or not is practically moot for users.
On the other hand, we've now spent more time talking about the problem than it would've taken me to read the whole page so... shrug :)
@marco @NVAccess
Justin Yarbrough
in reply to James Scholes • • •NV Access
in reply to Justin Yarbrough • • •Justin Yarbrough
in reply to NV Access • • •James Scholes
in reply to NV Access • • •@jyarbrough @jcsteh @marco Moving focus can be a sticky topic because it causes an outline/ring to appear around the thing that receives it (at least on accessible sites). Many web designers for some reason have an aversion to this happening when a focus change is triggered with a mouse, and this may explain why browser developers have been hesitant to do more than just scrolling for skip links.
Then again, this is a complete guess and could be wildly off the mark.
NV Access
in reply to James Scholes • • •James Scholes
in reply to NV Access • • •