updated SkipTo.js version to a version that supports "instant" scrolling

[jongund]

This version of skipto supports scrolling, but it is off by default.
Feedback that I have received indicates people with motion distractions want an opt in, rather than default feature, So need to discuss at an upcoming meeting.

---

WAI Preview Link (Last built on Thu, 17 Oct 2024 00:08:33 GMT).

[css-meeting-bot]

The ARIA Authoring Practices (APG) Task Force just discussed Skipto Update.

The full IRC log of that discussion

<jugglinmike> Topic: Skipto Update
<jugglinmike> github: https://github.com//pull/3141
<jugglinmike> Matt_King: Jon made some changes to skipto and submitted them as a pull request
<jugglinmike> Jon: I've been testing here at the University of Illinois. The feedback I received means that none of the changes will be perceptible to end users
<jugglinmike> Jon: I added a new "scrollTo" feature which is off by default. I could enable that feature if you would like, but consensus here at the University of Illinois was to disable it
<jugglinmike> Jon: besides that, there are changes under-the-hood related to web components
<jugglinmike> Matt_King: The motion is in direct response to pressing a key, so don't we always expect some kind of change in that case?
<jugglinmike> Matt_King: I always thought the motion thing was... Well, maybe the problem is the smooth-scrolling specifically
<jugglinmike> Jon: I can enable the "instant scroll" variant of the feature and people can take a look at that
<jugglinmike> Jon: I can also open a separate pull request with the "smooth scroll" variant of the feature. With two pull requests, people would be better-equipped to compare
<dmontalvo> q+ Lola
<jugglinmike> Matt_King: I think we should evaluate it within this group. There's even the possibility that you could add something to feature--somehow making it easy for people to update their setting directly
<dmontalvo> q+ howard-e
<jugglinmike> Jon: Let's let people try the two kinds of scrolling and test to make sure that it gets disabled when people turn off the feature on their OS
<jugglinmike> Matt_King: Sounds good
<jugglinmike> Lola: Is there a place for the user to control scrolling in the place where the scrolling is?
<jugglinmike> Jon: there is not right now
<jugglinmike> Lola: I think there would need to be if it were on by default. I believe WCAG requires that users have the ability to adjust animation whenever it is used
<jugglinmike> Jon: scrolling only occurs when people use skipTo
<jugglinmike> Matt_King: I don't know if this counts as animation. This is exactly the same kind of scrolling that you get with tabs
<dmontalvo> ack Lola
<jugglinmike> Jon: think the next step is for people to try it
<jugglinmike> Jon: I'll make that second pull request
<jugglinmike> ack howard-e
<jugglinmike> howard-e: It sounds to me like the scroll is controlled in the script itself. Or is it in an HTML attribute?
<jugglinmike> Jon: It can be controlled through a data- attribute, yet
<jugglinmike> Jon: there are three states: none, smooth, and instant
<jugglinmike> s/yet/yes/