regions of a page failure technique

I had an action item to update the proposal for a failure identified in
issue 173

"Failure of 1.3.1 due to regions of a page which are visually distinct,
​​
​and which ​
contain distinct groups of content (headers, footers, navigation bars, main
content, asides) not being programmatically determinable or identified by
text.":

I've added language to ensure these concerns that were raised are exempt.

1) Content that is not distinct visually is not a failure
2) Content that is not distinct  in substance is not a failure
3) Content that only has one or two items is not a failure because it is
not a region (group of content)

I support the technique because it is (1) a common failure of 1.3.1 (2) it
is straight forward to fix (3) I would like to ensure we haven't frozen the
ability to introduce common failures (4) it always was a failure, but
currently it is easy to fix and we want to encourage a culture that allows
blind people to easily find and identify regions

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>