WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL] Doubts regarding website logo


From: Mark Magennis
Date: Aug 17, 2020 10:58AM

Hi Bobby,

I'm not sure I understand why having a logo as the H1 breaks accessibility. It seems like the obvious choice to me.

For example, suppose you have a website of a company called The Company. The home page has a 'The Company' logo at the top. What should be the main heading of this page?

It's the home page but you're not going to put a heading 'Home' on it. It probably doesn't have any visible title that could sensibly be used as the page heading. The sensible choice for the home page title and therefore the H1 is usually 'The Company'.

You already have a logo which contains the words "The Company" and the text alternative of that is "The Company", so rather than add another heading, doesn't make sense to use that?

But you don't want to do this on any page other than the home page because other pages need a unique title specific to their content. This means you end up with some inconsistency - on other pages the logo is only a link. But I don't think that's a problem at all.


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of bobby accessibility
Sent: 17 August 2020 09:41
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] Doubts regarding website logo

Dear Vaibhav,

Choosing a logo as heading or H1 should not be a wise decision and it will break accessibility specially for UX..

I will suggest following acceptance criteria for logo:

1. It should be announced with a graphic logo (link or button) I will prefer to announce this as a link 2. Exemptions for Color contrast for logo no need to worry if contrast ratio is below 4.5:1.
3.It should be consistent all across the application.as move with top navigation.

Hope this helps.


On Sun, Aug 16, 2020 at 10:29 PM Vaibhav Saraf < <EMAIL REMOVED> >

> Hi Patrick,
> Thanks for sharing your point of view.
> The logo is identified on all the pages as a link but one page where
> it is a button. Yes it might not be right to classify it as a failure
> of consistent identification but it is deviating from the standard use
> of a button.
> Thanks,
> Vaibhav
> On Sun, 16 Aug 2020 at 02:16, Patrick H. Lauke
> wrote:
> > On 15/08/2020 17:19, Vaibhav Saraf wrote:
> > > Hi Everyone,
> > >
> > > I was auditing a website where on the login page they had
> > > programmed
> the
> > > logo to be a button and a heading level 1.
> > >
> > > On all other pages the logo was programmed as a button so I had
> > > failed
> it
> > > for coonsistent identification.
> >
> > Consistent identification wouldn't be quite the right SC in any case.
> > It's more about consistently identifying (in text/name) the same
> > control/functionality the same way across pages, not that there's
> > some consistency (of roles or whatever) between similar controls on
> > the same page.
> >
> > > But I had this particular doubt for treating the logo as a <h1>,
> > > after login for a specific group the website redirects to one
> > > deployed on a sub-domain, on all of the pages in the sub-domain
> > > the logo is marked as <h1>.
> >
> > It's fine as long as it's consistent. Some folks like logos as
> > <h1>s, others don't. What matters more is that it's
> > predictable/implemented the same way across all pages, so once an AT
> > user understands that that's the convention on that site, there's no further surprises for them.
> >
> > P
> > --
> > Patrick H. Lauke
> >
> > https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> > https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> > twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
> > > archives at http://webaim.org/discussion/archives
> >