E-mail List Archives
Re: Lift Assistive
From: Sean Murphy
Date: Feb 11, 2016 11:57PM
- Next message: _mallory: "Re: Activating controls with hidden accessible names using speech recognition"
- Previous message: Jonathan Avila: "Re: How were the WCAG contrast ratios determined"
- Next message in Thread: None
- Previous message in Thread: Maxability Accessibility for all: "Re: Lift Assistive"
- View all messages in this Thread
Text only is old school thinking and is really only focusing at a sub-section of the disability community. I suspect it was more geared towards screen reader users. Any site that has dedicated pages for accessibility isn't following best practises and costing themselves more money.
Sean
> On 12 Feb 2016, at 1:25 pm, Maxability Accessibility for all < <EMAIL REMOVED> > wrote:
>
> <its tools like this i think make our job harder. we keep telling people we
> need to code to standereds and then some one comes in and says our tool
> will do what you need make an accessable vertion well i say stop now and
> just code to the standers you will get better web sites and more access for
> every one not only people with disabilitys.>
>
> I second this. Just code to the standards.
>
> On Thu, Feb 11, 2016 at 1:38 AM, Don Mauck < <EMAIL REMOVED> > wrote:
>
>> Couldn't agree more! We had older architecture that required
>> Accessibility settings. Our position now is that we expect products to
>> stop using that and code to the standards. If we do that, shouldn't need
>> any special settings, customers hate it.
>>
- Next message: _mallory: "Re: Activating controls with hidden accessible names using speech recognition"
- Previous message: Jonathan Avila: "Re: How were the WCAG contrast ratios determined"
- Next message in Thread: None
- Previous message in Thread: Maxability Accessibility for all: "Re: Lift Assistive"
- View all messages in this Thread