W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

Re: Screen Magnification

From: Gregg Vanderheiden <gregg@raisingthefloor.org>
Date: Mon, 22 Jun 2015 11:55:08 -0500
Cc: Jonathan Avila <jon.avila@ssbbartgroup.com>, IG - WAI Interest Group List list <w3c-wai-ig@w3.org>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
Message-Id: <F0CC6FF1-D81A-4F20-BDBD-29DBE14B26A0@raisingthefloor.org>
To: Dick <wayneedick@gmail.com>
Hi Dick

Yes - the things required for WCAG conformance are enough to allow an assistive technology to do all of the things you describe below.   

If I did it I would have an option to do so in a window alongside of a window that displayed the regular layout. And it would highlight the text on the (regular display) page that was in the other window (the wrapping, large font etc window). 

I don’t think I’ve seen a piece of AT that did this exactly - (someone speak up if they know of one) but it is completely possible if the content follows WCAG.     (Do any of the screen-reader/enlarger programs do this already?  Could one of those be used with speech off?) 


gregg


PS  WCAG is not itself a regulatory body.  
WCAG is a set of guidelines
the WCAG WG is a group of volunteers working on Web Content Access — 
and the W3C is a standards body.
But yes - the Web Content Accessibility Guidelines (WCAG) are being used by other regulatory bodies for access guidance. 

----------------------------------
Gregg Vanderheiden
gregg@raisingthefloor.org




> On Jun 22, 2015, at 11:11 AM, Wayne Dick <wayneedick@gmail.com> wrote:
> 
> ​​
> Hi All,​
> ​+1 for panning. I use it all the time with ZT.
> 
> I do not want to minimize the importance of screen magnification software, or seem ungrateful for that matter.  The problem is that it as the only recognized accessibility support recognized by WCAG, it doesn't leave much professional opportunity for people who are not brilliant. 
> 
> I have a question. Are the accessibility API's robust enough powerful enough to support a software like this.
> 
> Reads the API syntax direction translation of the page content and constructs a linear, word wrapped, enlargeable visible web page with all the content of the original  page. Maybe overlay the original page with this API generated page. We never  change the original page.   I/O would work like speech recognition.  The software would translate the user commands (by mouse or keyboard) into keyboard access for the original page. Are there any barriers in the current API and web security model that would prevent this?
> 
> My guess is that we will have to expand our concept of accessible content, API usage and security sandbox communication to do this, but it could be started for reading.
> 
> I know WCAG WG is a regularity body, not a developer. So proposing new AT is not its purpose.  I just wonder if our current configuration could support something like that.
> 
> Thanks Gregg, I didn't want to sound anti screen magnification. 
> 
> Wayne
Received on Monday, 22 June 2015 16:55:41 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC