title: What are the implications of using static positioning over absolute when making offscreen content for accessibility?
body: <p>In creating alternatives to visual content to meet WCAG 2.0 guidelines, a common approach is to place an alternate display of content outside of the viewport so that it is readable to assistive technologies, but not present for sighted users.  The most cited examples typically look like: </p>
  
  <pre><code>.offscreen{
    position:absolute;
    left:-9999em;
  }
  </code></pre>
  
  <p>With this approach, it's easy to end up in a situation where you have additional scrollbars on layout containers.  However, if fixed positioning is used it seems to eliminate the problem, as the offscreen content is no longer in the context of its container.  My question is, what are the potential pitfalls of using static positioning for offscreen accessible content?  My initial indication is that a screenreader would treat it the same as content that was positioned otherwise, but I have yet to find an example using static positioning. Am I missing something?</p>