RE: JQuery-UI Calendar widget accessibility

Our group decision was that the APG will be much more broadly valuable and
maintainable if all the examples are vanilla JS/CSS/HTML without external
dependencies.

 

As our work on the APG is progressing and the number of examples needed to
express the various ways of implementing each pattern is growing, I am
increasingly seeing how important this decision is. For example, it is also
preventing the APG from becoming bloated and difficult to consume. Further,
the working group is taking responsibility for maintaining these examples,
so including multiple flavors of a single pattern that differ only in their
dependency trees is not a recipe for sustainability.

 

There are lots of other places where developers of various JS libs can
host/share/promote their various implementations of what is recommended in
the APG.

 

I encourage widget developers to seek feedback on their implementation of
best practice. But, I don't think we should add examples that have
dependencies on external js libs to the APG.

 

Matt King

 

From: Gunderson, Jon R [mailto:jongund@illinois.edu] 
Sent: Friday, January 29, 2016 1:00 PM
To: John Foliot <john.foliot@deque.com>; 'Bryan Garaventa'
<bryan.garaventa@ssbbartgroup.com>; 'Matt King' <mck@fb.com>; 'James
Nurthen' <james.nurthen@oracle.com>
Cc: 'ARIA Working Group' <public-aria@w3.org>
Subject: RE: JQuery-UI Calendar widget accessibility 

 

I am working the designer of the development version of the new JQuery Date
Picker and Calendar Widget on accessibility.

 

He is very interested in getting the feedback of the group on the keyboard
model and aria roles that could be used for the calendar widget since it is
under active development and is an entirely new code base from the current
publicly available JQuery-UI date picker widget.

 

When I mentioned potentially using an accessible version of the calendar
widget as an example in the APG he seemed to be honored by the idea, but I
will double check with him.

 

Jon Gunderson

 

 

From: John Foliot [mailto:john.foliot@deque.com] 
Sent: Friday, January 29, 2016 2:34 PM
To: 'Bryan Garaventa' <bryan.garaventa@ssbbartgroup.com
<mailto:bryan.garaventa@ssbbartgroup.com> >; Gunderson, Jon R
<jongund@illinois.edu <mailto:jongund@illinois.edu> >; 'Matt King'
<mck@fb.com <mailto:mck@fb.com> >; 'James Nurthen' <james.nurthen@oracle.com
<mailto:james.nurthen@oracle.com> >
Cc: 'ARIA Working Group' <public-aria@w3.org <mailto:public-aria@w3.org> >
Subject: RE: JQuery-UI Calendar widget accessibility 

 

Bryan Garaventa wrote:
>

> If we are going to be including jQuery UI examples within the APG, are we
also
> allowing other APIs too if provably accessible?

 

Good question Bryan, and I'll also add that the W3C should ensure we have
JQuery's permission (or at least awareness) before using their code as
examples in our documentation. While JQuery is licensed under the MIT
License (https://jquery.org/license/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__jquery.org_license_&d=
BQMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yA
I&m=H5drAB_Gs9ORcDNoU7cKmncI1Qtc0gqwXzWMectXhxI&s=Ti5G_AO17GWIk8MX7yNM-prmWZ
hs8UeCyoG9Wh5vYVE&e=> ) it seems it would be, if nothing else, *polite* to
have that discussion to let them know of our intent, and steps MUST be taken
(if we do this) to respect the MIT license, including providing the original
copyright and license notice in any copy of the software/source we use.

 

JF

 

From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
Sent: Friday, January 29, 2016 2:01 PM
To: Gunderson, Jon R <jongund@illinois.edu <mailto:jongund@illinois.edu> >;
Matt King <mck@fb.com <mailto:mck@fb.com> >; James Nurthen
(james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> )
<james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >
Cc: ARIA Working Group <public-aria@w3.org <mailto:public-aria@w3.org> >
Subject: RE: JQuery-UI Calendar widget accessibility 

 

> When it is closer to ready, yes . but not in its current state.

 

If we are going to be including jQuery UI examples within the APG, are we
also allowing other APIs too if provably accessible?

 

Also there should be no requirement that a calendar can only consist of a
Grid.

 

 

From: Gunderson, Jon R [mailto:jongund@illinois.edu] 
Sent: Friday, January 29, 2016 11:51 AM
To: Matt King <mck@fb.com <mailto:mck@fb.com> >; James Nurthen
(james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> )
<james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >
Cc: ARIA Working Group <public-aria@w3.org <mailto:public-aria@w3.org> >
Subject: RE: JQuery-UI Calendar widget accessibility 

 

Matt,

 

Felix one of the developers for the calendar widget would like input on the
accessibility design specifications before they start implementing the
accessibility features.

 

They know it is not accessible now, but would like design specifications on
what they should do.

 

I will take the APA groups comments and enter them in to the design wiki so
they know what to do.

 

Jon

 

 

From: Matt King [mailto:mck@fb.com] 
Sent: Friday, January 29, 2016 1:28 PM
To: Gunderson, Jon R <jongund@illinois.edu <mailto:jongund@illinois.edu> >;
James Nurthen (james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> )
<james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >
Cc: ARIA Working Group <public-aria@w3.org <mailto:public-aria@w3.org> >
Subject: RE: JQuery-UI Calendar widget accessibility 

 

John,

 

When it is closer to ready, yes . but not in its current state.

 

I did a quick test with JAWS and NVDA in Firefox. I am not sure where focus
is going on tab, but tabing through is completely silent with both.

 

It is not possible to close the window with the keyboard; the JS is eating
all keys.

 

The grid markup looks decent, but the grids need to be labeled.

 

The button markup in the grid is good.

 

I am happy to give it another go when you have some fixes.

 

Matt

 

 

From: Gunderson, Jon R [mailto:jongund@illinois.edu] 
Sent: Friday, January 29, 2016 8:42 AM
To: Matt King <mck@fb.com <mailto:mck@fb.com> >; James Nurthen
(james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> )
<james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> >
Cc: ARIA Working Group <public-aria@w3.org <mailto:public-aria@w3.org> >
Subject: JQuery-UI Calendar widget accessibility 

 

Matt and James,

 

Could we spend some time reviewing a new calendar widget (e.g. multiple
months in one dialog box) from the JQUery-UI team.

http://view.jqueryui.com/datepicker/demos/calendar/multiple-months.html
<https://urldefense.proofpoint.com/v2/url?u=http-3A__view.jqueryui.com_datep
icker_demos_calendar_multiple-2Dmonths.html&d=CwMFAg&c=5VD0RTtNlTh3ycd41b3MU
w&r=O5KcpICX8LHGtRJi41yDlw&m=hxqSKzBTF1A5XxccXnYvltGsuwNoKd30EPUYmhSMquI&s=-
ldWSz3hXMnrGR9rcRtZSKilQ_8QgStlY-H_CFsEYPs&e=>  

 

They have asked for some accessibility feedback and I would like to get some
feedback on the roles and keyboard model for this composite widget.

 

It would be a good example to include in the authoring practices guide of a
complex widget.

 

Jon

 

 

Jon Gunderson, Ph.D.

Coordinator of IT Accessibility

Disability Resources and Education Services

University of Illinois at Urbana-Champaign

 

E-mail: jongund@illinois.edu <mailto:jongund@illinois.edu>