Carolyn MacLeod

Noticed that the [APG example code for region landmark](http://w3c.github.io/aria-practices/examples/landmarks/region.html) includes the following HTML Technique: ```html title for region area 1 ... content for region area 1 ... ``` Perhaps this...

Note that the current [html spec for main element](https://html.spec.whatwg.org/multipage/grouping-content.html#the-main-element) is a bit different from the (old) W3C spec. You can still only have one visible main element: > A document...

@matatk Issue https://github.com/matatk/landmarks/issues/370 is a great example of where linting would be useful/helpful. :) I like your updated idea of exposing some icons in the pop-up. Maybe (for issue 370...

Sounds great, @matatk! Re: > I'll need to think about whether these errors/warnings should be presented to the end-user (given there's nothing they can do about them) Oh, right. My...

> Lack of a main region? Absolutely, flag lack of a main region, mostly because main is the most important landmark, but also if there's, say, a header and a...

@matatk After you [add linting support](https://github.com/matatk/landmarks/issues/182), maybe it would be ok for Landmarks to "support" [multiple](https://github.com/matatk/landmarks/blob/9ccf0c2bfa57afb18953db9569afafdd46e7c2bf/src/code/landmarksFinder.js#L161) [mains](https://github.com/matatk/landmarks/blob/9ccf0c2bfa57afb18953db9569afafdd46e7c2bf/src/code/landmarksFinder.js#L381) even though it is invalid? This would be in line with what browsers...

> Do you think the 'skip to main' shortcut should cycle between all discovered main regions, rather than only going to the first? Good question. If JAWS cycles, maybe Landmarks...

> However, I might be able to do pretty quickly is at least include the landmarks from other frames in the GUIs, separately from the landmarks for the main page—then...

Yes, I can still reproduce it (just tried in Chrome & FF on Win), but not when there's a vertical scrollbar (which is what happens when I open DevTools because...

Nice sleuthing! I wonder if this bit about maybe using pageXoffset and pageYoffset instead of scrollX and scrollY is useful? https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect#cross-browser_fallback (probably not helpful, but thought I'd mention noticing it)