Meeting topics:

Follow-up on last week's to-dos

• Swast start writing report, about the Google Doc audit specifically
  • Notes so far
• Swast to look into papers for inspiration for report structure
• Isabela to help schedule with collaborators
  • We scheduled with Gabriel, Eric, Tony and Noa
  • One mentor is present at each meeting.
• May or may not meet a collaborator by next week's meeting.
  • Met Gabriel on March 16, but had technical problems and couldn't complete audit. Rescheduled for next week, March 22.
  • Will meet with Eric after this internship meeting.
  • Will meet Tony and Noa next week as well.

Discussion topics and Resources

• Isabela's Document Outline Ideas
• Discuss what we want from meetings with volunteers
  • How can we help Swast feel better prepared for the meetings with audits?
    • Swast: "I could make a notion doc for to share the resources and an audit table which will have the tasks to be done"
    • Should we figure out the meeting agenda in our internship chat first? And then bring it to the volunteer group chat?
    • Perhaps there was a misunderstanding how much the mentors or Swast figures out meeting agenda.
  • Meeting with Noa, she can talk more about web accessibility.
    • Swast brought up a paper 'Web Accessibility Challenges', which could bring up discussion points for meeting Noa
    • Swast could prepare a Notion doc to prepare for meeting with volunteers
    • With Eric: first 30 minutes do audit, 15 minutes discussion
• How to write an audit report?
  • Resource: How to Write a Good Audit Report: 4 Key Resources to Follow
  • Going through audit written so far.
  • Can outline with headers. Or free-write. Or record yourself to start thinking and then transcribe.
  • Should we put in the Notion table
  • Having difficulty completing Audit Report section specifically

What are you planning to work on next?

• Schedule more time to collaboratively figure out report headings, structure and how the audit fits into that.

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting Notes: April 7, 2022

Follow-up on last week's to-dos

• Swast, Isabela and T meeting
  • Complete! Discussion follow-up
• Mars, Isabela to review, comment Swast's report
• Swast to continue writing rest of report
• Mentors to suggest a smaller, more feasible scope
• Mars to clean up notes with N, message N about anonymize
  • Not complete
• March 31 Meeting Notes conflict error
  • Mars to resolve

Discussion topics and Resources

Follow-up from meeting with T

• Very broad, went to many interesting questions
• A very different point of view and the report
• A lot can be explored in future
• Recognize limits of self-testing as abled person
• Where other platforms lacking in
• Accessibility is something people talk about, agree, but not consider when building platform from beginning
• Give the readers not just resources, but also empathy
• Maybe best practices -> questions

Outline- What about Best Practices Section

• New document by Swast. Best Practices for Accessible Real-Time Collaboration - Draft
• The Audit Report Draft will fit under the n new document
• Write a little more, make comments
• Started internship brief, we aimed for 'Best Practices' but over course of internship, we realize maybe we don't have enough to write a Best Practices section
• Maybe the document can also be more exploratory. Leaving door open for future people to explore

Talking about the Mega Outline

• https://github.com/isabela-pf/internship/blob/main/weekly-updates/report-outline-collaboration.md
• Can link out
• Can remove section- remove Recommendations
• Does Next Steps seems feasible? Can be a bullet list
• User Stories- diagrams, while cool, take time. Could make a bullet point version.
• Remove 'Summary of Audit' section, since already discussed elsewhere

Blog post

• May not have time
• Isabela will check with Tania if blog post still wanted.

Timeline

April 11-12: Swast finish writing, submit
April 13: Isabela and Mars to review
April 14 meeting: Discuss changes to make
April 15-21: Swast to re-write, based on our review
April 21 meeting: Internship closing, any last-minute changes
April 22: Submission

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?
• Mars will be out on April 14.

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Will probably go as a markdown file in the weekly updates folder

Meeting topics:

Follow-up on last week's to-dos

• Audit Google Docs 8 user journeys for people using screen-readers
• Audit Google Docs 8 user journeys for people using keyboard commands
  • 8 User Journeys to audit
    • Opening a document from a file browser
    • Saving a document
    • Finding which user made an edit to a document in the past in the document history
    • Seeing comments
    • Responding to a comment
    • Editing a comment
    • Receiving notification of a user joining a document
    • Receiving notification of a user commenting

Updates from last week:

• Swast was able to do the keyboard audit but had some difficulty setting up a screen-reader
  • Leads to discussion point 'Accessing accessibility'
  • Swast: Also, isn't it another part of accessibility that installation of screen readers is also a tough process to go through? like shouldn't it be easier?
  • Isabela: Lots of assistive tech is not necessarily easy for people to access, ironically
• Celebrate the what went well!

Discussion topics and Resources:

• 'Accessing accessibility'
  • Because there's a variety of screen-readers, personal preference and programs compatible with screen-readers, there's a lot of different ways to access accessibility. Sometimes these conflict or don't work with each other.
  • Finances of accessibility.
  • 'Accessing accessibility' is important as well. It is higher up in the structural ladder of accessibility.
  • Accessing accessibility tools (installation, finances) -> Using compatible programs and websites -> RTC accessibility
  • However, we may not have sufficient time to explore or suggest solutions in this internship. We can acknowledge it, but focus on RTC accessibility specifically
• Structural problems with an RTC tools that keep re-appearing in a user journey.
  • Were there any re-occurring problems you noticed while doing the keyboard and screen-reader audits of Google Docs?
  • Possible to-do item related to this topic: "Explore/catalog all visual (and/or audio if relevant)-only information in the last RTC interface you audited. For example, in google docs the users currently in a document are listed in the upper right via profile picture and no other way. A lot of accessibility is making sure info isn't lost, so it'll be good to know what we're accounting for."

Potential to-do items:

• Explore/catalog all visual (and/or audio if relevant)-only information in the last RTC interface you audited. For example, in google docs the users currently in a document are listed in the upper right via profile picture and no other way. A lot of accessibility is making sure info isn't lost, so it'll be good to know what we're accounting for

What are you planning to work on next?

• Audit Google Docs 8 user journeys for people using screen-readers
• In each user journey, what are the reoccurring problems, such as information that cannot be easily accessed? eg for Keyboard Audit, 'Can see who is on the doc (tool bar), but cannot see where they are on the doc'. We can read the Notes column in Notion and see what problems repeat
• Start making a User Journey diagram, similar to the one Swast made with her Goodreads redesign project

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting topics

Follow-up on last week's to-dos

• Time tracking check
• Draft in review
  • Do audit report comments need to be moved over?
  • What other support is needed for some of those comments?
  • Tania to review as well this week
• Blog post
  • Not ready for review right now
  • More difficult to write than expected
• Timeline check

Discussion topics and Resources

• Image description links?
  • Example of alt-text for complex graphs
• Recommendation section feedback, as Swast requested
• sometimes a developer can, cannot control what different screen reader reads. Can try to control, eg with ARIA labels for websites
• Swast felt like missing something but not sure what, looked at notes from different users
• can be for different audiences (for audiences)
• Consistently writing in formal tone
• Organize Recommendations by feasibility
• User Interviews seperate or together with Methods?

Potential to-do items

• Schedule working meeting for image description, convert to markdown
• Schedule working meeting for contributions (get final work into PR, and blog into a PR)
  Wednesday: Isabela and Swast,
  Thursday: Isabela, Mars, Swast

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Anything else?

Meeting Notes: March 31, 2022

Follow-up on last week's to-dos

• Swast, Isabela and T upcoming meeting
  • Rescheduled to next week.
• Swast, Mars and N meeting
  • Complete! Discussion follow-up
• Swast to continue writing Audit Report
• Swast to see how she wants to write, add or remove the 'mega-outline'
• Isabela to convert and anonymize meeting notes with G
• Mars to anonymize meeting notes with E
  • Updated in #19. Ready for review or merging

Discussion topics and Resources

Follow-up from meeting with N

• How was it leading a user interview?
• Did Swast feel adequately prepared with mentor's help? Such as working together to create the Notion page 'Meeting Agenda with N' and linking to How to Conduct User Interviews.
• What was interesting or surprised you in the meeting?
• How we'll anonymize the information, as N said her conference organization work and work with L can be identifiable information.
  • We could keep that information in the private notes, and in the public notes only include N's experience with RTC tools.
  • Or we could keep the conference work (answer for Qn: How you make broad recommendations, such as accessibility for conferences, when disability and accessibility is so individual?) but ask N and L about if and how that part be cited
• Follow-up with N with decision before publishing public notes on Github
• Still need to be careful about anonymization- while can use initials, some people have more easily identifiable information. So may remove this information for public notes.

Swast, Isabela and T upcoming meeting

• To ask
  • What kind of information do you think will help you build more accessible RTC tools?
  • What tasks do you commonly do in a notebook? Which of these tasks do you want to collaborate on or how?
  • Skip auditing!
  • Add some more general collaboration questions

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?
• Mars will be out on April 14.

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting Notes: April 7, 2022

Follow-up on last week's to-dos

• Mars, Isabela to talk with Swast and review Best Practices for Accessible Real-Time Collaboration - Draft
• Isabela on if blog post is still necessary, based on current timeline

Discussion topics and Resources

Resources for inclusive writing style guides

• Isabela has complied resources here, in this Internship repository

Talking about report

• Discussion!

Revisiting the Mega Outline

• What sections of the report has changed? Based on the last meeting, we've agreed to remove some sections
  -Discussion from last meeting
  • https://github.com/isabela-pf/internship/blob/main/weekly-updates/report-outline-collaboration.md
  • Can link out
  • Can remove section- remove Recommendations
  • Does Next Steps seems feasible? Can be a bullet list
  • User Stories- diagrams, while cool, take time. Could make a bullet point version.
  • Remove 'Summary of Audit' section, since already discussed elsewhere

Timeline

April 11-12: Swast finish writing, submit
April 13: Isabela and Mars to review
April 14 meeting: Discuss changes to make
April 15-21: Swast to re-write, based on our review
April 21 meeting: Internship closing, any last-minute changes
April 22: Submission

Mars to rise from the grave

• Will check report later this week

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

I'm making this issue because we had a lot of support ideas needed at our last meeting and I don't want to lose them in my notes. Please feel free to ignore this issue unless you are @isabela-pf 🌻.

• Find potential screen reader collaborators (experience with different OS is ideal)
• Collect and describe some resources on making sure document types are accessible (to go to the resources directory).
• Collect and/or create some best practices example outlines
• Create a list of RTC applications to reference (so we can do more audits now that we have the pattern for one down)
• Research where keyboard shortcuts fit with accessibility. Yes people use them, but can they alone be considered accessible navigation (Isabela suspects not, but worth exploring further)?

Draft

Backing up claim of remote of work

• "work began remotely and hence there was an increase in demands of RTC. "
• maybe add a link/citation

Rephrasing heading 'Is everything really accessible out there?'

Internal vs External accessibility tools

Thinking of headers

• Current RTC accessibility options are insufficient
• Need for better RTC accessibility options
• Insufficient support of current RTC accessibility options

Due to insufficient RTC accessibility options, People are pushed to use external tools

People often want to use their own tools and workflows

• sometimes people prefer own tools, but want to integrate into RTC
• For example, with N interview, she likes using Mac Gestures, but cannot use them in Google Docs = frustrating
• RTC tool should allow for options
• Can follow WCAG guidelines for 'rubust'
• "Content must be robust enough that it can be interpreted by by a wide variety of user agents, including assistive technologies."

User Diagram

• Highlight what feels bad = the 👎 point
  • 'Screen-reader reads out too much minor details, feels overwhelming'
• Where to write the full information? Recommendations?
• Can write

Factor: Screen-readers reading out too many minor details instead of most important details

• when screen-readers read out too much, repeated information, poor user experience
• eg Google Doc comments
• screen-reader reading all HTML elements. Possibility-Developer add ARIA label to identify most important information that screen-reaader reads

How can we tell what a screen-reader will read out?

How to represent useful information from our non-collaborative test volunteers?

user journey diagram - visual, helpful, summarize data we collected such as with NVDA and VoiceOver

interview - turn to user journey diagram? or a different diagram? or text as 'case study: using Google Docs with X'?

• anonymize concerns, don't want to put identifiable information

OR 'Key Takeaways for non-screen-reader accessibiltity'- talks about mac gestures and customization?

Meeting Notes: April 21, 2022

Follow-up on last week's to-dos

• Mars, Isabela to talk with Swast and review Best Practices for Accessible Real-Time Collaboration - Draft

Discussion topics and Resources

Possibility of extending internship by 3 weeks

• Tania, Ashley (HR) already have this in place- depends of Swast would like to take it
• Swast let us know if she would like to take it
• If so, additional time would give more time
  • Swast to write report
  • Mentors to review report
  • Swast to re-write report, based on feedback
  • Swast to write a blog post.

Possibility of closing of internship

• Any final steps
• Uploading the report onto this internship repository

Talking about report

• Discussion!

Revisiting the Mega Outline

• What sections of the report has changed? Based on the last meeting, we've agreed to remove some sections
  -Discussion from last meeting
  • https://github.com/isabela-pf/internship/blob/main/weekly-updates/report-outline-collaboration.md
  • Can link out
  • Can remove section- remove Recommendations
  • Does Next Steps seems feasible? Can be a bullet list
  • User Stories- diagrams, while cool, take time. Could make a bullet point version.
  • Remove 'Summary of Audit' section, since already discussed elsewhere

Timeline

April 11-12: Swast finish writing, submit
April 13: Isabela and Mars to review
April 14 meeting: Discuss changes to make
April 15-21: Swast to re-write, based on our review
April 21 meeting: Internship closing, any last-minute changes
April 22: Submission? Or extension to May 13.

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting topics:

Follow-up on last week's to-dos

• Start writing the outline or first draft of the report
• Can be shared on Notion, where Swast's previous notes are

Updates from last week:

• Isabela's To-Dos based on last week's discussions
  • Find potential screen reader collaborators (experience with different OS is ideal)
  • Collect and describe some resources on making sure document types are accessible (to go to the resources directory).
  • Collect and/or create some best practices example outlines
  • Create a list of RTC applications to reference (so we can do more audits now that we have the pattern for one down)
  • Research where keyboard shortcuts fit with accessibility. Yes people use them, but can they alone be considered accessible navigation (Isabela suspects not, but worth exploring further)?

Discussion topics and Resources:

• Outline examples

Potential to-do items:

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting topics:

Follow-up on last week's to-dos

1. Audit Google Docs 8 user journeys for people using screen-readers
   • 8 User Journeys to audit
     • Opening a document from a file browser
     • Saving a document
     • Finding which user made an edit to a document in the past in the document history
     • Seeing comments
     • Responding to a comment
     • Editing a comment
     • Receiving notification of a user joining a document
     • Receiving notification of a user commenting
2. Catalog what information cannot be accessed in each user journey
   • After completing the screen-reader audit: catalog all visual-only information in Google Docs
     • For example, in Google Docs the users currently in a document are listed in the upper right via profile picture and no other way. A lot of accessibility is making sure info isn't lost, so it'll be good to know what we're accounting for.
   • After completing the keyboard audit: catalog all mouse-only information in Google Docs.
     • For example, for the Keyboard Audit, in the 'Notes' column, there is 'Can see who is on the doc (tool bar), but cannot see where they are on the doc'. Is seeing other users a re-occurring problem for keyboard accessibility?
   • We can find this information by reading the 'Notes' column in the Notion table and see what problems re-occur
3. Start making a User Journey diagram, similar to the one Swast made with her Goodreads redesign project
   • Does not need to be complete by next week.
   • Will be a useful document in the final write-u

Updates from last week:

• Celebrate the what went well!

Discussion topics and Resources:

• Maybe discuss more on other assistive tech than screen readers

Potential to-do items:

• Sort through WCAG (check if link is correct) standards and label them as RTC problems and Independent of RTC so we can scope some accessibility areas we are not worried about

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting Notes: May 6, 2022

Follow-up on last week's to-dos

• Mars, Isabela to talk with Swast and review Best Practices for Accessible Real-Time Collaboration - Draft

Discussion topics and Resources

Exams over! Woo!

Last week's timesheet

• Need to edit and resubmit as PTO

Extended internship by 3 weeks

• New end date: May 21 2022, 3 Saturdays from now

New Timeline

April 21: Previous meeting
April 21-April 30: Exams
May 6: This meeting
May 8: Swast to release new draft
May 9-13: Mentors, Tania to review. Swast to write a blog post
May 13: All reviews submitted
May 14-18: Swast to re-write, edit based on feedback
May 18-20: Buffer, conversion from Notion to Markdown, write alt-text
May 20: Final Submission
May 21: End of internship

Slack channel to end May 21st, Saturday at

• 9AM (Isabela)
• 12:00 PM (Mars)
• 9:30PM (Swast)

Additional time would give more time

• Swast to write report (3-4 days)
• Mentors, Tania to review report
  • Tania will need some additional turn-around time, so account for that as well
• Swast to re-write report, based on feedback (3-4 days)
• Swast to write a blog post?
  • Can be written in the review period, while waiting for mentors and Tania to review
  • List of previous Quansight Internship 2021 blog posts
  • Lower stress, not reviewed like the report. Can be fun, free form
  • Some people may review blog post: Isabela, Mars, Ralf

Updates to the report

• Recommendation section

  • General? Or for specific audience eg Recommendations for designers vs Recommendations for developers
  • Write Recommendations list, see how many are specific vs general, go from there
  • Using audit as proof in Recommendation of what to do, not to do.
  • 'These recommendations are based on the audits and research conducted. Click on the link to see the source'
  • Formatting
    • Being very direct, brief summary, bullet point style
    • Linking vs not linking to audit.
    • Linking can be sufficient. Similar to a citation or WCAG recommendations.
    • Don't need to explain fully after each bullet point

• Represent data at tables

  • Example, template from previous meeting

• Alt-text for diagrams

  • Will get help writing alt-text for more complex images soon

• Previous discussion about removing, adding sections based on Mega Outline

  • https://github.com/isabela-pf/internship/blob/main/weekly-updates/report-outline-collaboration.md
  • Can link out
  • Can remove section- remove Recommendations? Or change
  • Does Next Steps seems feasible? Can be a bullet list
  • User Stories- diagrams, while cool, take time. Could make a bullet point version.
  • Remove 'Summary of Audit' section, since already discussed elsewhere

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting topics: Narrowing scope and talking about best practices documents

Updates from last week:

• Audit Google Docs using the 10 tests from this article, 'Quick accessibility tests anyone can do'
• Sort through WCAG standards and label them as RTC problems and Independent of RTC so we can scope some accessibility areas we are not worried about
• Celebrate the what went well!

Discussion/resource topics:

• What do different best practices documents look like/how are the organized/what do they include? We can refer to 'How to write a Best Practices Document', which is in this repository.

Potential to-do items:

• Make a list of very specific tasks people could want to do in an RTC document. This could be anything simple (like opening a document from a file browser) to something more complex (like finding which user made an edit to a document in the past).
  • We've decided to move forward with this task
• Explore/catalog all visual (and/or audio if relevant)-only information in the last RTC interface you audited. For example, in google docs the users currently in a document are listed in the upper right via profile picture and no other way. A lot of accessibility is making sure info isn't lost, so it'll be good to know what we're accounting for.
  • We may talk about this next week. Structural problems with an RTC tools that keep re-appearing in a user journey

What are you planning to work on next?

• Audit Google Docs 8 user journeys for people using screen-readers
• Audit Google Docs 8 user journeys for people using keyboard commands

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?
• Defining tasks for next week in a collaborative hack.md docuemnt

Meeting topics:

Follow-up on last week's to-dos

• Continue making outline of report
  • Figma files of the 5 outlines
• Ask for feedback on outline from
  • Isabela, Mars, Tony Fast, Gabriel Fouasnon
• Continue creating User Journey diagrams

Discussion topics and Resources

• Some uncertainty how and when to schedule feedback sessions

Potential to-do items

• Let's sort out scheduling with supporters!

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Meeting Notes: to be added

Mac, VoiceOver

Eric:
Audit Jupyter first, then audit Jupter RTC

Adding layers of complexity, interested in making Jupyter React with Slate accessible RTC, JupyterLab will not be accessible

Running local Jupyter, run voiceover
Command f5 to turn on and off

Setup takes time
Doesn't seem to exit easily

Not comment

Share a document:
Right click a file, Copy shareable link, share link
Authorize share token

Keyboard shortcut for right click:
Ctrl + Option, Shift M

Cmd f5
Tabbing, cannot focus in file directory
Going down file directory, VoiceOVer reads out long Name: Not good user experience

Ctrl + Option, Shift M
Arrow Down'
You are currently in menu, press enter
Launch a new anonymous browser, paste Shareable Link Link

Maybe try keyboard first

• Specific keyboard commands, repeat alone, can meet again, show again, can record

We try Jupyter, install extension for comments (calpoly comments,
old: [https://github.com/jupyterlab/jupyterlab-commenting](https://github.com/jupyterlab/jupyterlab-commenting)

new: RTC: https://github.com/jupytercalpoly/jupyterlab-comments

people would leave in-line comments

Would know Aria tags to put in, first step

Eric, going down file tree of Jupyter, every time reading out call details,

If you have a tree or list, screen-reader customize how much read

Developers love patterns. UI patterns, code patterns, design systems
Don't know how VoiceOver works, until tests- VoiceOver patterns, could be later in development cycle

Sooner your know, easier to implement
As a developer, need to know which details will be spoken by voiceover, filename only or creation date or status
Give option, shortcut to get more details

Developer don't know about VoiceOver verbosity, a few known readers like NVDA,
Google Docs
How does Verbosity work with JupyterLab
Like how an app may work differently in Android and iOS

Understand for common ground for all products

Qn 2
Why would developers look at this report?
Make button, affects screen-reader

Add Aria label, type (folder, file)
Folder- Analysis

Be interested in overview of content without getting too much information

Notebook
Developers used to keyboard, culturally, but not voiceover

Meeting topics:

Follow-up on last week's to-dos

• How the meeting with G went
  • Successfully completed all tasks
  • Find out what G or developers would like from the best practices section of the report
  • Interesting to hear NVDA. Both VoiceOver and NVDA access same information, but announce, priortize and work differently
  • eg NVDA action state first. VoiceOver action state at end
  • Is action more important? Was it because NVDA was developed by blind developers? We don't know who the VoiceOver developers are and their POV
  • Was not recorded.
• Upload the notes from meeting with G this week to the internship repo?
  • Any changes to make before it becomes public?
  • No, can make public now.
• Mars to access Swast's Meeting Agenda for interview with N
  • Link to private note in Slack

Discussion topics and Resources

• How to anonymize data collected from this user research

  • We are 'working in the open' with our internship repository, so the meeting notes are public.
  • We should have a process where
    • Have explicit consent from the volunteer that they are okay having their name (or any other potential identifying factors) in these public notes and/or
    • have a process where we remove names prior to having them on github
  • specific questions to ask in beginning
    • example script. More formal than our case.
    • Use cases:
      • public but anonymized
      • public but not anonymized
      • shared internally and anonymized
      • shared internally and not anonymized, shred with relevant team members
    • Other factors to consider for future best practice: interviewing people in Europe so there is EU General Data Protection Regulation (GDPR). Full control of personal information but can at odds with Github's version control (cannot change past)
    • In report, can say 'a developer who has worked on open-source projects'. But not specify too much that would give away identity

• Preparing for meeting with T later today

  • Can ask about recording
  • JupyterLab environment with RTC, extensions such as video chat
  • Are there any actions we could compare?
  • What kind of information do you think will help you build more accessible RTC tools?
  • What tasks do you commonly do in a notebook? Which of these tasks do you want to collaborate on or how?
  • Skip auditing!
  • Add some more general collaboration questions

• Preparing for meeting with N tomorrow

What are you planning to work on next?

• Swast to continue writing Audit Report
• Swast to see how she wants to write, add or remove the 'mega-outline'
• Swast, Isabela and T upcoming meeting
• Swast, Mars and N upcoming meeting
• Isabela to convert and anonymize meeting notes with G
• Mars to anonymize meeting notes with E

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

Because we are using issues for notes, it may be worth making a formal issue template out of the agenda template file so that it can appear automatically in the notes.

This is a small thing for sure, so I'm making this issue as a reminder more than an immediate to do.