jooyoungseo / assets2023_vscode Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 6.62 MB

Manuscript repo for experience report submitted to the ACM ASSETS 2023

TeX 99.22% Lua 0.76% SCSS 0.01%

assets2023_vscode's People

Contributors

Watchers

assets2023_vscode's Issues

Add ACM CCS

I need to add ACM CCS before this submission:

assets2023_vscode/_quarto.yml

Lines 77 to 108 in f98bba8

 # The code below is generated by the tool at http://dl.acm.org/ccs.cfm. 

 # Please copy and paste the code instead of the example below. 

 ccs: | 

  \begin{CCSXML} 

  <ccs2012> 

  <concept> 

  <concept_id>10010520.10010553.10010562</concept_id> 

  <concept_desc>Computer systems organization~Embedded systems</concept_desc> 

  <concept_significance>500</concept_significance> 

  </concept> 

  <concept> 

  <concept_id>10010520.10010575.10010755</concept_id> 

  <concept_desc>Computer systems organization~Redundancy</concept_desc> 

  <concept_significance>300</concept_significance> 

  </concept> 

  <concept> 

  <concept_id>10010520.10010553.10010554</concept_id> 

  <concept_desc>Computer systems organization~Robotics</concept_desc> 

  <concept_significance>100</concept_significance> 

  </concept> 

  <concept> 

  <concept_id>10003033.10003083.10003095</concept_id> 

  <concept_desc>Networks~Network reliability</concept_desc> 

  <concept_significance>100</concept_significance> 

  </concept> 

  </ccs2012> 

  \end{CCSXML} 

  \ccsdesc[500]{Computer systems organization~Embedded systems} 

  \ccsdesc[300]{Computer systems organization~Redundancy} 

  \ccsdesc{Computer systems organization~Robotics} 

  \ccsdesc[100]{Networks~Network reliability}

consider adding deepdive

we might want to include the deep dive, though it does contain some redundant information.

The video file is quite large and I was unable to upload it when I tried to.

Add author info

@meganrogge

Please add author info:

assets2023_vscode/assets2023_vscode.qmd

Lines 26 to 34 in b1af0c8

	- name: G.K.M. Tobin
	email: [email protected]
	affiliation:
	name: Institute for Clarity in Documentation
	address: P.O. Box 1212
	city: Dublin
	state: Ohio
	country: USA
	postal-code: 43017-6221

I don't mind taking the second authorship. :) Let's see how it goes later.

Add citations

I will take care of adding citations later.

Add brief thank-you reasons

In the Acknowledgement section, Currently, we have a list of individuals' names, but I was wonderinf if you would mind adding more context like this:

We thank John for his help with yy, and Smith for his advice and contribution for zz ...

assets2023_vscode/assets2023_vscode.qmd

Lines 107 to 115 in f45d358

 We thank ... 

 - Isidor Nikolic 

 - Kai Maetzel 

 - Daniel Imms 

 - Raymond Zhao 

 - Roberto Perez 

 - José Vilmar Estácio de Souza 

 - VS Code team 

 - Amnon Freidlin

Collect GitHub data

Need to collect GitHub issues, PRs, comments, and mentions related to our paper to properly cite.

Add bio

@meganrogge

Please share your bio with readers:

assets2023_vscode/assets2023_vscode.qmd

Lines 136 to 137 in 369c6ca

	* About Megan

Fix appendix section

Later I will need to fix the appendix section according to the format guidelines.

Write more takeaways

Following reviewers' feedback, we may want to include some more detailed takeaways of our paper in the Discussion section for the ASSETS community. For example:

Accessibility action research (our role as accessibility activists beyond conceptual or technical level).
Opportunities and challenges of improving accessibility within the open-source ecosystem, and its implication that can be applied to other open-source projects.

Opportunities: openness/transparency and direct end-user feedback in the dev cycle and iteration. @jooyoungseo was not employed by Microsoft, but could play an insider role and was able to closely work with the product engineers, including @meganrogge.
Challenges: The democratic nature could threaten the fundamental accessibility if not enough people express their needs. Since the users' feedback and bug report are critical in open-source ecosystem, the project could unintentionally neglect under-represented group's voice. Sometimes, due to the small number of users' feedback, criticality of accessibility features are under-estimated. Communication channels or methods themselves could become another accessibility hurdle (e.g., not all people are familiar with GitHub issue reporting and the process may be daunting to some end-users who may otherwise be able to provide constructive feedback).

Recommendation: Open-source team's empathy for the importance of accessibility is critical. Listen carefully to any small number of feedback from under-represented groups. If possible, build a rapport with the community and identify someone who can co-design the iterative accessibility improvement.

Version info for terminal buffer

It would be greatly appreciated if you could identify the version number of the VSCode stable version that introduced the accessible terminal buffer and replace xx with the exact version:

assets2023_vscode/assets2023_vscode.qmd

Line 50 in f98bba8

 More specifically, he proposed replacing the terminal output with a text editor buffer that allowed for standard arrow-key navigation. This process took over a year and a lot of technical trial and error and collaborative testing. For example, we started with a remarkup to redirect the terminal output web container, which was initially designated as "list", to the aria "document" or "textbox" landmarks, but were unable to achieve satisfactory results due to varying levels of screen reader and platform support for aria. Next, we remodeled the terminal output into a text area with "contenteditable" and "readonly" attributes, but this was not very compatible with the screen reader's speech buffer. Finally, we created a separate accessible terminal buffer by passing the terminal output to VSCode's native Monaco editor, which is guaranteed accessible, leading to a successful feature that ensures satisfactory accessibility and usability on any operating system or screen reader. This terminal buffer feature was officially released in VSCode stable version xx and has been very well received by many users in the Program-L community. 

Additional thank you

If accepted, additional thank you could be extended to Gino Scarpio.

Incorrect pronouns

I have just come across some incorrect pronouns in our paper, such as (JooYoung's pronoun: her instead of him):

assets2023_vscode/assets2023_vscode.qmd

Lines 58 to 59 in 62a0cea

 JooYoung had several Zoom meetings with Megan and Amnon Freidlin (Microsoft's sound designer), and through an iterative process, finalized the three audio cues used in the `git diff` context. These were the diff line Inserted sound, which is heard when something new is added (+), the diff line Deleted sound, which is heard when something existing is removed (-), and the diff line Modified sound, which is heard when something existing is modified (+-, -+). Our success came with some trial and error. For example, an early problem was that the Diff Line Inserted and Diff Line Deleted sounds had a similar range and texture, making it difficult to distinguish between them. JooYoung realized that this was a common complaint in Program-L beyond her personal experience, so she worked with the sound designer to test and finalize a sample file that was as self-explanatory as possible and didn't interfere with the sound of screen reader speech. Of course, we had to leave the potential issue of the static audio cues we chose not being able to adequately accommodate users with hearing impairments in certain ranges as a future work in progress, but this feature greatly improved the usability of our non-visual programming.

If accepted, we need to thoroughly review our paper again for final submission.

Add reflections and suggestions

I will also add mine. Please add yours at:

assets2023_vscode/assets2023_vscode.qmd

Lines 204 to 209 in c35a631

 # Discussion and Conclusion 

 * Reflection on what we have learned from this collaboration. 

 * What we recommend for other open-source communities for better accessibility.

Consider adding some figures or screenshots

We may want to include some screenshots that can demonstrate some of the features that we introduce in the paper. For screen reader speech output, we can capture VoiceOver caption panel.

Supplementary video

Following the reviewers' feedback, we may want to create a supplementary video that can demonstrate our experience and collaborative co-design deliverables.

Use pronouns

Thanks for doing the acknowledgements section! If you have time, please fix "your" with their specific prounouns, such as "thank for his xxx, her yy":

assets2023_vscode/assets2023_vscode.qmd

Lines 107 to 108 in 875089b

 We thank ... 

 - Isidor Nikolic for driving accessibility initiatives

VSCode and A11y commitment history

@meganrogge

It would be greatly appreciated if you could write the following section:

assets2023_vscode/assets2023_vscode.qmd

Lines 126 to 130 in 1c7eb12

 ## Visual Studio Code and Accessibility 

 * Brief history of VSCode 

 * How accessibility commitment got started

Make alt text more informative

It would be even nicer if we could make the alt text of our figures more informative and understandable. For example, "A screenshot of terminal buffer showing xxx."

Complete acknowledgements

@meganrogge

Please shout out to VSCode team and anyone we need to thank:

assets2023_vscode/assets2023_vscode.qmd

Lines 162 to 163 in 369c6ca

 We thank ... 

 :::

Create an accessible paper link

Once this paper is ready for submission, I need to create this repo as a public and make an accessible link:

https://github.com/jooyoungseo/assets2023_vscode/blob/f98bba85469ce5a5db401bdfbfd4cd4f3095b3df/_quarto.yml#L124-L125

	# The code below is generated by the tool at http://dl.acm.org/ccs.cfm.
	# Please copy and paste the code instead of the example below.
	ccs: \|
	\begin{CCSXML}
	<ccs2012>
	<concept>
	<concept_id>10010520.10010553.10010562</concept_id>
	<concept_desc>Computer systems organization~Embedded systems</concept_desc>
	<concept_significance>500</concept_significance>
	</concept>
	<concept>
	<concept_id>10010520.10010575.10010755</concept_id>
	<concept_desc>Computer systems organization~Redundancy</concept_desc>
	<concept_significance>300</concept_significance>
	</concept>
	<concept>
	<concept_id>10010520.10010553.10010554</concept_id>
	<concept_desc>Computer systems organization~Robotics</concept_desc>
	<concept_significance>100</concept_significance>
	</concept>
	<concept>
	<concept_id>10003033.10003083.10003095</concept_id>
	<concept_desc>Networks~Network reliability</concept_desc>
	<concept_significance>100</concept_significance>
	</concept>
	</ccs2012>
	\end{CCSXML}

	\ccsdesc[500]{Computer systems organization~Embedded systems}
	\ccsdesc[300]{Computer systems organization~Redundancy}
	\ccsdesc{Computer systems organization~Robotics}
	\ccsdesc[100]{Networks~Network reliability}

	We thank ...
	- Isidor Nikolic
	- Kai Maetzel
	- Daniel Imms
	- Raymond Zhao
	- Roberto Perez
	- José Vilmar Estácio de Souza
	- VS Code team
	- Amnon Freidlin

	# Discussion and Conclusion

	* Reflection on what we have learned from this collaboration.

	* What we recommend for other open-source communities for better accessibility.

	We thank ...
	- Isidor Nikolic for driving accessibility initiatives

	## Visual Studio Code and Accessibility

	* Brief history of VSCode

	* How accessibility commitment got started

jooyoungseo / assets2023_vscode Goto Github PK

assets2023_vscode's People

Contributors

Watchers

assets2023_vscode's Issues

Recommend Projects

Recommend Topics

Recommend Org