Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jupyter Community Workshop on accessibility #11

Closed
ellisonbg opened this issue Nov 21, 2019 · 112 comments
Closed

Jupyter Community Workshop on accessibility #11

ellisonbg opened this issue Nov 21, 2019 · 112 comments

Comments

@ellisonbg
Copy link
Contributor

There is a new call for proposals for Jupyter Community Workshops:

https://blog.jupyter.org/jupyter-community-workshops-call-for-proposals-for-jan-aug-2020-710f687e30f4

The deadline is 12/15 for the proposal. I think this would be a fantastic way to gather folks who are interested in accessibility and build out a plan. Let's use this issue as a way for folks to express interest in helping to organize and submit the proposal. If you are interested in helping to organize the JCW, please reply to this thread and we will setup a meeting with interested folks to get going on the JCW proposal.

@choldgraf
Copy link
Contributor

I think it's a fantastic idea - I am happy to help out with putting together a proposal

@sinabahram
Copy link

Happy to participate or help in different ways. I would like to be included on calls and such so I can figure out how best to assist. I'm also happy to offer our Zoom pro subscription as an accessible way of conducting meetings, both voice and video if people prefer.

@clapierre
Copy link

The DIAGRAM Center would like to participate and if it makes sense we could help lead this effort. Yesterday, Sina, myself, Volker and a few DIAGRAM Benetech folks got on a call to discuss this idea and we came up with some initial ideas. Sina / Volker please jump in here to add any addition context or clarifications.

Proposal:
3 day event - broken down into
Day 1 - Identifying top-level architectural issues (identifying severity and level of effort to remediate)
Day 2 - Break up into smaller teams to dig into these respective areas
Day 3 - Return as a group and come up with a work plan to address all issues (end result a document which outlines the top level issues to be addressed and potential steps needed to remediate -Note there may be some tasks dependent on others)

We are thinking potentially of having this either the week prior or after CSUN which would be either March 4,5 & 6. Or March 16, 17 & 18. (Note: CSUN is a huge disability conference so those traveling from out of town might potentially be at CSUN the week of March 9-13.)

We felt that having this event in the Bay Area would be ideal due to the proximity to Bloomberg and Berkley. We don't yet have a venue but we might be able to use the LightHouse of the Blind in SanFrancisco again, which is where this initial work on the accessibility of JupyterLab was started earlier this year.

We also discussed who would be required to attend and at a minimum this would be:

Sina Bahram @sinabahram
Volker Sorge @zorkow
James Nurthan (ARIA Expert and W3C WG Chair)
JupyterLab Architectural Expert
PhosporJS Architechural Expert
I think both @jasongrout and @choldgraf would also be a requirement, an possibly someone from Bloomberg?

(What am I missing... @sinabahram @zorkow)
Thanks
Charles LaPierre
Technical Lead DIAGRAM and Born Accessible (Benetech)

@choldgraf
Copy link
Contributor

hey @clapierre and team, thanks for putting this together!

I am happy to help writing a proposal like this, it sounds like a good group of "minimum necessary" people in the room to me. Perhaps if we any developers are available to put sustained cycles into it (e.g. if we can raise some $$$ at Berkeley) then they should be there too. I'd weight @jasongrout higher than me in terms of the value for this meeting as I'm fairly unfamiliar with JupyterLab tech, but unless I'm out of town for the dates for some reason, I'll certainly come to the meeting.

We might be able to use some space at UC Berkeley for this meet-up in a pinch, though it's a bit out of the way if you're coming from SF. Happy to look into this if it's useful.

@clapierre
Copy link

Hello @choldgraf @jasongrout @sinabahram, well we are 10 days before the deadline to submit a proposal for this accessibility workshop.
Does anyone have any ideas for a venue and does the timing I suggested work for you all either
March 4,5 & 6. Or March 16, 17 & 18.

If we need to put a budget together we will need to jump on this fairly quickly.
Thanks
Charles

@choldgraf
Copy link
Contributor

Tomorrow I'll see if we can get a spot at BIDS at UC Berkeley on those days...do we have other options for a location?

Happy to put cycles into writing etc in the new few days.

@clapierre
Copy link

Thanks Chris, let me know if you want to jump on a call next week sometime to help come up with a budget etc.
Charles

@choldgraf
Copy link
Contributor

@clapierre that sounds good to me. I'm relatively free on Monday, does the afternoon work?

If others would like to join in the call I'm happy to adjust times/days/etc.

@clapierre
Copy link

2pm on I am free so if you want I can send you an invite for a zoom meeting.

@choldgraf
Copy link
Contributor

choldgraf commented Dec 6, 2019

monday @ 2pm (California time) works for me...any others interested in joining?

@sinabahram
Copy link

sinabahram commented Dec 6, 2019 via email

@choldgraf
Copy link
Contributor

Also wanna ping @trallard to see if she'd be interested in this. She spearheaded a similar effort last year. It didn't get funded but perhaps we can reuse some material. https://discourse.jupyter.org/t/jupyter-community-workshop-proposal-on-diversity-inclusion-and-accessibility/259

@jasongrout
Copy link
Member

jasongrout commented Dec 8, 2019 via email

@trallard
Copy link
Member

trallard commented Dec 8, 2019

Hey folks I am definitely interested in helping with this proposal.

As per a venue I can check if we can use the Microsoft reactor in SF for this. I will check the availability first thing tomorrow and let you know. I'd love to join the call but 2pm California time might be a bit too late for me on Monday

@zorkow
Copy link

zorkow commented Dec 8, 2019

I have two hard deadlines on Tuesday. So Tuesday evening UK time is the earliest I can jump on a call.

@trallard
Copy link
Member

trallard commented Dec 9, 2019

Hi folks FYI:

  • The proposed dates are already taken at the SF reactor, but I can provisionally book 25-27th March 2020 if that would work (the venue would be completely free of charge)

I am also happy to put cycles in for writing, let me know if the call is happening or if this can be moved earlier as that time is a bit late in UK

@clapierre
Copy link

Should we meet today then at 2pm pacific or try for some time tomorrow?
Sounds like @jasongrout could do tomorrow, and possibly @zorkow.

As for the venue possible dates of the 25-27 (March). I will be returning from a Conference eBookCraft late on March 25th so I could only participate on the 26/27 if we keep those dates.
We don't need to stick with March, it was just a suggestion to coincide with CSUN. If we have it another time then @zorkow's airfare would be also considered for the budget since he would have been already attending CSUN.

@choldgraf
Copy link
Contributor

@clapierre if we can find a time that works for more folks tomorrow quickly, let's go with that. Otherwise we can meet today and report back to folks? I'll keep my 2pm today open either way.

Can we quickly see if Tuesday at 10am (California time), 6pm (UK time) works for a call?

I don't believe that we need to pick dates etc before writing the proposal, if I remember, other proposals in the past didn't have this level of detail in them. More important is to craft the idea / value to jupyter / people that should be in the room / etc.

@trallard
Copy link
Member

trallard commented Dec 9, 2019

6pm tomorrow should work for me!

@clapierre
Copy link

I have a conflict tomorrow at 10am pacific. I can do an hour on either side of that 9am or 11am.
otherwise I can only meet for 15 minutes at 10AM pacific tomorrow before my other meeting at 10:15

@choldgraf
Copy link
Contributor

OK how about we just fill out a Doodle to find a 1-hr window on Tuesday that works for the most folks, can folks fill out there availability tomorrow here:

https://doodle.com/poll/qm6fwhigzxxu64yk

?

Hopefully that'll be easier than us replying to this thread :-)

@clapierre
Copy link

My meeting tomorrow got cancelled so 10am pacific does work now. sorry about that.

@choldgraf
Copy link
Contributor

Hey all - what if we did 9:30am-10:30am Pacific time? That way @trallard could jump in for the first half, and @zorkow could join for the second? I believe that @clapierre and I can make the whole time.

@clapierre
Copy link

@choldgraf that works for me. You can email me the invite [email protected]. If you want me to set up the invite on my zoom account then I will need everyone's email address. I have Jason's and Volker's.
Thanks

@zorkow
Copy link

zorkow commented Dec 9, 2019

I might be back before 6pm, just can't guarantee it. But I get on the call as soon as I am home.

@choldgraf
Copy link
Contributor

choldgraf commented Dec 9, 2019

I think we can use the LBNL Jupyter Zoom channel, it should be open at this time. Some details on the call here:

When

9:30am California time on December 10th (see this arewemeetingyet link for timezones)

Where

At this zoom link (redacted)

Goals

  • Make a plan for writing the Jupyter / Bloomberg proposal
  • General ideas for where / when to host the meeting
  • An idea of core people we'll need for the meeting
  • realistic objectives for the meeting
  • anything else?

@clapierre
Copy link

BTW in the future I wouldn't put zoom account info in gitHub as this is open to the public. We shared zoom information before and got hacked.
See you all in a few hours.

@choldgraf
Copy link
Contributor

@jasongrout are you planning to meet today? We are meeting now on the zoom link above

@jasongrout
Copy link
Member

@choldgraf - sorry I didn't make the meeting this morning. Can someone summarize the discussion here? Or I can call you separately today to catch up.

@choldgraf
Copy link
Contributor

choldgraf commented Dec 10, 2019

Rough meeting notes

In attendance

Background

  • Last year there was a meeting to address some a11y issues in JupyterLab
  • Part of W4A conference, was a 2-day hackathon centered around making quick progress and PRs
  • This process made some small improvements to a11y, but it was clear that more foundational changes needed to be made in Lumino (née Phosphor)
  • There was a user-facing audit made, and some general ideas for changes, but was clear that more specifics and deeper dive were needed.

Goals for the workshop

  • This workshop will build on top of the work done last year to take a deeper dive in the infrastructure of Lumino
  • What we'll do
    • Have a top-to-bottom rundown of JupyterLab + Lumino with the goal of understanding its architecture etc.
    • Run a deeper audit of JupyterLab + Lumino
    • Come up with a laundry list of technical changes and paths forward to implement
    • Do some triaging / ranking of impact and effort
    • Turn this into some kind of structured document we can use to organize work, and potentially fundraise
    • Discuss ways that we can introduce more a11y-friendly standards, hooks, protocols, etc into the Jupyter ecosystem (e.g. so extension authors can easily plug into a11y).

Planning

(in short, I think we confirmed the details that @clapierre originally suggested in #11 (comment), so mostly we need to turn this into a proposal for the community call)

  • People to invite
    • Joanmarie Diggs (Orca / Aria expertise)
    • James Nerthon
    • Doug Shepers? - data visualizations
    • Folks on this thread
  • People that need to be there
    • One or more people with a deep understanding of Lumino / JupyterLab and can share their knowledge with others
    • One or more people with a11y expertise that can work with the Lumino people to create specific technical roadmaps
  • Location will be in the Bay Area, either MS reactor (@trallard), the Lighthouse (location of W4A hackathon last year), or UC Berkeley.

Next steps

  • @choldgraf will write a draft of a proposal in the next day. Will post to this thread for others to comment.
    • Synthesize background and goals from these notes into a narrative doc.
    • Plan is for grant to cover travel + hotel for this meeting.
      • Does it need to cover anything else? E.g. is personal time from folks being donated for this meeting or do we need to pay consulting rates? (in particular, @sinabahram)
  • Need to nail down a date and location, but these don't need to happen before the proposal since we already have a few good leads.

OK those are the notes that I had. @clapierre and @zorkow does this look correct to you?

@choldgraf
Copy link
Contributor

Hey all - just a note that I am still waiting to hear from experts about the core group that needs to be there. I think this means I am waiting to hear from @ellisonbg , @jasongrout on the Jupyter side, and @sinabahram (and maybe others?) on the accessibility side.

@sinabahram
Copy link

I believe that Volker and myself would be most needed, followed by James (I only say this because he's indicated he can't spend the whole week, not because I don't think he's not in category 1), and then followed by Neil. That assumes that we're handling structural and coding-related issues first before things like math content accessibility. Neil can speak-up if he feels I've mis-categorized him :).

@choldgraf
Copy link
Contributor

@sinabahram - I see that the week of June 15th works for most other than yourself. Do you think you could make this week? It seems like that month +/- a week or two is the window that works best. I also think it'll be less-likely that we have coronavirus issues as we head into summer, so I think there's benefit to having this meeting later on anyway.

@sinabahram
Copy link

sinabahram commented Mar 3, 2020 via email

@ellisonbg
Copy link
Contributor Author

ellisonbg commented Mar 3, 2020 via email

@choldgraf
Copy link
Contributor

Yeah it's something that the Pangeo meeting is worried about as well. I am hopeful that coronavirus concerns will die down a bit in the summer time (likely before returning in the Fall). However, I think it's still a significant concern.

Given that the success of this meeting relies on getting a few key stakeholders in the room, I am not sure how to proceed...

@NSoiffer
Copy link

NSoiffer commented Mar 3, 2020 via email

@sinabahram
Copy link

sinabahram commented Mar 3, 2020 via email

@sinabahram
Copy link

sinabahram commented Mar 3, 2020 via email

@clapierre
Copy link

I think that might be a good idea as well considering the circumstances.

@zorkow
Copy link

zorkow commented Mar 3, 2020

Sorry, I lost the thread a bit. I was fully offline while skiing and still haven't recovered.
Skim reading, I see two issues:

  • James' availability: As the main focus at the beginning of the workshop should be on a code audit to find the main barriers to accessibility, I believe that can be done without full knowledge of the Aria standard. So I don't think we would need James for that. However, it would be great to have him there towards the end of the week. But the beginning is probably a waste of his time.
  • Date: I agree that planning for the week of June 15 with Autumn as a contingency is probably a good idea now.

I would also assume that the "outbreak" will die down in a month or two. At least I'll be making my way to the Bay Area on Thursday.

@choldgraf
Copy link
Contributor

Hey all - I have been holding off on making any date decisions to see how the virus will spread. That said, I think that @zorkow makes a good point that unless we plan on waiting until the Fall (which is outside the window of what NumFocus allows for the dates), then we will just have to live with the risk of cancellation.

So, can everybody put a pin in the week of June 15th, and we can reassess in a month or so based on how the virus has spread. @jasongrout or @trallard , could you check if your respective locations would be available that week?

If these dates don't work out, another option is to try and hold this meeting in a more focused and online-only manner. If anybody has experience or thoughts on doing that, please reach out...

@trallard
Copy link
Member

Hi I can check tomorrow when I am back at work - I am not sure if the Reactor will be taking bookings atm as I know everything has come to a halt.

Also I believe NUMFOCUS will allow for the workshops to be moved due to the whole covid-19

@choldgraf
Copy link
Contributor

Hey all - I wanna give a heartbeat on this. I am not sure what the best plan forward will be, but it seems clear to me that we cannot expect this event will happen in mid-June in person. Do others agree?

If that is the case, I think that we have three options, and I'd love to hear what others wish to do:

  1. Post-pone this even until the Fall time (though we may run into the same issues)
  2. Plan an online sprint around these issues
  3. Try to accomplish the planning and accomplish tasks asynchronously (perhaps in this repository)

You all are the experts on JupyterLab / Accessibility, so I will defer to your judgment on the best way forward there. I think that my vote would be for something like a few hour-long sessions to cover major topics we'd have covered in person, as well as brainstorming some github issues and maybe a project board to track progress. Then, transition to online conversation spaces to start making progress.

*NOTE: I will have extremely limited availability starting in mid-July, so I will not be able to significantly plan or participate after then, just FYI (I'm having a baby)

@jasongrout
Copy link
Member

First of all, congratulations @choldgraf! That is really exciting!

I agree meeting in June in person is not going to happen.

I think the energy from (1) or (2) is needed to make (3) succeed. Perhaps (2) might be better to move things forward, though I'll defer to @sinabahram and others that are participating about how effective an online session might be compared to an in-person meeting.

@clapierre
Copy link

Yes congrats thats awesome! I know myself I am super busy through August, so my vote would be to do something in September. I think in person would be better.

@sinabahram
Copy link

Congratulations @choldgraf!

personally, I think travel will not open up for this kind of thing until Q1 or Q2 of next year, at the earliest. Maybe I'm biased in that I've already needed to cancel every single work trip between now and December, spanning at least a dozen or more trips, and those were simply the ones already known about in March and April. That doesn't even take into count all the trips that would have happened but never even got scheduled due to current circumstances, call that another dozen given extrapolation on the low-end of previous years. That's a ton of different organizations of various sizes all making the same decision, so I firmly don't think anything is happening in person in 2020, full stop. I could be wrong on this.

RE some extended sessions online, my thoughts are as follows. having a dedicated couple of days where everyone is in the same timezone and same room means a maximal return for a fixed donation of time and effort on my part. To spread this over a longer period with far less synchronicity translates to a rather substantial ask of time and hard opportunity costs for less potential beneficial outcomes, and so I can't say that I'm thrilled by that particular calculus, though it may be what we are left with due to necessity.

@ellisonbg
Copy link
Contributor Author

ellisonbg commented May 18, 2020 via email

@zorkow
Copy link

zorkow commented May 21, 2020

Firstly, Congratulations @choldgraf. Is it the first one? That's still exciting then...

While I am not quite as pessimistic as Sina regarding travel in general, I am probably more pessimistic wrt. to foreigners being allowed into the US.

I think we all know, there is nothing more effective to push such a project forward than being locked into a room together for 5 days. On the other hand we should get the ball rolling soon.
So we should have a virtual event first and if the funding is still available next year (and US borders are not closed), we could have an in person event then.

We held W4A conference this year on Zoom in Taiwan, and that was a very good and engaging experience. I am not sure how well this translates to workshops and hackathons, but the Diagram code sprint is in June; we can assess how effective that is and take it from there.

@clapierre
Copy link

LOL, yes we will be the guinea pigs and let you all know the results on how well the virtual code sprint works out, we will be using Slack / Github / and Zoom including Zoom breakout rooms potentially plus maybe some other collaborative documentation tools like google docs etc.

Our Virtual Codesprint will be from June 10-12th. (We will be sending this out to our DIAGRAM community later today I believe.)

@trallard
Copy link
Member

trallard commented Jun 3, 2020

Hey congratulations @choldgraf 🎉🎉

Echoing what every one mentioned before I would be happy for the event to move online. I recently moved the mentored sprints online and it was a huge success. So I would be more than happy to help with this and advise as much as possible.

@choldgraf
Copy link
Contributor

Hey all - I just posted this in a new issue to avoid this single thread becoming more gigantic than it already is:

#13

tl;dr: I don't think that I should be the one spearheading the organization of this accessibility meetup, because I'm expecting a baby girl in August and I fear that if this continues to be my responsibility then we will drop this ball in an unintentional way. I am happy to support somebody else in organizing etc, but I can't be the one to have responsibility for pushing it forward.

@choldgraf
Copy link
Contributor

Hey all - I just had a meeting @trallard , and we came up with the following plan. Would love to hear what others think:

  • Attach an accessibility sprint / workshop to either JupyterCon or PyData Global.
    • Ensure that we have enough availability from the folks in this thread that we can make meaningful progress towards auditing / roadmapping Jupyter interface accessibility
    • We could also use this to get participation from other interested parties that attend those conferences
  • @trallard will lead the organization of this effort. She is going to explore either baking this in to one of the sessions as JupyterCon or proposing it as a satellite event.
  • I will help out however I can, whenever I can poke my head out of the fog of new baby.

Are others +1 on this approach? I think that attaching this to one of the major conferences this year could be a great way to streamline organizing responsibilities and piggy-back off of the energy and attention that will already be directed to those events. We could also potentially re-use some of the infrastructure those conferences will have for organizing sessions.

Also, I wanna say many many thanks to @trallard for offering to help organize this 👍

@sinabahram
Copy link

I think this makes general sense, but I hesitate to have the initial work coincide with an event like that. The reason is that I feel there are several conversations that need to happen first so as to organize some approaches, figure out low-hanging fruit, work on splitting out some tasks or prototyping some affordances, and then once those tasks are known, the added benefit of having tons of hands on keyboards is helpful; otherwise, it may do more harm than good due to noise/lack of specific problems to tackle. I'd be happy to hop on a call in the next few weeks to help roadmap some of that out if that is helpful.

@choldgraf
Copy link
Contributor

Hey all - I just spoke with @Ruv7 who said that there is still funding for this workshop to take place if we'd like to do so before the end of 2022. Since this issue is already quite large, I've created a new one to discuss re-booting the workshop process. I would love collaboration from you all there, particularly from folks who are interested in organizing! I'll close this issue as "resolved" since much of it was discussing funding, which we got :-)

new issue: #43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants