Re: Linearization

Hi David,

I know you support linearization. I am a lot more optimistic because I do
it every day, and most of the time it works.

Remember, we are not dealing with old pages as much as new pages. It is
relatively easy to design with linearization in mind. There are authoring
techniques to produce pages that can be linearized are seven years old. If
you meet 1.3.2 you are most of the way. If you are responsive you are
there. The CSS docs on flexbox are explicit about meeting 1.3.2. The
framework is good to do this.

There are UI packages that will have to be rethought, but is that much
different than asking people to include keyboard accessibility? It will
take thought.

The add-on nature of 2.1 means that you can meet 2.0 and work your way into
2.1. I think linearization will be low hanging fruit for developers. Once
the get over the angst about having to do it, they will find it easy and
useful.

Stay Accessible, Wayne






On Thu, Feb 16, 2017 at 2:24 PM, David MacDonald <david100@sympatico.ca>
wrote:

> 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 <(613)%20235-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.
>>
>>
>>
>>
>>
>>
>