Re: Fixed headers (was: accessibility support for low vision)

> I was pondering a way of saying that: if an element is fixed in the
viewport and takes up more than 30% of the viewport, then it counts as a
‘loss of content

Maybe in the normative definition of "loss of content"???

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Wed, Jul 19, 2017 at 7:20 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> There is one potential issue that I’ve been mulling how to address, but
> not worked it out yet.
>
>
>
> From testing various sites, if a site is using responsive design the 400%
> (320px) level it is generally fine for the zoom SC, but there are two
> somewhat common issues I’ve come across in the last couple of months:
>
>
>
>    1. A huge, fixed header area. Wayne mentioned this, it comes from
>    developers not considering that the 320px *width* breakpoint can have
>    a very short *height*. It is easy to fix: unstick the header. (Getting
>    them to test with zoom is usually enough to motivate that fix.)
>
>    2. Removing functionality at the smaller sizes so that it isn’t
>    available at all.
>
>
> I think the second is covered (especially with the new amendment to the
> note yesterday), but the first is not covered in a black and white way.
>
>
>
> I was pondering a way of saying that: if an element is fixed in the
> viewport and takes up more than 30% of the viewport, then it counts as a
> ‘loss of content’.
>
>
>
> The zoom SC [1] is wordy already (including the notes), is this something
> that could be tackled in the understanding?
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
> 1] https://rawgit.com/w3c/wcag21/resize-content_ISSUE-77/
> guidelines/sc/21/resize-content.html
>
>
>