WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Icon-only buttons

for

From: Mark Magennis
Date: Jan 21, 2022 4:37AM

I don't think you need the button Pat. You just need to include the icon within the link. Something like this:

<p>For more information, please visit the <a href="xxx">website of the Information Commissioner <img alt="opens in a new tab"></a>.</p>

A screen reader will read this as "link website of the Information Commissioner opens in a new tab".

Mark

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Pat Reynolds
Sent: 21 January 2022 11:18
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Icon-only buttons

Hi Mark,

For clarification, there would be two links. E.g. if the text / icon is:
"For more information, please visit the website of the Information Commissioner [symbol of arrow popping out of a box]"
Then the words 'the website of the Information Commissioner would be linked to https://ico.org.uk and the symbol would be on a button, also linked to https://ico.org.uk/, and the button would also have the ialt text that it is a link to an external site.

How this would appear at the moment (which is not as good, in my opinions
is:
"For more information, please visit the website of the Information Commissioner (link opens in a new tab)" with the words 'the website of the Information Commissioner would be linked to https://ico.org.uk

But maybe in reading order the button needs to be first, and include the url of the website, so that the person using a screen reader hears the relevant information directly after "For more information, please visit".

With thanks,

Pat
<https://ico.org.uk/>

*- -*

*Dr Pat Reynolds*
Executive Director


A Charitable Incorporated Organisation registered in England and Wales, number 1167484 VAT registration: 233 0105 70

*Join us on social:*
[image: : https://www.facebook.com/FreeUKGEN]
https://www.facebook.com/FreeUKGEN <https://twitter.com/FreeUKGen> <https://www.instagram.com/freeukgenealogy/>
<https://www.pinterest.co.uk/FreeUKGenealogy/>
Please read our *Privacy Notice*
<https://www.freeukgenealogy.org.uk/files/Documents/Privacy-Notice.pdf> for information on how we will protect and use your data.

<https://www.easyfundraising.org.uk/causes/freeukgenealogy/?utm_campaign=raise-more>

+44 1723 362616 +44 7943 145387
Westwood House,Westwood, Scarborough YO11 2JD, UK


On Fri, 21 Jan 2022 at 11:08, Mark Magennis < <EMAIL REMOVED> >
wrote:

> Pat,
>
> Having a "link opens in new tab" symbol on a button sounds illogical.
> If it opens a new page then logically it is a link, not a button, and
> should be exposed as a link.
>
> As far as I can tell, this is the view of most accessibility
> specialists - that role should not follow behavior, i.e. if it behaves
> like a button make it a button and if it behaves like a link make it a
> link. But some people disagree and think that role should follow
> appearance. i.e. if it looks like a button make it a button and if it looks like a link make it a link.
> Considering the experience of screen reader users, both views have
> their merits.
>
> Role follows behavior means screen reader users can better guess the
> behavior from hearing the role. Role follows appearance means that
> there is less of a disconnect between the appearance and the announced
> role for partially sighted screen reader users, and also that it is
> less confusing when discussing the UI with sighted colleagues or
> support personnel where you might get an exchange like "try pressing
> the Edit button", "I can't find an edit button, there isn't one. Oh
> wait, there's an edit link, is that what you mean?".
>
> As I said, I think most accessibility folks are in the role follows
> behavior camp but I don't have enough experience of having asked users
> themselves what they prefer to be able to speak for users (apart from
> those who are also accessibility specialists and therefore advanced
> users). Which is a shame because they are the most important judges of the best approach.
>
> Mark
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Pat Reynolds
> Sent: 21 January 2022 10:41
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] [EXTERNAL] Re: Icon-only buttons
>
> Thanks for asking the question, Michael.
>
> This discussion has prompted me to wonder if this is a good solution
> to the issue of how to inform users that a link opens in a new page?
> I personally like the "international" icon that informs sighted users
> that a link will open in a new tab (I have some sight, hand issues, and dyslexia).
> I wonder if the symbol was on a button (also linking to the
> destination) this would be acceptable.
>
> With best wishes,
>
> Pat
> *- -*
>
> *Dr Pat Reynolds*
> Executive Director
>
>
> A Charitable Incorporated Organisation registered in England and
> Wales, number 1167484 VAT registration: 233 0105 70
>
> *Join us on social:*
> [image: : https://www.facebook.com/FreeUKGEN]
> https://www.facebook.com/FreeUKGEN <https://twitter.com/FreeUKGen> <
> https://www.instagram.com/freeukgenealogy/>
> <https://www.pinterest.co.uk/FreeUKGenealogy/>
> Please read our *Privacy Notice*
> <https://www.freeukgenealogy.org.uk/files/Documents/Privacy-Notice.pdf
> > for information on how we will protect and use your data.
>
> <
> https://www.easyfundraising.org.uk/causes/freeukgenealogy/?utm_campaig
> n=raise-more
> >
>
> +44 1723 362616 +44 7943 145387
> Westwood House,Westwood, Scarborough YO11 2JD, UK
>
>
> On Thu, 20 Jan 2022 at 18:41, Michael H < <EMAIL REMOVED> > wrote:
>
> > Interesting conversations! Very helpful!
> >
> > Would it be wise to develop the icon buttons to scale with the text
> > size scale for low vision users?
> > https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html
> >
> > I really appreciate all the informative replies! Thank you everyone.
> >
> > I'm going to run this by my teammates and may be back with a few
> > more questions.
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >