WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: resize text SC 1.4.4

for

From: Mallory
Date: Apr 10, 2017 6:58AM

Only a Note:
Chrome support for Dragon is spotty and now the plugin in FF doesn't
work.
With Dragon I'm pretty much IE only currently. I know that's Nuance's
fault
but there are times where users are either going to need to view
something
on two browsers because of (lack of) support or rely on a single
browser.

Yes, browsers can be updated cost-free, but everything you need still
needs
to work with them. I was stuck on IE9 until I could cough up 80 euros
for my
ZoomText upgrade.

cheers,
_mallory


On Sun, Apr 9, 2017, at 04:51 PM, Birkir R. Gunnarsson wrote:
> Unless you are producing content that can only be exclusively accessed
> in a closed environment, where e.g. Firefox is not availalbe for
> download, that argument does not really apply, see the definition of
> accessibility supported
> http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html
> )if the content works in one widely support user agent available for
> download or does not cost a person with a disability any more than a
> person without, both are true for Firefox and Chrome, although Chrome
> has spotty accessibility support).
> Users are able to update mainstream browsers are little to no cost,
> and there are many reasons why they should which have nothing to do
> with accessibility (e.g. security).
> As long as your content is coded according to standard and works with
> a mainstream agent at least 1 or 2 versions back (I go with 2), you
> should be fine. Requiring that your web content works with IE 6 or
> Jaws 9 is not an matter of accessibility conformance, as long as NVDA
> and Firefox are available to the user.
>
>
>
> On 4/7/17, Katie Haritos-Shea < <EMAIL REMOVED> > wrote:
> > Thanks for that update Patrick!
> >
> > Katie Haritos-Shea
> > 703-371-5545
> >
> > On Apr 7, 2017 6:06 PM, "Patrick H. Lauke" < <EMAIL REMOVED> > wrote:
> >
> >> On 07/04/2017 21:37, Katie Haritos-Shea GMAIL wrote:
> >>
> >>> Browser zoom may not work in *all* cases, especially in the case of
> >>> mobile content. Keep in mind that for mobile devices, content that
> >>> developers have built for mobile web content/sites can put *constraints*
> >>> on
> >>> the ability for content to zoom and the viewport size. So you still need
> >>> to
> >>> test and keep a watch on that.
> >>>
> >>
> >> With a follow-up that recent versions of iOS/Safari, as well as Windows 10
> >> Mobile/Edge, now ignore any meta viewport restrictions that stop users
> >> from
> >> zooming by default. Other current mobile browsers have a user setting for
> >> users to explicitly override this (Windows Phone 8 in OS settings > ease
> >> of
> >> access > allow zooming on all web content; Chrome settings > Accessibility
> >> > Force enable zoom; Opera settings > Force enable zoom; Firefox settings
> >> > >
> >> Accessibility > Always enable zoom; Samsung Internet settings > Manual
> >> zoom).
> >>
> >> But yes, for older mobile browsers (e.g. older versions of iOS, old
> >> Android/Browser, etc) still relevant advice.
> >>
> >> 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
> >> > >> > >> > >> > >>
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > >