Show HN: GitHub's Fixed Header for better accessibility | Hacker News Reader

Show HN: GitHub's Fixed Header for better accessibility

gist.github.com

45 pointsamitmerchant26 comments

I'm sorry, but fixed headers are almost always a bad idea, because it make assumptions about the clients that may not be valid. The assumption is that the client has the vertical space for a fixed header.

Even the example is shown for a client that has plenty of vertical space. If the user is on something like a 13" laptop, the fixed header reduces the amount of "usable" space on the page.

Unless you're absolutely sure that the client is on a big monitor, and has a browser window that's higher than it is wide, don't use fixed headers.

Interestingly enough you rarely see website/webapps that utilises the fact that most users are on wide-screen monitors (mobile excluded).

Its optional though.

If you don't want it, don't add it

I guess there's the ability of adding a media query for a certain height so it only shows up on taller screens.

Media Query + min-width fix.

https://gist.github.com/luke3butler/72492aaa68ee9425758ee786...

One other major failing is zooming nearly always breaks fixed headers.

And if the user is on a laptop, they likely have a Home key, making accessing the header one button press away.

It makes more sense on mobile devices where scrolling up can be a pain.

And scrolling down too! In fact scrolling seems to be an anti-pattern for mobile web where touch and swipe are primary interactions. Just sayin'.

They're not all bad. I like sites where the sticky bar hides after scrolling down for a bit and reappears when scrolling up.

And here's a chrome extension that disables static headers, for us who dislike them / low res devices / zoomed pages.

https://chrome.google.com/webstore/detail/fix-fixed/fmekfmdh...

I mean, nice for your plugin for those who like it. I just found this a bit relevant.

Mmm, I'm one that dislikes fixed position headers as they and take up space most times without providing much added value, but perhaps for some that Github more frequently it could be useful to always have the search and top links available. From the title I was expecting something for blind readers of similar.

Also as side note 'static' in CSS actually refers to to elements that stay in their original position within the flow of a document, while 'fixed' means always display it at the same position in the browser window even while scrolling. The spec terminology could be a bit clearer to be honest.

And "absolute" actually means relative (to closest non static ancestor).

I'd normally just use a shortcut to search. I'm used to the `/` key for search (I notice Gmail uses it), but for Github the shortcut is `s`. One that I use a lot for Github is `t` to search for files in a repository.

https://help.github.com/articles/using-keyboard-shortcuts/

Glad to see that I'm not the only one who dislikes static headers.

https://gist.github.com/Jackbennett/0733616c4da282ec8667ff1b...

Here's a version that moves it to the empty sidebars.

This seems wonderful, especially for mobile. A quick search of AMO and google doesn't turn up anything similar for Firefox. Anyone know of a similar Firefox extension?

This works too.

https://alisdair.mcdiarmid.org/kill-sticky-headers/

Does this help the disabled? If not, it's 'user experience', not accessibility.

> Accessibility refers to the design of products, devices, services, or environments for people who experience disabilities.

(nitpick) This isn't accessibility. It's not related to helping the blind/crippled/etc.

Primary Meanings of accessibility:

1. (n) the quality of being at hand when needed 2. (n) the attribute of being easy to meet or deal with

I didn't downvote your comment but in case you're not aware, referring to a disabled person as a cripple can be seen as offensive.

Oh! for a second I thought this was an "official" feature release. Not an improvement IMHO.

But for me this illustrates the "killer app" of browser extensions, that you can customize the sites you use every day and are not dependent on them implementing a certain feature.

It depends on your definition of accessibility I suppose...

Well like Humpty Dumpty when I use a word it means what the first search in google says it means, no more no less https://www.google.com/search?q=accessibility

Better accessibility? Just to note that position fixed with an input element receiving focus will break on iOS. Its a long-standing bug with very few work-arounds.

(that said, I realise you can't apply these styles to iOS anyway, it is a mute point).

Moot point.

https://en.wiktionary.org/wiki/moot_point

To add to the moot point, GitHub uses a separate mobile UI anyway.

Reply on news.ycombinator.com