What accessibility support exists for low vision?

Point taken.  Perhaps we only need to point out is that the landscape break
point should exist always. That would address fixed banners take 3/4 of the
space leaving 1/4 for main.

This is probably a silver issue. The fact still remain that responsive
design (done correctly) makes browser zoom the first accessibility support
for low vision that has existed.

On Wednesday, July 19, 2017, Patrick H. Lauke <redux@splintered.co.uk>
wrote:
> Quickfire comment: why are you inventing a new term "symmetric responsive
design"? Changing browser zoom level changes the browser-internal mapping
of its viewport / pixel density, so the fact that, say, 16px text ends up
rendering as 64px text at 400% is simply a result of the fact that the
browser's viewport mapping (its own CSS pixels to OS pixels) was changed.
It's nothing more than regular responsive design. Adding new terminology
("symmetric", which also isn't really all that understandable/appt to
describe what you're getting at, I'd argue) adds nothing other than an
extra layer of confusion for authors reading the spec.
>
> P
>
> On 19/07/2017 03:27, Wayne Dick wrote:
>>
>> Surprisingly I have a complete answer to this problem. Browser Zoom
>> applied to "symmetric" responsive design.
>>
>> What is symmetric responsive design. Put simply, it is responsive design
>> that responds equally  well to changes in device dimensions as it does
>> to changes in browser zoom level.
>>
>> The general answer is personalization, but for content size symmetric
>> responsive design does it.
>>
>> How precisely does it work:
>>
>> 1. For now assume our base resolution is 1280 by 720 and our font size
>> for running text is 16px. This is the pivot case because it will act
>> like 12pt type on other media and  it divides well by 4. Thus 400%
>> enlargement creates a 320 by 180 screen where the font size of 16px =
>> 64px. That is about the best balance of size and space available for
>> very large print.
>>
>> So, symetric reaponsive design should follow the list of do's and
>> don't's below.
>>
>> Do:
>>
>>   * Use symmetric responsive design
>>   * Make a break point class for resolution 320 by 180
>>   * Use Expand / Collapse to give a users a time based sequence of full
>>     screen interactions with applications
>>   * Use appropriate inline markup
>>     to enable adaptation of text
>>
>> Don't
>>
>>   * Use fixed position banners
>>   * Force the main area to occupy less than 80% of the screen space
>>   * Put controls in the middle of the main page area without an on / off
>>     mechanism
>>   * Put sprites in background images.
>>
>> If an author does this. The standard user agent technology becomes the
>> best assistive technology available for users with low vision to read
>> the web for both passive content and applications.
>>
>>
>> Wayne
>>
>>
>>
>>
>>
>>
>>
>
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>