[Athen] Lift Assistive?

[Sean Keegan]

Hi Rachel,


> If our web resources are created to meet WCAG 2.0 AA (our goal),

> is there a reason to keep our Lift Assistive license?


Short answer - no.

Slightly longer answer - I know some web developers who saw the use of
implementing the Lift Assist tool as a mechanism to serve mobile devices,
etc., but I think if the developer incorporates a responsive design into
the website, then that should address the mobile perspective. I think there
are more tools/solutions that a web developer can incorporate into a site
that largely removes the need for such a solution today.

Take care,
Sean


On Wed, Feb 10, 2016 at 9:57 AM, Thompson, Rachel <rsthompson2 at ua.edu>
wrote:


> Hi, esteemed list.

>

> One of the web decision makers on our campus is asking for opinions on the

> Lift Assistive tool. It has been in use on our campus for a long time as a

> way to produce a text-only version of web pages.

>

> I know text-only does not mean accessible and I think tools like this give

> our web teams the erroneous feeling that content is accessible when it is

> not. I also hate the lack of equity with separate-but-equal approaches.

>

> If our web resources are created to meet WCAG 2.0 AA (our goal), is there

> a reason to keep our Lift Assistive license?

>

> If you have an opinion or have faced similar questions, could you please

> share?

>

> Much obliged,

> Rachel

>

> Dr. Rachel S. Thompson

> Director, Emerging Technology and Accessibility

> Center for Instructional Technology

> University of Alabama

> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list

>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20160210/2d2c218a/attachment.html>