Re: Linearization

I support the Linearization SC understanding that we might have to re scope
it to blocks of text if it can't be solved for all content by final draft.

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 Thu, Feb 16, 2017 at 3:44 PM, Wayne Dick <wayneedick@gmail.com> wrote:

> As Micheal Cooper put it in a WCAG meeting. Responsive design is an
> authoring technique, not an assistive technology.
>
> Translation: Authors can write code so that it can be linearized.
>
> Linearization is a web content issue, and it is dealt with in mainstream
> web development every day.
>
> When we test current pages many will fail. That is OK. Many pages fail
> today.
>
> It will take time to develop tools, identify all the failures but this is
> a problem that the mainstream solved for us when they moved 22 inch
> landscape pages to 4.7 inch portrait mobile pages. It is time to ask
> authors to give people with low vision what they give to others on mobile.
>
> Will it take work on the part of developers? Yes it will, but consider the
> 3,000,000 people with LV in the US. If each one read one page a day that
> would be 40 scrolls to overcome lack of word wrapping. If each scroll took
> 1 second that would be 120,000,000 seconds. That would be 2,000,000 minutes
> or 3.8 years. Our time counts too.
>
>
>
>
>
>