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.<p>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.<p>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.<p>Interestingly enough you rarely see website/webapps that utilises the fact that most users are on wide-screen monitors (mobile excluded).
And here's a chrome extension that disables static headers, for us who dislike them / low res devices / zoomed pages.<p><a href="https://chrome.google.com/webstore/detail/fix-fixed/fmekfmdhojjdlffigjlnbfkmjjncfkde" rel="nofollow">https://chrome.google.com/webstore/detail/fix-fixed/fmekfmdh...</a><p>I mean, nice for your plugin for those who like it. I just found this a bit relevant.
Does this help the disabled? If not, it's 'user experience', not accessibility.<p>> Accessibility refers to the design of products, devices, services, or environments for people who experience disabilities.
Oh! for a second I thought this was an "official" feature release. Not an improvement IMHO.<p>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.
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.<p>(that said, I realise you can't apply these styles to iOS anyway, it is a mute point).