W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: Is Java Web Start covered by WCAG?

From: John Foliot <john.foliot@deque.com>
Date: Wed, 26 Apr 2017 15:35:56 -0500
Message-ID: <CAKdCpxw3QWZntXvy2f7UnYtTJJafXKQqU4uopu5xwJQ7ssdt_Q@mail.gmail.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: Gregg Vanderheiden RTF <gregg@raisingthefloor.org>, James Nurthen <james.nurthen@oracle.com>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Hi all,


content (Web content)

information and sensory experience to be communicated to the user by means
of a user agent <https://www.w3.org/TR/WCAG20/#useragentdef>, including
code or markup that defines the content's structure
<https://www.w3.org/TR/WCAG20/#structuredef>, presentation
<https://www.w3.org/TR/WCAG20/#presentationdef>, and interactions

user agent

any software that retrieves and presents Web content for users

*Example: *Web browsers, media players, plug-ins, and other programs —
including assistive technologies <https://www.w3.org/TR/WCAG20/#atdef> —
that help in retrieving, rendering, and interacting with Web content.

If when it is run it uses HTTP to get its content

Hmmm... while in principle I tend to agree with this sentiment (along with
the addition of HTTPS), that is not part of the
definition, and I would argue, rightfully so.

In theory, a PDF attached to an email could/would still be 'governed' by
WCAG 2.0 (especially given how much extra WCAG 2.0.stuff - Techniques,
etc., are PDF-focused), yet that email would not necessarily be using the
HTTP protocol.

PhoneGap wraps web content that uses HTTP.  So does that make PhoneGap a
user agent?

Per the definitions above, I would argue yes. The goal of PhoneGap is/was
to allow developers to write their applications using the standard
HTML/CSS/JavaScript stack, and then place that 'application' inside of a
wrapper to emulate a native application (http://phonegap.com/).

Since the developer / content-author is using basic web technologies, I
would argue then that WCAG applies to PhoneGapped apps as well (or at
least, it should), as PhoneGap is, in effect, the user-agent. (Q: isn't
part of the work of the MATF also looking at accessibility of native apps

> (is)
Java Web Start is covered by WCAG
​ [JamesN]​
said, "The application is started from
a URL and the application is downloaded, installed updated and run
directly when clicking on a URL in a web page."

Web Start programs are no longer an integrated part of the web page, they
are independent applications that run in a separate frame.

Programmers often speak of the *Java Network Launching Protocol* (*JNLP*)
interchangeably with the term "Web Start". The JNLP protocol, defined with
an XML <https://en.wikipedia.org/wiki/XML> schema, specifies how to launch
Java Web Start applications.

JNLP works in a similar fashion to how HTTP/HTML works for the web. For
rendering <https://en.wikipedia.org/wiki/Web_browser_engine> an HTML webpage
<https://en.wikipedia.org/wiki/Webpage>, after the user clicks on a
weblink, the browser submits a URL to a webserver
<https://en.wikipedia.org/wiki/Webserver>, which replies with an HTML file.
The browser then requests the resources referred to by this file (images,
css <https://en.wikipedia.org/wiki/Cascading_style_sheets>), and finally
renders the page once it has received enough information. Page rendering
usually starts before all resources have downloaded; some resources not
critical to the layout of the page (such as images) can follow on

JNLP mirrors this process; in the same way that a Web browser renders a
webpage, a JNLP client "renders" a Java app
<https://en.wikipedia.org/wiki/Java_application>. After the user clicks on
a weblink, the browser submits an URL to a webserver, which replies with a
JNLP file (instead of a HTML file) for the application. The JNLP client
parses this file, requests the resources specified (jar files), waits for
the retrieval of all required resources, and then launches the application.
The JNLP file can list resources as "lazy", which informs the JNLP client
that the application does not need those resources to start, but can
retrieve them later on when/if the application requests them.

Asking about Web Start is, to me, asking the wrong question. If Web Start
is used to transport and then launch a User Interface-based application or
content​, I'd argue that yes, it is in scope in the same way that PDF is in
scope. But that's just me, and I think James is correct in asking for a
definitive 'ruling' here. I'd vote Yes, content delivered via Web Start
should be WCAG compliant as well.



On Wed, Apr 26, 2017 at 2:57 PM, Laura Carlson <laura.lee.carlson@gmail.com>

> I can't tell either. James?
> On 4/26/17, Gregg Vanderheiden RTF <gregg@raisingthefloor.org> wrote:
> > Can't quite tell from your description. If it is downloaded and
> > installed and then run it is not the web application.
> >
> > If when it is run it uses HTTP to get its content then it is web
> > content. What is download it is simply a special user agent.
> >
> > From your description it isn't quite clear which of the two cases it is
> >
> > Gregg
> >
> >
> >
> >> On Apr 26, 2017, at 8:45 PM, Laura Carlson <laura.lee.carlson@gmail.com
> >
> >> wrote:
> >>
> >> Hello Everyone,
> >>
> >> James asked on Oracle's Adapting Text comment [1] if Java Web Start
> >> [2] [3] is covered by WCAG.  He said, "The application is started from
> >> a URL and the application is downloaded, installed updated and run
> >> directly when clicking on a URL in a web page."
> >>
> >> Thoughts?
> >>
> >> Thank you.
> >>
> >> Kindest Regards,
> >> Laura
> >>
> >> [1] https://github.com/w3c/wcag21/issues/222#issuecomment-297476165
> >> [2] https://en.wikipedia.org/wiki/Java_Web_Start
> >> [3] https://www.java.com/en/download/faq/java_webstart.xml
> >>
> >> --
> >> Laura L. Carlson
> >>
> >
> --
> Laura L. Carlson

John Foliot
Principal Accessibility Strategist
Deque Systems Inc.

Advancing the mission of digital accessibility and inclusion
Received on Wednesday, 26 April 2017 20:36:32 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:12 UTC