Jupyter accessibility meetings 2022
Contents
Jupyter accessibility meetings 2022#
1.12.22 Meeting Minutes#
Attendees#
tony
Ely
Mike
Frederic
Gabriel
Martha
Jason
Nick
Matthew
Chadi
What are people working on?#
Isabela
Jupyter accessibility workshops are upcoming on January 15, January 22, and two events in March.
Find all up-to-date links on the Jupyter blog announcement post
Gabriel
Mapping out and comparing frontend of JupyterLab and RetroLab
Chadi
How to get involved with Jupyter accessibility work
Review tasks on the JupyterLab accessibility project board
Focus on documentation fixes. Some could be adding alt text, making sure things are up to date.
Make changes to documentation theming that supports accessibility across projects (find test background on https://github.com/jupyterlab/jupyterlab/pull/11803 and https://github.com/pydata/pydata-sphinx-theme/pull/548)
Open issues based on what isnât working for you! Weâre relying heavily on standards, but user feedback would be even better.
Nick
exploring robotframework-axelibrary as a thing to add to JupyterLibrary
should be possible to e.g. configure
Test Teardown
toCollect Accessibility Violations
âŚand when error conditions arise
tag with violations which would bubble up to
potentially blocked by limited maintainer effort on upstreams
also have some data analysis tools for long-term ingest of many robot reports
both could be injected into e.g. robotkernel
Some links in chat:
1.26.22 Meeting Minutes#
Attendees#
Isabela
Frederic
Ely
Jason
Darian
Gabriel
Nick
Patrick
Tony
What are people working on?#
Tony https://github.com/jupyter/accessibility/issues/67
What jupyter/accessibility has been so far: kind of a cross-project team compass
This PR discusses ways to make it a more resource-focused and active repo. Also to help people actually start using Jupyter tools (thatâs been a popular ask)
Patrick
Could anyone give an update on how things are currently working, perhaps both high level and in the code?
People are interested! We need to follow up and connect these communities
Are these communities also willing to giving feedback on how to make better experiences (not just be WCAG compliant) based on how they use these tools?
Isabela
Jupyter accessibility workshop summary/things to do
Alt text PRS from the workshop (still in progress until the end of this week)
Gabriel
Does the JupyterLab settings UI PR add accessibility features/is that a place they could go in the future?
Right now? Thatâs not the focus. It could be added in the future.
Next steps#
Discuss jupyter/accessibility reorganization (open for commenting to everyone!)
Follow up on cross-community collaboration (Isabela, Jenn, Tony, Patrick)
Remove hardcoded css colors to improve the extensibility of the these (maybe Nick?)
2.09.22 Meeting Minutes#
Attendees#
Nick
Tony
Martha
Ely
Frederic
Thomas
Chadi
Isabela
What are people working on#
Chadi
Interest in being assigned from existing issues
nick: ipywidgets needs love. probably no existing issues, needs the audit and issue authoring. âthere are definitely some ambulatory items on some of the custom controlsâ
Thomas
âWhen is Jupyter Classic going away?â
Tony replies with the related Juypyter Enhancement Proposal
https://jupyter.org/enhancement-proposals/79-notebook-v7/notebook-v7.html
Whoâs working on the grant now
Gabriel (not in meeting today) is the person you want to meet. Heâs been working on testing at jupyter/accessibility
Whatâs been happening?
Frederic
jupyter-ui-toolkit update
Intent of making all components in JupyterLab more accessible from their foundation rather than only remediation of existing.
This has ties to [WIP] JEP for React.js at Jupyter datalayer/jupyter-react#9.
Tony
We need to have some testing notebooks for manual testing. Any thoughts on things/content types we need to make sure to include?
Ely: Errors!
Nick: the smallest elements, input/output (not even cells). something like the work at jtpio/replite
Nick: run-only experience
Isabela: Jupyter accessibility workshops in January (summary)
Sprint had two alt text PRs come out of it. Jupyter.org alt text was merged. Project Jupyter documentation PR could use review
Isabela: Jupyter accessibility workshops in March!
Draft sprint topic is on auditing. Is there anything specific youâd all like to have covered? Are there any projects youâd like to propose we use for the sprint?
2.23.22 Meeting Minutes#
Attendees#
Tony
Ely
Gabriel
Martha
Nick
Jason
notes#
pdf accessibility https://www.section508.gov/create/pdfs/
stylelint-a11y https://github.com/YozhikM/stylelint-a11y
https://bareynol.github.io/mui-theme-creator/ theme editor
Thoughts from Ely on custom themes
should we talk to people who are used to customizing colors?
an export button would be really good for someone who has spent a lot of time working on their own theme locally
What are people working on#
@tonyfast
reusable tasks for building jupyterlab, retrolab, lumino combinations.
turning
jupyter/accessibility
into a js/py packages
3.9.22 Meeting Minutes#
Attendees#
Martha
Tony
Jason W
Jenn
Isabela
Gabriel
Agenda#
Gabriel
What do developers want/what would you all find helpful in the jupyter/accessibility repo
People can give feedback and ideas later via issues (or PRs if you have something you want to contribute) on jupyter/accessibility.
What Iâm working on, just FYI:
Jason W
JupyterLab cell toolbar PR 12028 â Feedback sought on usability, accessibility, etc.
Tab behavior is consistent throughout JupyterLab (which is good), but itâs JupyterLabâs tab behavior that doesnât make sense. This may need to be a separate issue.
Tabbing through regions is discussed in https://github.com/jupyterlab/jupyterlab/issues/9688
Focus is working throughout, so there is nothing that relies solely on a hover state (good!)
How this interacts with a cellâs command versus edit state is interesting. Navigating the toolbar happens in command mode, but tabbing fully through the toolbar transitions to edit mode with no immediate way back (instead users must return to the start of command mode outside the cell). This is to preserve the use of tab for code completion in a cell, something we do need to preserve.
Jenn
Grant!
Tony
brings up discussion at matplotlib/matplotlib #15971 Improve the accessibility of figures shown with
_repr_html_
around deprecation oflongdesc
and if there are ways this can be solved in a better experience and not only one-off tags.
3.23.22 Meeting Minutes#
Attendees#
Mike
Ely
Martha
Jenn
Gabriel
Tania
Isabela
Agenda#
Jupyter accessibility workshop resources! (First two events are up, but the last ones are pending. They will all link here.) Jupyter accessibility workshops repo
Mike:
progressbar aria https://github.com/jupyterlab/jupyterlab/pull/12238
An addition based on review on a prior pull request.
This is something worth testing! Open invite for people to give it a try.
Prompted a discussion around what/how can we test these things going forward. Do we have several accessibility fixes weâd like tested where itâs worth actively reaching out to people?
Similar, but separate from discussion around regular user feedback surveys timed with JupyterLab releases.
Tania: Jupyter governance and jupyter/accessibility. A discussion around whatâs happening and where the community thinks we belong!
The initial proposal:jupyter/governance #121 Standing Committees and Working Groups PR
Further discussion: jupyter/governance #124 [Proposal] - add jupyter/accessibility as a software sub-project
:pencil: Future governance Software Steering Council roles and responsibilities
Questions to pass over to the governance body:
What are the criteria under which the WGâs might or not get voting rights?
Same but for continued vote/existence?
Pros and cons of each level. Summary is that it seems like thereâs more pros and no real cons on being a software project (long term).
Next steps#
TODO: open an issue on jupyter/accessibility and use it as a RFD (request for discussion)/lazy voting and revisit in 2-4 weeks?
Isabela to follow up with Mike on asking the community for feedback on existing accessibility fixes.
4.6.22 Meeting Minutes#
Attendees#
Frederic
Nick
Jason
Darian
Martha
Ely
Gabriel
Mike
Preston
Tom
Rohit
Pooja
Isabela
What are people working on?#
Preston
Contributing guide questions https://github.com/jupyter/accessibility/issues/47
Should this be specific to the repo (not general jupyter contrib)
CI. whatâs the status (based on jupyterlab benchmarks repo)
things that donât exist (another issue or whatâs happening?)
Follow up on issue with some of these specifics.
Tom
Has there been a date announced for when support for classic Notebook (as it is now) ends? This has to do with Notebook 7 release work.
goal is to only support two versions simultaneously
nbclassic package (notebook 6 ui written as jupyter server extension)
https://github.com/jupyter/notebook-team-compass/issues/5#issuecomment-1085254000
support for extension updates is a priority
Gabriel
:tada: Not much to discuss, but I put up my first JupyterLab PR: Add checkboxes to file browser #12299.
Small accessibility win; hopefully will lead to more
Darian
Governance question re: Working Group and Subproject brought up by Tania
Isabela
Open question from me, what do you all want me to work on next?
From notebook call: nbgrader importance; could use my attention
âIt just canât be worse than the existing nbgraderâ :laughing:
If nothing else, can we go through the JupyterLab accessibility project board?
tag people not necessarily accessibility involved if they know whatâs up
ask it in jupyterlab
Next steps#
Follow up on accessibility fixes survey/feedback request (Isabela to Mike)
Follow up with Tania about last meetingâs governance discussion (Isabela to Tania)
Three options for governance next steps and have people involved come to consensus (Isabela to create and tag people)
4.20.22 Meeting Minutes#
Attendees#
Gabriel F.
Nick
Isabela
What are people working on?#
Please vote on jupyter/accessibilityâs status in the new Jupyter governance by midnight wherever you are today!
Meeting this Friday, April 22: FAST-based JupyterLab UI toolkit. This is a discussion around the proposal for a new JupyterLab UI toolkit, which weâve seen demoâed for accessibility considerations. Show up or comment on the issue if youâd like to weigh in!
Isabela
Gabriel
A plan for the next six weeks that Quansight Labs is considering
A number of learnings about automated accessibility tests has been rolled into that doc
We are looking for pathways to contributions from other people - especially in this group
Nick
Model-based testing. Build a user model of somebody using the Jupyter test. A model is more interesting that a particular case because you get to weird error messages and corner cases that we need to test for.
A close example with stateful, property-based testing in Hypothesis
Workflow is not to do this all thinking about it as a test, but more as a state and task combo (ie. Iâm looking at a notebook and I want to )
on the subject of building up a language to create test plans (Isabela metaphor: magnetic fridge poetry)
goal, action, goal, action, goal action (thatâs a human-readable way we can work with)
https://github.com/robots-from-jupyter/robotframework-jupyterlibrary
https://github.com/ipython/traitlets/pull/705#issuecomment-1103958033
opt-in a11y checks - label on PR that goes into changelog
5.04.22 Meeting Minutes#
Attendees#
Martha
Isabela
Gabriel
What are people working on?#
Isabela
Governance follow up. We voted at jupyter/accessibility #81. Isabela needs to know how to move this forward.
Testing updates! Weâre at the foundation level now, but thoughts on prioirities are welcome.
Feedback: documentation is the most valuable thing!
Mentioned links: Quansight-Labs/jupyter-a11y-mgmt #95 Scoping automated testing comment and jupyter/accessibility #74 past draft PR for axe-core testing.
Next steps#
The dream: updated galata documentation.đ
Follow up about governance status (Isabela)
6.1.22 Meeting Minutes#
Attendees#
Tony
Mike
Ely
Gabriela
Isabela
Nikhil
What are people working on?#
Intros for newcomers!
Tony
jupyter/accessibility #90 automated accessibility testing efforts
axe-core test suite
Run axe-core tests against JupyterLab in GitHub Actions
Will help support user stories for testing in quansight-Labs/jupyter-a11y-mgmt/discussions/122
Automated testing is known to catch only a percentage of known accessibility problems (usually WCAG, which is the minimum itself). How/are there plans to include disabled user testing?
Because of open source we need solutions that arenât only tied to people (espcially individuals). But we also agree we need this input. Itâs been a combo of getting funding (to pay people for their expertise) and some parts of JupyterLab are so inaccessible that we need to fix areas before we can get good feedback.
How does this fit with the extension-cookiecutter?
Voice navigation in JupyterLab?
Where to start? Has there been existing work? Not as far as anyone here knows.
Having semantic HTML is probably the start, though, because it would allow other tools to hook into JupyterLab well.
Some resources on how this work might need to behave: Browsing with assistive tech - Tetralogical
Workshops mentioned in Lab call?
Thereâs no current plan from anyone here to submit for the next Community Workshop proposal cycle.
Next steps#
6.15.22 Meeting Minutes#
Attendees#
Tony
Gabriel
Mike
Adam
Martha
Isabela
What are people working on#
Tony
Help using the extension cookiecutter
Isabela
Jupyter accessibilityâs governance status has changed. Hooray and thanks for yâallâs help! Weâre a subproject!
Testing updates. I want to share the manual testing script work and template for feedback.
JupyterLab accessibility statement. Iâd like to go over and request feedback on this proposal statement. Itâd also be good to think about how we propose this to JupyterLab.
Next steps#
Follow up on subproject set up (Isabela)
6.29.22 Meeting Minutes#
Attendees#
Gabriel
Tony
Darian
Sylvain
Martha
Nikhil
Mike
Tania
What are people working on?#
Sylvain
Codemirror 6 migration is ready for testing, accessibility perspective and otherwise.
Please test it with the binder link in the PR! Feedback is extremely welcome! Please note CM6âs accessibility doesnât seem to be clearly documented.
Known issues we will not be addressing: LaTeX syntax highlighting does not yet exist
Isabela
JupyterLab accessibility statement approach
Iâm going to be working on theming soon. What are your dream themes? (ie. ideal accessible themes)
:bulb: colour-blind friendly - as many as possible?!, selective contrast, address Irlen syndrome needs, monochrome
Gabriel
I havenât been doing much Jupyter-related accessibility work lately, but I have been trying to implement accessibility-related CI/CD for the upcoming new Quansight website (quansight.com and labs.quansight.org), and I have been a bit surprised (but not surprised) that some of this stuff isnât more plug-and-play.
Quansightâs new website is statically generated with Vercel. You might think that there would be some ready drop-in solution to run pa11y-ci or axe-core against the pages in your site, but so far I havenât found it.
Nikhil
Havenât been working on Jupyter-specific accessibility tickets (although I would like to dive in), but have been working on data viz accessibility! Continuing some prior research I worked on during school (w/ Doug Schepers, Frank Elavsky) on auto-generating summaries using NLPfor complex/reactive charts/graphs and also diving more into sonification (Highcharts).
One of our research benchmarks: Chart2Text: Generating Natural Language Explanations for Charts by Adapting the Transformer Model
From @gabalafou: hereâs a Colab using some sonification
Mike
https://github.com/krassowski/jupyterlab-voice-control is now a thing, was demoed on previous JupyterLab meeting
Next steps#
Collect requests for notebook and visualization standards in JupyterLab to figure out where that info may be best stored (Isabela)
Create a list for requested JupyterLab accessible themes with status (Isabela)
Update on static website testing set up (Gabriel)
Watch the jupyter-lab-voice demo when itâs on YouTube!
7.13.22 Meeting Minutes#
Attendees#
Tony - QLabs
Balaji - Berkeley
Ryan - Berkeley
Allison - Berkeley
Paul - Berkeley
Sean - Berkeley
Tania - QLabs
Gabriel - QLabs
Richard - Berkeley
Isabela - QLabs
What are people working on?#
Quick updates
Circle back on next steps for our subproject status: probably a council
Theming status - JLab 3.4.3 under review based on this draft criteria
Questions about JupyterLab accessibility status for use at UC Berkeley.
JupyterLab as a part of DataHub, needs to be accessible.
Interest in WCAG 2.0 AA alignment and figuring out how to collaborate.
If we do an audit now, can we show by [timeline is unclear]
Short term: classes deploying this before the end of the year
Long term: how do we sustain this work and these changes to avoid regression and ensure a solid experience.
New campus committee will focus on digital accessibility - Berkeley News
About Accessibility in Learning Tools - Berkeley Research, Teaching, and Learning
Next steps#
Update meeting notes in jupyter/accessibility (Isabela)
Bring up statement work with main JupyterLab team (Isabela)
Follow up on subproject next steps (Isabela)
(+1 Nikhil - would love to learn more!)
8.10.22 Meeting Minutes#
Attendees#
Gabriel F. - Quansight Labs
Ely - Bloomberg
Ryan
Martha
Balaji - UC Berkeley
Mike
Richard
Isabela
Darian
Agenda#
Identify accessibility targets for Lumino 2 #341
Mike:
silentNotifications
support - there is a stale PR which has an accessibility related utility function for announcing changes, maybe worth pulling into in lumino https://github.com/jupyterlab/jupyterlab/pull/9031 it looks like a similar effort was attempted years ago for: https://github.com/jupyterlab/jupyterlab/pull/6583Changing divs to buttons? (+1 from Isabela on this)
Isabela: Does the labelling issue in jupyterlab/jupyterlab #6581 Input fields in dialogs need to be labeled have roots in Lumino?
[name=gabriel] is DataGrid used in JupyterLab? Darian: CSV viewer, variables viewer(?), pandas dataframes - basically anywhere you see the âspreadsheetâ component
question from Ely about accessibility of canvas (because datagrid uses canvas)
Isabela mentions/asks about Google Docs and Canvas. Link from Mike: https://workspaceupdates.googleblog.com/2021/05/Google-Docs-Canvas-Based-Rendering-Update.html
[name=gabriel] what counts as API change beyond method names/signatures?
response from Darian: for example, CSS is considered API because we donât make it private
Circle back on next steps for our subproject status: probably a council
Theming status - JLab 3.2.0 partial (non-color) draft review. Thereâs also been more indepth review on zoom behavior at quansight-labs/jupyterlab-accessible-themes.
Convention to support alt text in notebooks - github issue
Mike would like the ways that metadata gets used by tools like nbconvert for things like alt text to be standardized
Realted issue at jupyter/accessibility #37
Some questions. Should this be a change done on a tool by tool level, or overall? If it is overall, what is the path?
Possibly a Jupyter Enhancement Proposal to bring this into nbformat. Possibly the Jupyter Standards group. These will both be slower. There may be faster and just as good changes in nbconvert level.
What happens when you work on the individual output level versus the cell level (which may have multiple outputs).
Mike: IPython mimebundle adds
alt
to output metadata: https://github.com/ipython/ipython/blob/9ed8ecd64be967335ce7f098f67aa602a3f3383b/IPython/core/display.py#L1015-L1050Mike: R IRKernel does not add alt to image output metadata: https://github.com/IRkernel/IRdisplay/blob/master/R/display_images.r
Mike: width and height metadata are âcodifiedâ: https://nbformat.readthedocs.io/en/latest/format_description.html#display-data
Darian: but not formally in https://github.com/jupyter/nbformat/blob/main/nbformat/v4/nbformat.v4.schema.json (which does not prevent the use of
width
,height
noralt
)
Next steps#
Circle back on next steps for our subproject status: start a council (Isabela)
from Ryan âshould there be a github issue in lab to measure/describe a11y issues with itâs current use of canvas?â Yes! (Isabela)
Review DataGrid specifically to understand the work that would be needed to make it more accessible (start with a complicated component)
8.24.22 Meeting Minutes#
Attendees#
Darian
Tony
Gabriel
Ryan
Martha
Isabela
Allison
Agenda#
Rendered notebook user testing has started! You can track that work-in-progress on the iota-school/notebooks-for-all repo
Lumino 2.0 accessibility
Relevant links lumino #341 and jupyterlab #12992 and lumino examples and Section 508
This is in alpha release at this point.
Lumino provides the top level menus, the command palette and search, the keyboard shortcut system, the dock panel (sidebars), and Widgets (a lot like react components but with different life cycle; more like building UI in Qt).
Some changes are low-level changes, like making sure that keyboard navigation is not inhibited. Lumino doesnât have a concept of the content in these widgets, so some changes that are content-specific do not belong there.
Whatâs the status of where we are in evaluating any API-breaking changes or other issues?
DataGrids still seems the most potentially suspect. It does impact certain cell outputs, too, so this could be critical.
Probably the most sure-fire choice would be to provide an option to turn this off and render as a table.
Maybe itâs easier to review on Notebook and then we find those issues and then can evaluate wheter or not they are Lumino.
Where do ARIA labels or similar tags align with this work?
Gabriel
A win! lumino #373
Next steps#
Review Notebook 7 for accessibility as means of identifying Lumino changes and more. (Isabela + anyone interested) (most recent review is)
9.07.22 Meeting Minutes#
Attendees#
Darian
Ryan
Gabriel
Martha
Isabela
Ely
Agenda#
How do we want to set up the council? Background: the governance bootstrapping docs donât account for the fact that we became a software project later and did not have existing steering council members to start our council process. We also need to have a council soon to nominate our representative to the new SSC soon.
Some options to create the starter group:
Add who has already voted in our most recent votes as the starter group.
Add whoever is in the GitHub organization as the starter group.
Add meeting attendees over a certain list of recent months as the starter group.
Maybe a number of regular attendance? But this shouldnât be the only thing because there are many valuable asynch contributions.
Darian: âhas attended x number of times out of y number last meetings OR has voted in https://github.com/jupyter/accessibility/issues/81â
More setting up council to dos:
Council team compass
Github team
Mailing list (if wanted)
SSC representative
two-factor authentication
Isabela
Reflow and Lumino?
Next steps#
Isabela to set up starter group list for the council. Reach out to list of individuals.
Isabela to post an issue about how we determine this starter group for transparency.
Add PR to jupyter/accessibility when this starter group is formed. Then we can have the discussion about where things go without blocking this process.
9.21.22#
Attendees#
Darian
Tania
Gabriel
Ryan
Ely
Agenda#
Discussing depth-levels in JupyterLab/lumino codebases
Example that sparked this conversation https://github.com/jupyterlab/jupyterlab/pull/13109
Most recent Zoom audit in JupyterLab and findings https://github.com/Quansight-Labs/jupyterlab-accessible-themes/issues/34
Examples of manual-testing scripts we are working on https://github.com/Quansight-Labs/jupyter-a11y-testing/tree/main/testing/scripts
Darian: is happy to offer office hours to help folks orient around the codebase
Ely: had plenty support from Jason when walking this path
Ely: some helpful information was around panel, CSS, historical context (from Jason), panels needed for a particular situation
Provide examples of extensions with the panels/layout explanations (maybe in the readme in Lumino)
Tania: could we look at codetours for example? https://github.com/microsoft/codetour
Adjacent: Tania proposed this docs reorg (JupyterLab) https://github.com/jupyterlab/jupyterlab/issues/7387
Darian: proposal -> use some of these calls to do âBBQ bonanza/triageâ -> find where the issue resides to help fixing this
October 5 2022#
Attendees#
Jeremy (might not be able to attend)
Frederic
Mike
Gabriel
Isabela
Allison
Darian
Frederic
Martha
Detroit
Balaji
Ryan
Agenda#
Mike:
Shadow DOM
Jeremy:
A new pre-release of Notebook 7 is available: https://github.com/jupyter/notebook/releases/tag/v7.0.0a6
Discourse topic: https://discourse.jupyter.org/t/notebook-7-pre-releases-are-available/16063
It includes the switch to CodeMirror 6 that landed in JupyterLab: https://github.com/jupyterlab/jupyterlab/pull/11638
Closed the old issue on the RetroLab repo that was about doing an accessibility audit on the RetroLab UI: https://github.com/jupyterlab/retrolab/issues/80. Now that the CodeMirror 6 update is available in a Notebook 7 pre-release it should be possible to make this audit with a document-oriented notebook UI.
There is no development happening in
jupyterlab/retrolab
anymore, improvements and fixes should be done in JupyterLab and Notebook 7.Happy to help in the
jupyter/notebook
orjupyter/accessibility
. Please report any issue if you find any, thanks!Try it on Binder with this gist: https://gist.github.com/jtpio/d368ab89cee5123ecee60683115e15f3
Frederic
Improvements of tab panel labelledby - will be part of 3.5.0
Some related work with consistency of CSS variables between background color and text color:
Link background colors and ui font colors in the style
This was seen when working on a JupyterLab theme editor
Mike v2:
low hanging fruit good first issue for new contributors https://github.com/jupyterlab/jupyterlab/issues/13045
Isabela
Office hours follow up (from last meeting)?
Council updates?
Gabriel
If we have time for office hours, can we chat about tab focus indicators and/or tab traps in code cells?
Next steps#
Shadow DOM needs more research and/or a binder to test it in
Explore Notebook 7. Report Notebook 7 issues.
Add âoffice hoursâ help for under agenda and make a queue of issues to pull from
October 19 2022#
Attendees#
Mike
Isabela
Gabriel
Stephannie
Martha
GĂŠrard
Tania
Ryan
Balaji
Kseniya
Israel
Agenda#
Isabela
Discussion on directions for high browser zoom and JupyterLab at jupyterlab/jupyterlab #10004. Please weigh in!
Mike: Another approach would be to have UI and document zoom approached separately since it is possible they are different use cases.
Mike: âA datapoint for previous discussion: in VScode the default is to zoom everything and user needs to enable document zooming manually though they divide ctrl + scroll as it seems.â
For anyone curious, here is what we did on the collaborative keyboard navigation review for the Notebook 7 prerelease. It will become an issue elsewhere.
Gabriel
Sneak peek on some of the work Iâm doing. tl;drâ Run accessibility regression tests via GitHub Actions against a JupyterLab PR, showing if it breaks (or fixes) any regression tests.
Copy this to next meetingâs agenda: For the remainining meeting time, can we open up and dig into CodeMirror? -Gabriel [name=Tania] I am interested in this, mostly how can we âtestâ for the newly introduced accessibility features
November 2 2022#
Attendees#
Darian
Gabriel
Stephannie
Isabela
Martha
Ely
Ryan
Mike
Kseniya
Balaji
Tania
Agenda#
Isabela
Update on Space Telescope user testing results. This resources PR provides all info used to plan the tests so far and script, notebook used, and takeaways from the first round of tests.
Mike
nbdime? Keep an eye out for any PRs here because this could relate to the inaccessibility of the space. We should review any PRs with this in mind.
Darian
Rick mentioned someone from UC Berkeley might contact us re: accessibility for Jupyter tools deployed there
Jupyter Executive Council election
For the remainining meeting time, can we open up and dig into CodeMirror? -Gabriel [name=Tania] I am interested in this, mostly how can we âtestâ for the newly introduced accessibility features
November 16 2022#
Attendees#
Darian
Gabriel
Stephannie
Isabela
Tania
Mark
Detroit
Ryan
tf
Sylvain
Ely
Agenda#
Special guest appearance: Katie [name=Tania]- Since Darian mentioned an audit (potential) it would be definitely good to keep in sync and find a way to standardise our auditing processes in Jupyter-world
Isabela
Update on Space Telescope user testing results. We have more complete takeaways from the first round of tests. If thereâs any interest in me sharing the results or answering questions, let me know!
For desired reflow in JupyterLab, please feel free to weigh in on jupyterlab/jupyterlab #10004. Iâm trying to keep this moving forward and would like if we can get to a decided direction.
Regarding reflow Darian/Sylvain does any of you have ideas/suggestions on moving this forward and help land on a decision/path forward
[name=Gabriel] In response to this question, there was discussion and questions around Notebook 7 vs JupyterLab
Sylvain
Notebook v7 audit by Balaji at UC Berkeley
November 30 2022#
Attendees#
Mark
Martha
Gabriel
JooYoung
Tony
Stephannie
Mike
Tania
Agenda#
Gabriel
Discuss: âJupyter Accessibilityâ:
Group exercise: open your favorite search engine, type âJupyter Accessibilityâ⌠where does it take you? what is the first thing you see?
Are we happy with this?
If not, what do we need to do? [name=Tania] - we need docs like https://code.visualstudio.com/docs/editor/accessibility for Lab and friends [name=Mike] - Collect a list of extensions and themes for accessibility features see https://jupyter-accessibility.readthedocs.io/en/latest/#using-jupyter-software-with-assistive-technology Comments included that we donât have user-focused documentation to point to. Even if they live on a per project basis, it makes sense to also have them here.
Some take-aways:
Keep jupyter/accessibility as one repo. Donât split into two repos (one for user-facing docs, one for team compass)
Put sign posts for end users in jupyter/accessibility repo and website.
Try to add accessibility docs to jupyter.org and/or JupyterLab ReadTheDocs
Push forward the work done on the Accessibility statement, with an eye to providing useful info for disabled users.
Think about restructuring current docs so that they address different users: contributors, end users, maintainers, and such.
Repos that use the keyword accessibility but are incomplete or works in progress sohuld probably have some kind of WIP label and preamble.
Links:
[name=Mike] I opened a PR to add link to accessibility docs on docs.jupyter.org
[name=Tania] Point accessibility.jupyter.org to these docs?
Isabela
Summary of Space Telescope user testing results for test 1: navigation. Results slides. Full results.
Want to fix the broken link to our old meeting notes? Help with jupyter/accessibility #113 is welcome!
I want to review and (if needed) update the accessibility project board soon. Is anyone interested in giving this a review as well? We can split issues up to save time.
December 14 2022#
Attendees#
Min
Darian
Ryan
tonyfast
Blessing Ogoh
Gabriel
Isabela
Agenda#
Isabela
Calendar check. Is this our last meeting of the year?
[name=Gabriel] FYI, the JupyterLab team meeting on Dec 28 that precedes this one was cancelled.
Want to fix the broken link to our old meeting notes? Help with jupyter/accessibility #113 is welcome!
[name=Min] my first accessibility PR! https://github.com/jupyter/accessibility/pull/115
I want to review and (if needed) update the accessibility project board soon. Is anyone interested in giving this a review as well? We can split issues up to save time.
Gabriel
In the meeting before this one, Florence from QuantStack demoâd a JupyterLab extension to edit the look and feel of JupyterLab.
[name=Ryan] Sounds like it could lead to accessible themes or maybe more accessible defaults
[name=Gabriel] Yes! but for me the key thing that interests me here in terms of accessibility for end users is empowering end users to customize the UI to their particular accessibility needs (high contrast, color blindness, large font, etc.)
Min
Connecting Blessing, Outreachy intern working on accessibility in JupyterHub
Authentication, Spawning, Admin pages
Wave exposing existing color/contrast issues
How to make intentional design decisions
Darian
Wanted to open a PR against @steff456âs Lumino PR for collapsing menus
tony
Progress on navigating static notebooks after a recent round of tests.