E-mail List Archives
Thread: Java wasp can comply with WCAG 2.1?
Number of posts in this thread: 3 (In chronological order)
From: JP Jamous
Date: Sat, Jan 12 2019 10:08AM
Subject: Java wasp can comply with WCAG 2.1?
No previous message | Next message →
I agree with Glen. As a developer, I do not foresee any relationship between JS and WCAG. As long as the JS code is creating well structured HTML and executing properly for assistive technology to recognize the client-side code changes, JS is fine to be used.
I think you might be thinking of situations where JS functions fire up but the assistive technology has no idea of that execution. Again as Glen mentioned, you use ARIA to ensure progress messages are being announced by screen readers.
Technically speaking, yes JS can be quite accessible and can create inaccessible modifications client-side if not presented properly. I think you are linking the latter to WCAG.
--------------------
JP Jamous
Senior Digital Accessibility Engineer
E-Mail Me |Join My LinkedIn Network
--------------------
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of glen walker
Sent: Friday, January 11, 2019 1:07 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Java webapp can comply with WCAG 2.1?
It's been a few years since I've written Java and JSP pages, but there are no limitations that I'm aware of. You essentially have an html page, with embedded java scriptlets. Your html can be as accessible as you want, and anything the scriptlet generates is totally up to you. You can provide ARIA properties on non-semantic elements from your Java code just as easily as you can hand-code them in html.
On Fri, Jan 11, 2019 at 1:04 AM Edelényi Zsolt < = EMAIL ADDRESS REMOVED = > wrote:
> Glen,
>
> Thank you for your answer. Yes, I am talking about .jsp. I was told
> that Java has limitations of HTML output, and consequently you cannot
> gerenate HTML pages which comply with WCAG.
>
> I do not know if this is true?
>
> Zsolt
>
> On 2019. 01. 09. 1:02, glen walker wrote:
> > Are you talking about a stand alone java app, or about a web app
> > whose contents are generated by java (such as a .jsp page)?
> >
> > A .jsp page can certainly be accessible. It's just generating html,
> > and
> we
> > know what accessible html should look like.
> >
> > Glen
> > > > > > archives at http://webaim.org/discussion/archives
> > > > > archives at http://webaim.org/discussion/archives
> >
From: Patrick H. Lauke
Date: Sat, Jan 12 2019 11:14AM
Subject: Re: Java wasp can comply with WCAG 2.1?
← Previous message | Next message →
On 12/01/2019 17:08, JP Jamous wrote:
> I agree with Glen. As a developer, I do not foresee any relationship between JS and WCAG. As long as the JS code is creating well structured HTML and executing properly for assistive technology to recognize the client-side code changes, JS is fine to be used.
>
> I think you might be thinking of situations where JS functions fire up but the assistive technology has no idea of that execution. Again as Glen mentioned, you use ARIA to ensure progress messages are being announced by screen readers.
>
> Technically speaking, yes JS can be quite accessible and can create inaccessible modifications client-side if not presented properly. I think you are linking the latter to WCAG.
JP, this was about JSP pages, not JS code rendered client-side...
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
From: JP Jamous
Date: Sat, Jan 12 2019 1:55PM
Subject: Re: Java wasp can comply with WCAG 2.1?
← Previous message | No next message
My apologies Patrick. I did not read the whole thread.
I thought it covered JS executing client-side.
--------------------
JP Jamous
Senior Digital Accessibility Engineer
E-Mail Me |Join My LinkedIn Network
--------------------
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of
Patrick H. Lauke
Sent: Saturday, January 12, 2019 12:14 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [WebAIM] Java wasp can comply with WCAG 2.1?
On 12/01/2019 17:08, JP Jamous wrote:
> I agree with Glen. As a developer, I do not foresee any relationship
between JS and WCAG. As long as the JS code is creating well structured HTML
and executing properly for assistive technology to recognize the client-side
code changes, JS is fine to be used.
>
> I think you might be thinking of situations where JS functions fire up but
the assistive technology has no idea of that execution. Again as Glen
mentioned, you use ARIA to ensure progress messages are being announced by
screen readers.
>
> Technically speaking, yes JS can be quite accessible and can create
inaccessible modifications client-side if not presented properly. I think
you are linking the latter to WCAG.
JP, this was about JSP pages, not JS code rendered client-side...
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
http://webaim.org/discussion/archives