(unknown charset) RE: Skip to content link

To be sure, I later saw your options comments.
Still the use of equals at all  suggests equal to.
Actually my understanding is that the code is not about tool, but 
interaction.  Meaning many  use a number of tools to manage their 
interaction?
Kare



On Tue, 12 Mar 2024, Kevin Prince wrote:

> Absolutely they can, I don't think I implied otherwise (and as President
> of Deafblind New Zealand I wouldn't dare😊 ). Maybe the == didn't come
> across as being Always and entirely equal to.
> 
> Kevin Prince
> Product Accessibility & Usability Consultant
> 
> Foster Moore
> A Teranet Company
> 
> E kevin.prince@fostermoore.com
> Christchurch
> fostermoore.com
> -----Original Message-----
> From: Karen Lewellen <klewellen@shellworld.net>
> Sent: Wednesday, March 13, 2024 9:47 AM
> To: Kevin Prince <kevin.prince@fostermoore.com>
> Cc: Adam Cooper <cooperad@bigpond.com>; 'Tom Shaw'
> <tom-shaw@hotmail.com>; w3c-wai-ig@w3.org
> Subject: RE: Skip to content link
> 
> [You don't often get email from klewellen@shellworld.net. Learn why this
> is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> CAUTION: This email originated from outside of the organization.
> 
> 
> Kevin,
> Perhaps I am naive, but why cannot a person end up with more than one
> disability experience?
> And, are there not several definitions of a keyboard user, i. e. one
> using their keyboard to manage individual access needs?
> Further, I am confused entirely by the screen reader users, as if all
> users, and screen readers are uniform?
> Karen
> 
> 
> 
> On Tue, 12 Mar 2024, Kevin Prince wrote:
> 
> > But keyboard users is not==screenreader users. And skip links are not
> primarily for screenreaders users (who have a bunch of other tools).
> >
> > Kevin
> >
> > From: Adam Cooper <cooperad@bigpond.com>
> > Sent: Friday, March 8, 2024 1:32 PM
> > To: 'Tom Shaw' <tom-shaw@hotmail.com>; w3c-wai-ig@w3.org
> > Subject: RE: Skip to content link
> >
> > You don't often get email from
> > cooperad@bigpond.com<mailto:cooperad@bigpond.com>. Learn why this is
> > important<https://aka.ms/LearnAboutSenderIdentification>
> > CAUTION: This email originated from outside of the organization.
> >
> > As a screen reader user for about 20 years , I have never used either a
> skip to link or a back to link to navigate a view because these features
> are typically poorly implemented and support for conventional
> implementations has been inconsistent during this time.
> >
> > By 'poor implementation' I mean mechanisms that don't actually move
> virtual cursor focus, land on the same spot for every view regardless of
> their content, land on the first natively focusable element in content,
> skip past useful information, skip to irrelevant parts of the screen, and
> so on ... the feature-presence checklist approach to WCAG is much to
> blame here in my view.
> >
> >
> >
> > But, more importantly, why would I bother using a skip link when screen
> reader applications provide much more efficient and diverse ways of
> entering the content of a view ...
> >
> > people who are trained to use a screen reader in this country typically
> don't use skip features either in my experience because their
> navigational strategies - just like the functionality offered in screen
> readers - is element based ... e.g., quick use key navigation in
> JAWS-speak.
> >
> > Putting the very limited sample of the WebAIM SR users survey aside,
> I'd be interested to know whether people who use a screen reader as a
> result of a lack of functional vision actually use these features and
> under what circumstances ... or whether this is just yet another
> accessibility industry sacred cow.
> >
> >
> >
> >
> >
> > From: Tom Shaw <tom-shaw@hotmail.com<mailto:tom-shaw@hotmail.com>>
> > Sent: Friday, March 8, 2024 12:12 AM
> > To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
> > Subject: Skip to content link
> >
> > Hi there.
> >
> > I have a very long GOV.UK process with lots of pages. The first page I
> activate the skip to content link and it works as expected, however, for
> the rest of the hjourney users are now automatically taken to the main
> content everytime because the anchor in the URL #main-content' is always
> there. So it often skips the h1, hint text, back link etc....therefore
> I'd say affecting SR and KO users. I understand this is a potentially a
> backend mistake but I still feel this falls under 2.4.3 Focus Order? Is
> this right?
> >
> > Thank you.
> >
> >
> > Kevin Prince
> >
> > Product Accessibility & Usability Consultant
> >
> >
> >
> > E kevin.prince@fostermoore.com
> >
> > Christchurch
> >
> > fostermoore.com
> >
> > This email and its contents are confidential. If you are not the
> intended recipient, you should contact the sender immediately, you must
> not use, copy or disclose any of the information in the email, and you
> must delete it from your system immediately.
> 
>