WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Java wasp can comply with WCAG 2.1?

for

From: JP Jamous
Date: Jan 12, 2019 1:55PM

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 REMOVED> > On Behalf Of
Patrick H. Lauke
Sent: Saturday, January 12, 2019 12:14 PM
To: <EMAIL 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