E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 15 (In chronological order)

From: Lucy Greco
Date: Fri, May 10 2019 5:56PM
Subject: links to the page they are on
No previous message | Next message →

hello:

i personaly do not like having links on a web page to the page itself as
it can be vary frustrating for a user if they think they have gone to a new
page and find they are on the same page. could some one tell me wair to
find this problem in the w3c speck thanks
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces

From: Patrick H. Lauke
Date: Fri, May 10 2019 6:03PM
Subject: Re: links to the page they are on
← Previous message | Next message →

On 11/05/2019 00:56, Lucy Greco wrote:
> hello:
>
> i personaly do not like having links on a web page to the page itself as
> it can be vary frustrating for a user if they think they have gone to a new
> page and find they are on the same page. could some one tell me wair to
> find this problem in the w3c speck thanks

If you mean if this is addressed in WCAG, then no...it's a general
usability, rather than accessibility, issue ... so nothing that would
directly contravene any SC.

For AT users, the issue can be mitigated by adding aria-current="page"
to the link, which will (in supported browser/AT combos) at least
announce that the link relates to the current page.
https://www.w3.org/TR/wai-aria-1.1/#aria-current

And yes, while it can be annoying having a link basically to where you
are, there's also an argument that this creates a certain consistency
(so the navigation has the same actionable links in every page).

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Lucy Greco
Date: Fri, May 10 2019 6:06PM
Subject: Re: links to the page they are on
← Previous message | Next message →

thanks for the quick reply so the cognative working group did not think
this was a problem? interesting
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



On Fri, May 10, 2019 at 5:03 PM Patrick H. Lauke < = EMAIL ADDRESS REMOVED = >
wrote:

> On 11/05/2019 00:56, Lucy Greco wrote:
> > hello:
> >
> > i personaly do not like having links on a web page to the page itself
> as
> > it can be vary frustrating for a user if they think they have gone to a
> new
> > page and find they are on the same page. could some one tell me wair to
> > find this problem in the w3c speck thanks
>
> If you mean if this is addressed in WCAG, then no...it's a general
> usability, rather than accessibility, issue ... so nothing that would
> directly contravene any SC.
>
> For AT users, the issue can be mitigated by adding aria-current="page"
> to the link, which will (in supported browser/AT combos) at least
> announce that the link relates to the current page.
> https://www.w3.org/TR/wai-aria-1.1/#aria-current
>
> And yes, while it can be annoying having a link basically to where you
> are, there's also an argument that this creates a certain consistency
> (so the navigation has the same actionable links in every page).
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >

From: glen walker
Date: Fri, May 10 2019 6:08PM
Subject: Re: links to the page they are on
← Previous message | Next message →

I agree with Patrick. The only time I recommend that links should go to
themselves is in a breadcrumb trail and I use aria-current="page" on the
self link, as Patrick described. I do that for UX reasons so that the
entire breadcrumb trail can be tabbed to.

From: Patrick H. Lauke
Date: Fri, May 10 2019 6:09PM
Subject: Re: links to the page they are on
← Previous message | Next message →

On 11/05/2019 01:06, Lucy Greco wrote:
> thanks for the quick reply so the cognative working group did not think
> this was a problem? interesting

I can't speak for the group, but I can say that they did not put forward
any SCs that made it into WCAG concerning this particular issue.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Ryan E. Benson
Date: Fri, May 10 2019 9:15PM
Subject: Re: links to the page they are on
← Previous message | Next message →

To clarify, you are talking about if example.com/second-page, has <a href="
http://example.com/second-page">Second page</a>, and not <a href="
http://example.com/second-page#subSection>;go to the subsection</a>, correct?

--
Ryan E. Benson


On Fri, May 10, 2019 at 8:07 PM Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:

> thanks for the quick reply so the cognative working group did not think
> this was a problem? interesting
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
>
> On Fri, May 10, 2019 at 5:03 PM Patrick H. Lauke < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > On 11/05/2019 00:56, Lucy Greco wrote:
> > > hello:
> > >
> > > i personaly do not like having links on a web page to the page itself
> > as
> > > it can be vary frustrating for a user if they think they have gone to a
> > new
> > > page and find they are on the same page. could some one tell me wair to
> > > find this problem in the w3c speck thanks
> >
> > If you mean if this is addressed in WCAG, then no...it's a general
> > usability, rather than accessibility, issue ... so nothing that would
> > directly contravene any SC.
> >
> > For AT users, the issue can be mitigated by adding aria-current="page"
> > to the link, which will (in supported browser/AT combos) at least
> > announce that the link relates to the current page.
> > https://www.w3.org/TR/wai-aria-1.1/#aria-current
> >
> > And yes, while it can be annoying having a link basically to where you
> > are, there's also an argument that this creates a certain consistency
> > (so the navigation has the same actionable links in every page).
> >
> > P
> > --
> > Patrick H. Lauke
> >
> > www.splintered.co.uk | https://github.com/patrickhlauke
> > http://flickr.com/photos/redux/ | http://redux.deviantart.com
> > twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > > > > > > >
> > > > >

From: James A.
Date: Sat, May 11 2019 1:21AM
Subject: Re: links to the page they are on
← Previous message | Next message →

Hi Lucy

In-page links can be useful in some cases for people with cognitive disabilities. For example, table of contents and links to sections can help with orientating users and avoid unnecessary reading. The problem can occur if there is no means of returning to the original location on the page. The UK government website uses this approach well eg https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps#contents

Another useful use case for many users is when there is a footnote, for example to small print or terms and conditions which are frequently indicated by *.

I consider that 2.4.4 Links Purpose covers the need to ensure all users understand the purpose of the link is to move within the page.

Best wishes

Abi James

University of Southampton
Abilitynet & British Dyslexia Association

Sent from my iPhone

On 11 May 2019, at 01:09, Patrick H. Lauke < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:

On 11/05/2019 01:06, Lucy Greco wrote:
thanks for the quick reply so the cognative working group did not think
this was a problem? interesting

I can't speak for the group, but I can say that they did not put forward any SCs that made it into WCAG concerning this particular issue.

P
--
Patrick H. Lauke

https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 | https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatrickhlauke&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAMyvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4vyEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0 | https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Patrick H. Lauke
Date: Sat, May 11 2019 2:17AM
Subject: Re: links to the page they are on
← Previous message | Next message →

It was my understanding that Lucy meant the former (the link to the current page is still a clickable link in the navigation), not the latter (in-page anchor-type links)

P

> On 11 May 2019, at 04:15, Ryan E. Benson < = EMAIL ADDRESS REMOVED = > wrote:
>
> To clarify, you are talking about if example.com/second-page, has <a href="
> http://example.com/second-page">Second page</a>, and not <a href="
> http://example.com/second-page#subSection>;go to the subsection</a>, correct?
>
> --
> Ryan E. Benson
>
>
>> On Fri, May 10, 2019 at 8:07 PM Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> thanks for the quick reply so the cognative working group did not think
>> this was a problem? interesting
>> Lucia Greco
>> Web Accessibility Evangelist
>> IST - Architecture, Platforms, and Integration
>> University of California, Berkeley
>> (510) 289-6008 skype: lucia1-greco
>> http://webaccess.berkeley.edu
>> Follow me on twitter @accessaces
>>
>>
>>
>> On Fri, May 10, 2019 at 5:03 PM Patrick H. Lauke < = EMAIL ADDRESS REMOVED = >
>> wrote:
>>
>>>> On 11/05/2019 00:56, Lucy Greco wrote:
>>>> hello:
>>>>
>>>> i personaly do not like having links on a web page to the page itself
>>> as
>>>> it can be vary frustrating for a user if they think they have gone to a
>>> new
>>>> page and find they are on the same page. could some one tell me wair to
>>>> find this problem in the w3c speck thanks
>>>
>>> If you mean if this is addressed in WCAG, then no...it's a general
>>> usability, rather than accessibility, issue ... so nothing that would
>>> directly contravene any SC.
>>>
>>> For AT users, the issue can be mitigated by adding aria-current="page"
>>> to the link, which will (in supported browser/AT combos) at least
>>> announce that the link relates to the current page.
>>> https://www.w3.org/TR/wai-aria-1.1/#aria-current
>>>
>>> And yes, while it can be annoying having a link basically to where you
>>> are, there's also an argument that this creates a certain consistency
>>> (so the navigation has the same actionable links in every page).
>>>
>>> P
>>> --
>>> Patrick H. Lauke
>>>
>>> www.splintered.co.uk | https://github.com/patrickhlauke
>>> http://flickr.com/photos/redux/ | http://redux.deviantart.com
>>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>> >>> >>> >>> >>>
>> >> >> >> >>
> > > >

From: Wolfgang Berndorfer
Date: Sat, May 11 2019 9:21AM
Subject: Re: links to the page they are on
← Previous message | Next message →

I think, In-side links can improve usability not only for people with
cognitive disabilities. TOC and footmarks have already been mentioned.

What more? Reading a web side is not like reading a novel from the beginning
to the end. When I seek information on a side, I first try to get an
overview by checking available headings. If the heading text seems helpful,
I read the subcontent. This strategy is helpful for all and highly
recommendable for people, who use screen readers, like me.

If in the subcontent I inquire, topics are contained, which already have
been discussed on the same side, it’s very helpful, when they are linked.

Complementary:
a) Metainfos for links like In-Side-Links have lately been discussed here
under the thread “Meta Infos necessary in links”. (Sorry: Didn’t find any
direct online resource on webaim for the thread.).
b) UX is not the same as usability. The user experience is too often bad
usability. No helpful headings …
Wolfgang 

-----Ursprüngliche Nachricht-----
Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im Auftrag
von James A.
Gesendet: Samstag, 11. Mai 2019 09:22
An: WebAIM Discussion List
Betreff: Re: [WebAIM] links to the page they are on

Hi Lucy

In-page links can be useful in some cases for people with cognitive
disabilities. For example, table of contents and links to sections can help
with orientating users and avoid unnecessary reading. The problem can occur
if there is no means of returning to the original location on the page. The
UK government website uses this approach well eg
https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-web
sites-and-apps#contents

Another useful use case for many users is when there is a footnote, for
example to small print or terms and conditions which are frequently
indicated by *.

I consider that 2.4.4 Links Purpose covers the need to ensure all users
understand the purpose of the link is to move within the page.

Best wishes

Abi James

University of Southampton
Abilitynet & British Dyslexia Association

Sent from my iPhone

On 11 May 2019, at 01:09, Patrick H. Lauke
< = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:

On 11/05/2019 01:06, Lucy Greco wrote:
thanks for the quick reply so the cognative working group did not think
this was a problem? interesting

I can't speak for the group, but I can say that they did not put forward any
SCs that made it into WCAG concerning this particular issue.

P
--
Patrick H. Lauke

https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp
;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4
a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%
2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 |
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com
%2Fpatrickhlauke&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4
bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAM
yvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%
2Fphotos%2Fredux%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a14
8f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4v
yEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0 |
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devia
ntart.com&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d
6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%
2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
twitter: @patrick_h_lauke | skype: patrick_h_lauke
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim
.org%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d
5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiq
KpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
List archives at
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%
2Fdiscussion%2Farchives&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac5
2a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMl
tgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >

From: Lucy Greco
Date: Mon, May 13 2019 4:07PM
Subject: Re: links to the page they are on
← Previous message | Next message →

Hello:
Let me clarify a little. I have no issue with same-page links. All the
aforementioned reasons I agree with and would always encourage.

I'm talking about those links that, when clicked, only refresh the page you
are on. So, for example, you are reading an article about the health care
system, and in the body of the article there is a link to the article, and
in the "Recently posted" footer of the article, there is a link to the
article, and in the menu there is also is a link to the article. Each of
these links will refresh the page and sometimes just go back to the top of
the page, and then the user wonders why the link did not work.

Thanks,
Lucy

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



On Sat, May 11, 2019 at 8:21 AM Wolfgang Berndorfer <
= EMAIL ADDRESS REMOVED = > wrote:

> I think, In-side links can improve usability not only for people with
> cognitive disabilities. TOC and footmarks have already been mentioned.
>
> What more? Reading a web side is not like reading a novel from the
> beginning
> to the end. When I seek information on a side, I first try to get an
> overview by checking available headings. If the heading text seems helpful,
> I read the subcontent. This strategy is helpful for all and highly
> recommendable for people, who use screen readers, like me.
>
> If in the subcontent I inquire, topics are contained, which already have
> been discussed on the same side, it's very helpful, when they are linked.
>
> Complementary:
> a) Metainfos for links like In-Side-Links have lately been discussed here
> under the thread "Meta Infos necessary in links". (Sorry: Didn't find any
> direct online resource on webaim for the thread.).
> b) UX is not the same as usability. The user experience is too often bad
> usability. No helpful headings …
> Wolfgang
>
> -----Ursprüngliche Nachricht-----
> Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im Auftrag
> von James A.
> Gesendet: Samstag, 11. Mai 2019 09:22
> An: WebAIM Discussion List
> Betreff: Re: [WebAIM] links to the page they are on
>
> Hi Lucy
>
> In-page links can be useful in some cases for people with cognitive
> disabilities. For example, table of contents and links to sections can help
> with orientating users and avoid unnecessary reading. The problem can occur
> if there is no means of returning to the original location on the page. The
> UK government website uses this approach well eg
>
> https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-web
> sites-and-apps#contents
> <https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps#contents>
>
> Another useful use case for many users is when there is a footnote, for
> example to small print or terms and conditions which are frequently
> indicated by *.
>
> I consider that 2.4.4 Links Purpose covers the need to ensure all users
> understand the purpose of the link is to move within the page.
>
> Best wishes
>
> Abi James
>
> University of Southampton
> Abilitynet & British Dyslexia Association
>
> Sent from my iPhone
>
> On 11 May 2019, at 01:09, Patrick H. Lauke
> < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:
>
> On 11/05/2019 01:06, Lucy Greco wrote:
> thanks for the quick reply so the cognative working group did not think
> this was a problem? interesting
>
> I can't speak for the group, but I can say that they did not put forward
> any
> SCs that made it into WCAG concerning this particular issue.
>
> P
> --
> Patrick H. Lauke
>
>
> https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp
> ;data
%7C01%7Ca.james%40soton.ac.uk
> %7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4
>
> a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%
> 2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 |
>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com
> %2Fpatrickhlauke&amp;data
%7C01%7Ca.james%40soton.ac.uk
> %7C5cc6c5ac52a148f4
>
> bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAM
> yvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%
>
> 2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a14
>
> 8f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4v
> yEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4vyEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0>
> |
>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devia
>
> ntart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d
>
> 6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%
> 2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0>
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > >
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim
>
> .org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d
>
> 5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiq
> KpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim.org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiqKpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0>
> List archives at
>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%
>
> 2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac5
>
> 2a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMl
> tgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMltgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0>
> > = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> > > > >
> > > > >

From: Birkir R. Gunnarsson
Date: Mon, May 13 2019 5:12PM
Subject: Re: links to the page they are on
← Previous message | Next message →

This is where aria-current="page" would be handy, jut put it on the
link and the screen reader will announce "current page".
If there are visual cues that the links point to the current page yu
can make it a WCAG 1.1.1 or 1.3.1 requirement (1.1.1 if it is an icon,
1.3.1 if it is communicated through styling or formatting), that, or
that the links be neutered by removing their href attributes, but if
not it's a screen reader usability recommendation.



On 5/13/19, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
> Hello:
> Let me clarify a little. I have no issue with same-page links. All the
> aforementioned reasons I agree with and would always encourage.
>
> I'm talking about those links that, when clicked, only refresh the page you
> are on. So, for example, you are reading an article about the health care
> system, and in the body of the article there is a link to the article, and
> in the "Recently posted" footer of the article, there is a link to the
> article, and in the menu there is also is a link to the article. Each of
> these links will refresh the page and sometimes just go back to the top of
> the page, and then the user wonders why the link did not work.
>
> Thanks,
> Lucy
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
>
> On Sat, May 11, 2019 at 8:21 AM Wolfgang Berndorfer <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> I think, In-side links can improve usability not only for people with
>> cognitive disabilities. TOC and footmarks have already been mentioned.
>>
>> What more? Reading a web side is not like reading a novel from the
>> beginning
>> to the end. When I seek information on a side, I first try to get an
>> overview by checking available headings. If the heading text seems
>> helpful,
>> I read the subcontent. This strategy is helpful for all and highly
>> recommendable for people, who use screen readers, like me.
>>
>> If in the subcontent I inquire, topics are contained, which already have
>> been discussed on the same side, it's very helpful, when they are linked.
>>
>> Complementary:
>> a) Metainfos for links like In-Side-Links have lately been discussed here
>> under the thread "Meta Infos necessary in links". (Sorry: Didn't find any
>> direct online resource on webaim for the thread.).
>> b) UX is not the same as usability. The user experience is too often bad
>> usability. No helpful headings …
>> Wolfgang
>>
>> -----Ursprüngliche Nachricht-----
>> Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im Auftrag
>> von James A.
>> Gesendet: Samstag, 11. Mai 2019 09:22
>> An: WebAIM Discussion List
>> Betreff: Re: [WebAIM] links to the page they are on
>>
>> Hi Lucy
>>
>> In-page links can be useful in some cases for people with cognitive
>> disabilities. For example, table of contents and links to sections can
>> help
>> with orientating users and avoid unnecessary reading. The problem can
>> occur
>> if there is no means of returning to the original location on the page.
>> The
>> UK government website uses this approach well eg
>>
>> https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-web
>> sites-and-apps#contents
>> <https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps#contents>
>>
>> Another useful use case for many users is when there is a footnote, for
>> example to small print or terms and conditions which are frequently
>> indicated by *.
>>
>> I consider that 2.4.4 Links Purpose covers the need to ensure all users
>> understand the purpose of the link is to move within the page.
>>
>> Best wishes
>>
>> Abi James
>>
>> University of Southampton
>> Abilitynet & British Dyslexia Association
>>
>> Sent from my iPhone
>>
>> On 11 May 2019, at 01:09, Patrick H. Lauke
>> < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:
>>
>> On 11/05/2019 01:06, Lucy Greco wrote:
>> thanks for the quick reply so the cognative working group did not think
>> this was a problem? interesting
>>
>> I can't speak for the group, but I can say that they did not put forward
>> any
>> SCs that made it into WCAG concerning this particular issue.
>>
>> P
>> --
>> Patrick H. Lauke
>>
>>
>> https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp
>> ;data
%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4
>>
>> a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%
>> 2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 |
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com
>> %2Fpatrickhlauke&amp;data
%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a148f4
>>
>> bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAM
>> yvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%
>>
>> 2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a14
>>
>> 8f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4v
>> yEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4vyEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0>
>> |
>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devia
>>
>> ntart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d
>>
>> 6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%
>> 2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0>
>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>> >> >>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim
>>
>> .org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d
>>
>> 5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiq
>> KpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim.org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiqKpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0>
>> List archives at
>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%
>>
>> 2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac5
>>
>> 2a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMl
>> tgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMltgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0>
>> >> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>> >> >> >> >>
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.

From: Wolfgang Berndorfer
Date: Tue, May 14 2019 6:20AM
Subject: Re: links to the page they are on
← Previous message | Next message →

Wouldn’t it already clarify, if it wasn’t a link, but a refresh-*button*?
Aria-current is rather meant for a *collection of links* to inform screen
readers about something, which is somehow highlighted visually as current
already. Guess in Lucys example, there is no collection of links.
Wolfgang 

-----Ursprüngliche Nachricht-----
Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im Auftrag
von Birkir R. Gunnarsson
Gesendet: Dienstag, 14. Mai 2019 01:12
An: WebAIM Discussion List
Betreff: Re: [WebAIM] links to the page they are on

This is where aria-current="page" would be handy, jut put it on the
link and the screen reader will announce "current page".
If there are visual cues that the links point to the current page yu
can make it a WCAG 1.1.1 or 1.3.1 requirement (1.1.1 if it is an icon,
1.3.1 if it is communicated through styling or formatting), that, or
that the links be neutered by removing their href attributes, but if
not it's a screen reader usability recommendation.



On 5/13/19, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
> Hello:
> Let me clarify a little. I have no issue with same-page links. All the
> aforementioned reasons I agree with and would always encourage.
>
> I'm talking about those links that, when clicked, only refresh the page
you
> are on. So, for example, you are reading an article about the health care
> system, and in the body of the article there is a link to the article, and
> in the "Recently posted" footer of the article, there is a link to the
> article, and in the menu there is also is a link to the article. Each of
> these links will refresh the page and sometimes just go back to the top of
> the page, and then the user wonders why the link did not work.
>
> Thanks,
> Lucy
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
>
> On Sat, May 11, 2019 at 8:21 AM Wolfgang Berndorfer <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> I think, In-side links can improve usability not only for people with
>> cognitive disabilities. TOC and footmarks have already been mentioned.
>>
>> What more? Reading a web side is not like reading a novel from the
>> beginning
>> to the end. When I seek information on a side, I first try to get an
>> overview by checking available headings. If the heading text seems
>> helpful,
>> I read the subcontent. This strategy is helpful for all and highly
>> recommendable for people, who use screen readers, like me.
>>
>> If in the subcontent I inquire, topics are contained, which already have
>> been discussed on the same side, it’s very helpful, when they are linked.
>>
>> Complementary:
>> a) Metainfos for links like In-Side-Links have lately been discussed here
>> under the thread “Meta Infos necessary in links”. (Sorry: Didn’t find any
>> direct online resource on webaim for the thread.).
>> b) UX is not the same as usability. The user experience is too often bad
>> usability. No helpful headings …
>> Wolfgang
>>
>> -----Ursprüngliche Nachricht-----
>> Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im
Auftrag
>> von James A.
>> Gesendet: Samstag, 11. Mai 2019 09:22
>> An: WebAIM Discussion List
>> Betreff: Re: [WebAIM] links to the page they are on
>>
>> Hi Lucy
>>
>> In-page links can be useful in some cases for people with cognitive
>> disabilities. For example, table of contents and links to sections can
>> help
>> with orientating users and avoid unnecessary reading. The problem can
>> occur
>> if there is no means of returning to the original location on the page.
>> The
>> UK government website uses this approach well eg
>>
>>
https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-web
>> sites-and-apps#contents
>>
<https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-we
bsites-and-apps#contents>
>>
>> Another useful use case for many users is when there is a footnote, for
>> example to small print or terms and conditions which are frequently
>> indicated by *.
>>
>> I consider that 2.4.4 Links Purpose covers the need to ensure all users
>> understand the purpose of the link is to move within the page.
>>
>> Best wishes
>>
>> Abi James
>>
>> University of Southampton
>> Abilitynet & British Dyslexia Association
>>
>> Sent from my iPhone
>>
>> On 11 May 2019, at 01:09, Patrick H. Lauke
>> < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:
>>
>> On 11/05/2019 01:06, Lucy Greco wrote:
>> thanks for the quick reply so the cognative working group did not
think
>> this was a problem? interesting
>>
>> I can't speak for the group, but I can say that they did not put forward
>> any
>> SCs that made it into WCAG concerning this particular issue.
>>
>> P
>> --
>> Patrick H. Lauke
>>
>>
>>
https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp
>> ;data=01%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4
>>
>>
a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%
>> 2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 |
>>
>>
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com
>> %2Fpatrickhlauke&amp;data=01%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a148f4
>>
>>
bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAM
>> yvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
>>
>>
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%
>>
>>
2Fphotos%2Fredux%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a14
>>
>>
8f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4v
>> yEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
>>
<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com
%2Fphotos%2Fredux%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a1
48f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4
vyEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0>
>> |
>>
>>
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devia
>>
>>
ntart.com&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d
>>
>>
6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%
>> 2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
>>
<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devi
antart.com&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408
d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy
%2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0>
>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>> >> >>
>>
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim
>>
>>
.org%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d
>>
>>
5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiq
>> KpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
>>
<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webai
m.org%2F&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6
d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWi
qKpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0>
>> List archives at
>>
>>
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%
>>
>>
2Fdiscussion%2Farchives&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac5
>>
>>
2a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMl
>> tgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
>>
<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org
%2Fdiscussion%2Farchives&amp;data=01%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac
52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EM
ltgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0>
>> >> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>> >> >> >> >>
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.

From: Patrick H. Lauke
Date: Tue, May 14 2019 6:39AM
Subject: Re: links to the page they are on
← Previous message | Next message →

On 14/05/2019 13:20, Wolfgang Berndorfer wrote:
> Wouldn't it already clarify, if it wasn't a link, but a refresh-*button*?

Who's talking about buttons now? Lucy's talking about links... (the
"refresh" bit she talked about is the effect it has, from a user's point
of view)

> Aria-current is rather meant for a *collection of links* to inform screen
> readers about something, which is somehow highlighted visually as current
> already. Guess in Lucys example, there is no collection of links.

Lucy's mentioned that a link to the current page is present in the
footer under "Recently posted" (assuming it's a list of links) and in
the navigation menu.

In these cases, I'd say aria-current is perfectly fine and as intended.

It's a bit more arguable if aria-current could be added to a link
anywhere in the page that is not in a "collection / list / set" (e.g.
Lucy mentions that the body of the article itself has a self-referential
link back to its own page again).

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: cb
Date: Wed, May 15 2019 3:48PM
Subject: Re: links to the page they are on
← Previous message | Next message →

Does anybody know of a site we could look at now that takes this approach,
neutering the link to the current page in sitewide navigation? I've been
looking for examples and have come up empty.

Caroline

On Mon, May 13, 2019 at 4:12 PM Birkir R. Gunnarsson <
= EMAIL ADDRESS REMOVED = > wrote:

> This is where aria-current="page" would be handy, jut put it on the
> link and the screen reader will announce "current page".
> If there are visual cues that the links point to the current page yu
> can make it a WCAG 1.1.1 or 1.3.1 requirement (1.1.1 if it is an icon,
> 1.3.1 if it is communicated through styling or formatting), that, or
> that the links be neutered by removing their href attributes, but if
> not it's a screen reader usability recommendation.
>
>
>
> On 5/13/19, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
> > Hello:
> > Let me clarify a little. I have no issue with same-page links. All the
> > aforementioned reasons I agree with and would always encourage.
> >
> > I'm talking about those links that, when clicked, only refresh the page
> you
> > are on. So, for example, you are reading an article about the health care
> > system, and in the body of the article there is a link to the article,
> and
> > in the "Recently posted" footer of the article, there is a link to the
> > article, and in the menu there is also is a link to the article. Each of
> > these links will refresh the page and sometimes just go back to the top
> of
> > the page, and then the user wonders why the link did not work.
> >
> > Thanks,
> > Lucy
> >
> > Lucia Greco
> > Web Accessibility Evangelist
> > IST - Architecture, Platforms, and Integration
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> >
> > On Sat, May 11, 2019 at 8:21 AM Wolfgang Berndorfer <
> > = EMAIL ADDRESS REMOVED = > wrote:
> >
> >> I think, In-side links can improve usability not only for people with
> >> cognitive disabilities. TOC and footmarks have already been mentioned.
> >>
> >> What more? Reading a web side is not like reading a novel from the
> >> beginning
> >> to the end. When I seek information on a side, I first try to get an
> >> overview by checking available headings. If the heading text seems
> >> helpful,
> >> I read the subcontent. This strategy is helpful for all and highly
> >> recommendable for people, who use screen readers, like me.
> >>
> >> If in the subcontent I inquire, topics are contained, which already have
> >> been discussed on the same side, it's very helpful, when they are
> linked.
> >>
> >> Complementary:
> >> a) Metainfos for links like In-Side-Links have lately been discussed
> here
> >> under the thread "Meta Infos necessary in links". (Sorry: Didn't find
> any
> >> direct online resource on webaim for the thread.).
> >> b) UX is not the same as usability. The user experience is too often bad
> >> usability. No helpful headings …
> >> Wolfgang
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im
> Auftrag
> >> von James A.
> >> Gesendet: Samstag, 11. Mai 2019 09:22
> >> An: WebAIM Discussion List
> >> Betreff: Re: [WebAIM] links to the page they are on
> >>
> >> Hi Lucy
> >>
> >> In-page links can be useful in some cases for people with cognitive
> >> disabilities. For example, table of contents and links to sections can
> >> help
> >> with orientating users and avoid unnecessary reading. The problem can
> >> occur
> >> if there is no means of returning to the original location on the page.
> >> The
> >> UK government website uses this approach well eg
> >>
> >>
> https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-web
> >> sites-and-apps#contents
> >> <
> https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps#contents
> >
> >>
> >> Another useful use case for many users is when there is a footnote, for
> >> example to small print or terms and conditions which are frequently
> >> indicated by *.
> >>
> >> I consider that 2.4.4 Links Purpose covers the need to ensure all users
> >> understand the purpose of the link is to move within the page.
> >>
> >> Best wishes
> >>
> >> Abi James
> >>
> >> University of Southampton
> >> Abilitynet & British Dyslexia Association
> >>
> >> Sent from my iPhone
> >>
> >> On 11 May 2019, at 01:09, Patrick H. Lauke
> >> < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:
> >>
> >> On 11/05/2019 01:06, Lucy Greco wrote:
> >> thanks for the quick reply so the cognative working group did not
> think
> >> this was a problem? interesting
> >>
> >> I can't speak for the group, but I can say that they did not put forward
> >> any
> >> SCs that made it into WCAG concerning this particular issue.
> >>
> >> P
> >> --
> >> Patrick H. Lauke
> >>
> >>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp
> >> ;data
%7C01%7Ca.james%40soton.ac.uk
> >> %7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4
> >>
> >>
> a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%
> >> 2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 |
> >>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com
> >> %2Fpatrickhlauke&amp;data
%7C01%7Ca.james%40soton.ac.uk
> >> %7C5cc6c5ac52a148f4
> >>
> >>
> bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAM
> >> yvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
> >>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%
> >>
> >> 2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk
> %7C5cc6c5ac52a14
> >>
> >>
> 8f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4v
> >> yEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
> >> <
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4vyEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
> >
> >> |
> >>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devia
> >>
> >> ntart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk
> %7C5cc6c5ac52a148f4bfc408d
> >>
> >>
> 6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%
> >> 2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
> >> <
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
> >
> >> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> >> > >> > >>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim
> >>
> >> .org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk
> %7C5cc6c5ac52a148f4bfc408d6d
> >>
> >>
> 5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiq
> >> KpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
> >> <
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim.org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiqKpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
> >
> >> List archives at
> >>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%
> >>
> >> 2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk
> %7C5cc6c5ac5
> >>
> >>
> 2a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMl
> >> tgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
> >> <
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMltgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
> >
> >> > >> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> >> > >> > >> > >> > >>
> >> > >> > >> > >> > >>
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >

From: Detlev Fischer
Date: Thu, May 16 2019 12:22AM
Subject: Re: links to the page they are on
← Previous message | No next message

One example where current page of main nav is not linked in site wide navigation is https://accessuse.eu/en/ <https://accessuse.eu/en/>

> Am 15.05.2019 um 23:48 schrieb cb < = EMAIL ADDRESS REMOVED = >:
>
> Does anybody know of a site we could look at now that takes this approach,
> neutering the link to the current page in sitewide navigation? I've been
> looking for examples and have come up empty.
>
> Caroline
>
> On Mon, May 13, 2019 at 4:12 PM Birkir R. Gunnarsson <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> This is where aria-current="page" would be handy, jut put it on the
>> link and the screen reader will announce "current page".
>> If there are visual cues that the links point to the current page yu
>> can make it a WCAG 1.1.1 or 1.3.1 requirement (1.1.1 if it is an icon,
>> 1.3.1 if it is communicated through styling or formatting), that, or
>> that the links be neutered by removing their href attributes, but if
>> not it's a screen reader usability recommendation.
>>
>>
>>
>> On 5/13/19, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>>> Hello:
>>> Let me clarify a little. I have no issue with same-page links. All the
>>> aforementioned reasons I agree with and would always encourage.
>>>
>>> I'm talking about those links that, when clicked, only refresh the page
>> you
>>> are on. So, for example, you are reading an article about the health care
>>> system, and in the body of the article there is a link to the article,
>> and
>>> in the "Recently posted" footer of the article, there is a link to the
>>> article, and in the menu there is also is a link to the article. Each of
>>> these links will refresh the page and sometimes just go back to the top
>> of
>>> the page, and then the user wonders why the link did not work.
>>>
>>> Thanks,
>>> Lucy
>>>
>>> Lucia Greco
>>> Web Accessibility Evangelist
>>> IST - Architecture, Platforms, and Integration
>>> University of California, Berkeley
>>> (510) 289-6008 skype: lucia1-greco
>>> http://webaccess.berkeley.edu
>>> Follow me on twitter @accessaces
>>>
>>>
>>>
>>> On Sat, May 11, 2019 at 8:21 AM Wolfgang Berndorfer <
>>> = EMAIL ADDRESS REMOVED = > wrote:
>>>
>>>> I think, In-side links can improve usability not only for people with
>>>> cognitive disabilities. TOC and footmarks have already been mentioned.
>>>>
>>>> What more? Reading a web side is not like reading a novel from the
>>>> beginning
>>>> to the end. When I seek information on a side, I first try to get an
>>>> overview by checking available headings. If the heading text seems
>>>> helpful,
>>>> I read the subcontent. This strategy is helpful for all and highly
>>>> recommendable for people, who use screen readers, like me.
>>>>
>>>> If in the subcontent I inquire, topics are contained, which already have
>>>> been discussed on the same side, it's very helpful, when they are
>> linked.
>>>>
>>>> Complementary:
>>>> a) Metainfos for links like In-Side-Links have lately been discussed
>> here
>>>> under the thread "Meta Infos necessary in links". (Sorry: Didn't find
>> any
>>>> direct online resource on webaim for the thread.).
>>>> b) UX is not the same as usability. The user experience is too often bad
>>>> usability. No helpful headings …
>>>> Wolfgang
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im
>> Auftrag
>>>> von James A.
>>>> Gesendet: Samstag, 11. Mai 2019 09:22
>>>> An: WebAIM Discussion List
>>>> Betreff: Re: [WebAIM] links to the page they are on
>>>>
>>>> Hi Lucy
>>>>
>>>> In-page links can be useful in some cases for people with cognitive
>>>> disabilities. For example, table of contents and links to sections can
>>>> help
>>>> with orientating users and avoid unnecessary reading. The problem can
>>>> occur
>>>> if there is no means of returning to the original location on the page.
>>>> The
>>>> UK government website uses this approach well eg
>>>>
>>>>
>> https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-web
>>>> sites-and-apps#contents
>>>> <
>> https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps#contents
>>>
>>>>
>>>> Another useful use case for many users is when there is a footnote, for
>>>> example to small print or terms and conditions which are frequently
>>>> indicated by *.
>>>>
>>>> I consider that 2.4.4 Links Purpose covers the need to ensure all users
>>>> understand the purpose of the link is to move within the page.
>>>>
>>>> Best wishes
>>>>
>>>> Abi James
>>>>
>>>> University of Southampton
>>>> Abilitynet & British Dyslexia Association
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On 11 May 2019, at 01:09, Patrick H. Lauke
>>>> < = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >> wrote:
>>>>
>>>> On 11/05/2019 01:06, Lucy Greco wrote:
>>>> thanks for the quick reply so the cognative working group did not
>> think
>>>> this was a problem? interesting
>>>>
>>>> I can't speak for the group, but I can say that they did not put forward
>>>> any
>>>> SCs that made it into WCAG concerning this particular issue.
>>>>
>>>> P
>>>> --
>>>> Patrick H. Lauke
>>>>
>>>>
>>>>
>> https://eur03.safelinks.protection.outlook.com/?url=www.splintered.co.uk&amp
>>>> ;data
%7C01%7Ca.james%40soton.ac.uk
>>>> %7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4
>>>>
>>>>
>> a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=ZTVr2mbqr%2Fs2TF3u%2BlC0vBX93%
>>>> 2FpOIyc1spISAjpY8DM%3D&amp;reserved=0 |
>>>>
>>>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com
>>>> %2Fpatrickhlauke&amp;data
%7C01%7Ca.james%40soton.ac.uk
>>>> %7C5cc6c5ac52a148f4
>>>>
>>>>
>> bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2BvC2MLAM
>>>> yvuPCM5k92qrljVb8IKQrSrAHOdYKPoUBEQ%3D&amp;reserved=0
>>>>
>>>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%
>>>>
>>>> 2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a14
>>>>
>>>>
>> 8f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4v
>>>> yEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
>>>> <
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Dploz4vyEj%2BgzRa4Bf%2Bcoj74%2FspIYqDnD93J2xOIMCY%3D&amp;reserved=0
>>>
>>>> |
>>>>
>>>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.devia
>>>>
>>>> ntart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a148f4bfc408d
>>>>
>>>>
>> 6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%
>>>> 2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
>>>> <
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=MeVMveX2np8Abayy%2FWzEv844DnAbZ0D3AABPWafJB5E%3D&amp;reserved=0
>>>
>>>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>>> >>>> >>>>
>>>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim
>>>>
>>>> .org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac52a148f4bfc408d6d
>>>>
>>>>
>> 5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiq
>>>> KpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
>>>> <
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist.webaim.org%2F&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Pd7BO%2FTgArmqGVWiqKpFysfvZT2n4veRtNakm5A9hFE%3D&amp;reserved=0
>>>
>>>> List archives at
>>>>
>>>>
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%
>>>>
>>>> 2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk
>> %7C5cc6c5ac5
>>>>
>>>>
>> 2a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMl
>>>> tgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
>>>> <
>> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebaim.org%2Fdiscussion%2Farchives&amp;data
%7C01%7Ca.james%40soton.ac.uk%7C5cc6c5ac52a148f4bfc408d6d5a4e97f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=EMltgqPRJGLvHSqNCcq%2BuDRtEi11uTiqp%2BppBMEVZDc%3D&amp;reserved=0
>>>
>>>> >>>> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>>>> >>>> >>>> >>>> >>>>
>>>> >>>> >>>> >>>> >>>>
>>> >>> >>> >>> >>>
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> >> >>
> > > >