WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Selects with drop downs

for

From: Ryan E. Benson
Date: Mar 15, 2018 7:38PM

> That doesn't work in this context, which was: go ahead and use
HTML/CSS/JS features as per spec, and tough if browsers don't support it,
it's their responsibility. Because you don't control what browser your end
users are using (this is not about purchasing any system)

This is an internal system, so knowing all internal systems must run on IE,
then that issue is solved. If it was public facing, then such issues would
come into play.

--
Ryan E. Benson

On Thu, Mar 15, 2018 at 6:18 AM, Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

> On 15/03/2018 03:13, <EMAIL REMOVED> wrote:
>
>> << all we can do is to diligently file bugs or promote bugs if already
>> filed to keep the issues alive on the vendor's to-do list.>>
>>
>> Definitely, do that.
>> But how about another tactic?
>>
>> Sec. 508 requires the federal government buy accessible software and
>> hardware. Enforce it, especially if you're a government entity or one that
>> is covered by accessibility regulations, such as schools and colleges.
>>
>> Tell the manufacturers why their products will no longer be purchased,
>> that you'll consider them again in the future if they correct their
>> shortcomings.
>>
>> This strategy has worked in the past with other manufacturers in the
>> industry.
>>
>
> That doesn't work in this context, which was: go ahead and use HTML/CSS/JS
> features as per spec, and tough if browsers don't support it, it's their
> responsibility. Because you don't control what browser your end users are
> using (this is not about purchasing any system)...
>
> P
> --
> 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
> > > > >