Re: Is Java Web Start covered by WCAG?

>>Ø  that PDF delivered via FTP is in scope...
>This is something the group doesn’t seem to agree on.  I’d like to get
consensus on this as well.  I was told by members of the working group who
were involved during WCAG 2.0’s creation that it was not covered.

The WCAG definition is clear that a "web page is delivered over HTTP" WCAG
applies to web pages...

If we want to widen it for future versions that is another matter... but as
far as clarity, the definition of web page is very clear in the standard.
It says exactly what the working group  intended it to say.





Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Fri, Apr 28, 2017 at 11:44 AM, Detlev Fischer <
detlev.fischer@testkreis.de> wrote:

> > > The Mobile Accessibility Task Force proposals cover both "web"
> content, "web apps" and Native apps
> >
> > I don’t think they have tried to cover native apps (MATF – please
> correct me if you did?!)
>
>
> If memory serves, for of many the SCs that we were initially working on,
> it did not matter whether it would be web or somewhere on the range from
> web to native that Alastair has drawn up. Success Criteria like 3.2.6
> Accidental Activation as well as the proposed #60 Target size, #63 Touch
> with Assistive Technology, #66 Pointer inputs with additional sensors, #67
> Device sensors, 70 Orientation seem to apply to both web and native.
>
> I think we were working under the assumption that we would cover aspects
> that were related to the form factor: small screen, other sensors, (often)
> lack of physical keyboard, and especially touch / gesture interaction. Then
> thankfully Patrick entered the fray and made the point that the desktop /
> mobile distinction is flawed. SCs like Target size that first seemed
> straightforward then really got difficult by having to take into account
> differnet input modalities and the fluidity of responsive web design
> triggered both by viewport sizes AND the UA zoom function.
>
> I join the ranks of those who would like more clarity on the definition of
> (web) content that WCAG 2.1 and future versions will apply to (backed by
> examples).
> WCAG2ICT and EN 301 549 assume that a subset of WCAG can also apply in
> parts to general software (native apps).
>
>
>
>