From 3735fb41eefffde3b911292bbd9e9b1a6c133779 Mon Sep 17 00:00:00 2001
From: Jennifer Mankoff <jmankoff@cs.washington.edu>
Date: Fri, 2 Dec 2022 20:58:33 -0800
Subject: [PATCH] cleaning up of things not needed; etc
---
_config_production.yml | 2 +-
_includes/navigation.html | 2 +-
assignments/accessibility.md | 232 ------------------
assignments/consent.md | 42 ----
...deo-image.md => describing-video-image.md} | 0
...abilityjustice.md => disabilityjustice.md} | 0
...essibility.md => finding-accessibility.md} | 0
assignments/hw0-learninggoals.md | 31 ---
assignments/hw1-nvda.md | 105 --------
assignments/hw2-soundRecognition.md | 42 ----
assignments/{accessibility-img => img}/1.png | Bin
.../androidview.png | Bin
.../{accessibility-img => img}/avd.png | Bin
.../mdnavigator1.png | Bin
.../mdnavigator2.png | Bin
.../mdnavigator3.png | Bin
.../mdnavigator4.png | Bin
.../playstoreemulator.png | Bin
.../projectview.png | Bin
19 files changed, 2 insertions(+), 454 deletions(-)
delete mode 100644 assignments/accessibility.md
delete mode 100644 assignments/consent.md
rename assignments/{act3-describing-video-image.md => describing-video-image.md} (100%)
rename assignments/{hw0-disabilityjustice.md => disabilityjustice.md} (100%)
rename assignments/{act1-finding-accessibility.md => finding-accessibility.md} (100%)
delete mode 100644 assignments/hw0-learninggoals.md
delete mode 100644 assignments/hw1-nvda.md
delete mode 100644 assignments/hw2-soundRecognition.md
rename assignments/{accessibility-img => img}/1.png (100%)
rename assignments/{accessibility-img => img}/androidview.png (100%)
rename assignments/{accessibility-img => img}/avd.png (100%)
rename assignments/{accessibility-img => img}/mdnavigator1.png (100%)
rename assignments/{accessibility-img => img}/mdnavigator2.png (100%)
rename assignments/{accessibility-img => img}/mdnavigator3.png (100%)
rename assignments/{accessibility-img => img}/mdnavigator4.png (100%)
rename assignments/{accessibility-img => img}/playstoreemulator.png (100%)
rename assignments/{accessibility-img => img}/projectview.png (100%)
diff --git a/_config_production.yml b/_config_production.yml
index f9af1685..ad91fcae 100644
--- a/_config_production.yml
+++ b/_config_production.yml
@@ -22,7 +22,7 @@ paginate: 5
quarter: "Winter 2023"
classnum: "CSEP 590a"
copydate: "3/30/20"
-status: final
+status: draft
warning: old
author:
diff --git a/_includes/navigation.html b/_includes/navigation.html
index 82a32719..ea1e2126 100644
--- a/_includes/navigation.html
+++ b/_includes/navigation.html
@@ -1,4 +1,4 @@
-q<!-- Much of this code copied from pdarragh at https://gist.github.com/pdarragh/c7ca120604c1a1d8b8de -->
+<!-- Much of this code copied from pdarragh at https://gist.github.com/pdarragh/c7ca120604c1a1d8b8de -->
{% for entry in site.data.navigation %}
{% if entry.url == "canvas" %}
diff --git a/assignments/accessibility.md b/assignments/accessibility.md
deleted file mode 100644
index 69630ce7..00000000
--- a/assignments/accessibility.md
+++ /dev/null
@@ -1,232 +0,0 @@
----
-layout: assignment
-published: true
-
-title: Accessibility
-code: as3
-
-assigned: April 22, 2020
-due:
- - <strong>Due</strong> April 30, 2020, 10:00pm
- - <strong>Lock</strong> May 2, 2020, 10:00pm
-
-revised: 10:00 PM Tuesday, April 21st, 2020
-
-objective: Identify and repair app accessibility issues.
-
-android_goals:
- - Basics of Android assistive tools
-hci_goals:
- - Explore App accessibility
- - Understanding the impact of different accessibility issues
- - Simple repairs to accessibility issues
- - Write up a report on accessiblity issues
----
-
-* TOC
-{:toc}
-
-This assignment has two parts that are inter-related. Part 1 of this assignment involves finding
-all the accessibility problems in the code base for our toy camera app, a and documenting them,
-while in Part 2 of the assignment you will fix these problems. It will be important to iterate on this find/fix cycles as
-fixing one problem may uncover new ones. You will use a number of tools to find these issues,
-including but not limited to the Google Accessibility Scanner and TalkBack. It will be important
-for you to experience the app through the use of a screen reader to find all of the problems
-a user might encounter.
-
-# GitGrade links
-
-**Classroom** [Summary](https://gitgrade.cs.washington.edu/student/summary/8723)
-
-**Links:** [Accept the Assignment](https://gitgrade.cs.washington.edu/student/assignment/122) / [Turn-in the Assignment](https://gitgrade.cs.washington.edu/student/assignment/122/turnin)
-
-# Part 1
-
-Tasks:
-- Learn different categories of app accessibility issues
-- Identify accessibility issues in our example app
-- Write a detailed report as a communication tool to developers who need to make the app accessible
-
-Accessibility is an important part of any app. Whether you are developing a new app or adding features
-to an existing one, it is important to consider the accessibility of your app's components.
-
-For some background you will want to do the following:
-
-- Start by watching this [quick video](https://youtu.be/1by5J7c5Vz4) to learn how visually-impaired
-users interact with Android applications. The video also offers some tips on ensuring your app is
-compatible with assistive tools.
-- Next read the list of errors that are found by Google's accessibility Scanner which is
-show in Table 2 on the 8th page of the PDF (which is numbered page 9) of
-[Epidemiology as a Framework for Large-Scale Mobile Application Accessibility Assessment](https://xiaoyizhang.me/assets/Paper/ASSETS_2017_Epidemiology.pdf).
-- Finally, because it is important to write succinct and yet descriptive alt text (content descriptions), you
-should read about [proper alt text writing](https://webaim.org/techniques/alttext/).
-
-For example, consider this view of the Layout Inspector of the layout app that we recently completed.
-(You will not be using your layout code for this assignment, we are using it for illustrative
-purposes here.) The selected image in the upper left of the screen does not have
-`contentDescription` property. **Google's Accessibility Scanner** will classify this as
-"Item Label" error (defined in the paper above), which will also mean a screen reader cannot
-read the alternative text of the image to people with visual impairments.
-
-{:width="500px"}
-
-The goal of Part 1 of the assignment is to identify **at least 10** accessibility issues in the app
-you will be given, **at least one** can't be found with the Accessibility Scanner. All of
-the issues listed in the ASSETS/Epidemiology paper may NOT be represented in the app, but you should be aware
-that they could be found in other apps. For your reference, we identified at least 12 errors in the app.
-
-## Setup
-In order to proceed you will need to setup your device and your Android Studio IDE.
-
-### Adding Markdown Viewing in Android Studio
-You will be writing your report in "Markdown." Markdown is a a text markup language that
-allows for simple formatting using plain text files. We have provided you with a `Part1.md` starter
-file that is in the root directory of your the repository you received when you accessed the
-assignment.
-
-You can edit your markdown file in any text editor, including Android Studio. We recommend you install
-the [Markdown Navigator](https://plugins.jetbrains.com/plugin/7896-markdown-navigator-enhanced) to help
-you preview your edits. (Click on the pictures to see a larger version)
-
-[{:width="250px"}](accessibility-img/mdnavigator1.png)
-[{:width="250px"}](accessibility-img/mdnavigator2.png)
-[{:width="250px"}](accessibility-img/mdnavigator3.png)
-
-Once you have the Markdown Navigator installed, open up `Part1.md` and click the button pointed to
-by the arrow in the following image to bring up the Markdown Preview pane.
-
-{:width="500px"}
-
-### Installing Accessibility Scanner
-
-You must first install the Accessibility scanner on your Android Device or in your Emulator using the
-Google Play store. IMPORTANT: The Pixel 2 XL Emulator does NOT have the Google Play store on it,
-so you have to start by installing the Pixel 2 or other Emulator where you can also install the Play Store
-using the *Tools->AVD Manager*. The best way to determine if the Emulator has the Play Store
-is to look for the icon under the Play Store column in the AVD Manager.
-
-{:width="300px"}
-
-To create another emulator, press the *Create Virtual Device* button, then find an emulator that has
-the Play Store icon in the Play Store column. Click Next and follow the instructions for the rest of the installation.
-
-{:width="500px"}
-
-Note that you will have to specifically choose this new emulator (as opposed to the one you were
-using before) when you are running your application on the emulator through Android Studio.
-
-To install the Accessibility Scanner, search for it in the Play Store and install it on your device or emulator.
-The installation process will be the same for a physical phone or the emulator equipt with the Play Store.
-Follow the instructions on the
-[Getting started with Google Accessibility Scanner](https://support.google.com/accessibility/android/answer/6376570?hl=en&ref_topic=6376582)
-page to get the scanner working on your device.
-
-Another option is to install the Android Accessibility Suite which contains both the Accessibility
-Scanner and TalkBack if it has not been installed before.
-
-### Installing TalkBack
-
-You will need to have a good understanding of how to set up and use
-[Talkback](https://support.google.com/accessibility/android/answer/6283677?hl=en) one
-of the assistive tools built-in to you Android. You may want to try using
-talk back on another application before you use it on the app you are given for this assignment.
-
-
-### Other Tools
-
-Another built-in assistive tool is [Switch Access](https://support.google.com/accessibility/android/answer/6122836?hl=en),
-which you may choose to set up and use.
-
-## Writing the report.
-
-Use the Accessibility Scanner, Talkback, and perhaps other tools to detect defects in our toy camera app.
-The Accessibility Scanner is decent with suggested fixes to problems it finds, however, some solutions
-are not obvious for each screen element type, so you will have to do some research to
-find all of the attributes that help to make an application more accessible. It may also help
-to use other tools (such as the Layout Inspector in Android) to help you track down the location
-of the issue the Accessibility tools find.
-
-As you find issues in the app, write them up in your report. Your report structure will contain
-two sections, an Overview in which you will describe your experience using assistive tools while testing the
-accessibility of the app before and after fixing issues, and a "table" of issues you found
-and how you fixed them. The outline of this report is given to you in `Part1.md` which remember is
-in the root directory of your the repository you received when you accessed the
-assignment. To open this file you can either use the _File->Open_ menu item, or change the _Android_
-drop down above the `app` folder to say _Project_ and double click on `Part1.md` from there.
-
-
-{:width="200px"}
-{:width="200px"}
-
-
-For each issue you identify within the app, document the following details:
-- The XML id of the item that needs to be fixed. If there is no id you can describe it briefly (~3 words)
-- The issue type as drawn from the list in ASSETS/Epidemiology paper.
-- The fix should provide a brief description (1 sentence or so) of what you did. If the fix involves
-changing or adding alt text, you should include the alt text you added for each inaccessible UI element in your
-fix description.
-- The file or files in which you fixed this issue
-- The line number(s) where you fixed this issue
-
-An example issue is shown in the `Part1.md` file. *Please* retain the two spaces at the end
-of every line so the line breaks will be maintained
-([examples](https://gist.github.com/shaunlebron/746476e6e7a4d698b373)). This will help the staff
-in grading your assignment.
-
------- Sample Issue ------
-*Id*: @+id/edit
-*Issue*: Item Type Label contains unnecessary text
-*Fix*: Remove the word "button" from the text description
-*File*: string.xml
-*Line number*: 11
-
-**Resources**
-
-- [Android Accessibility Overview](https://developer.android.com/guide/topics/ui/accessibility/)
-- [Android Accessibility Guides](https://developer.android.com/guide/topics/ui/accessibility/apps)
-- [Material Design: Assistive Technology](https://material.io/design/usability/accessibility.html#assistive-technology)
-
-
-# Part 2
-
-Tasks:
-
-- Repair accessibility issues you identified in part 1, including the sample issue
-
-For each issue that you identified in the app, please repair it by modifying code or XML layout file.
-You must also repair the sample issue that we have identified but not yet fixed in the code.
-For reference, in the sample solution we ran the app through the Accessibility Scanner and
-identified and fixed at least 12 issues (including the one we identified).
-
-For any repairs involving strings, please add a new entry for the fix into the strings.xml file,
-and then reference it (thereby retaining the old entry in the file). Recall that you can reference
-a string by changing the `contentDescription` property in the
-layout editor, or calling the equivalent method (`imageView.setContentDescription(...)`)
-
-All of these changes only require modifying existing XML attributes or adding new ones;
-or changing a line or two of code.
-
-# Turn-in
-
-## Submission Instructions
-
-You will turn in both Part 1 and Part 2 via GitGrade. The files you will need to include are:
-
-```
-- Part1.md
-- MainActivity.java
-- app_bar_main.xml
-- content_main.xml
-- nav_header_main.xml
-- strings.xml
-- colors.xml
-```
-
-## Grading (25pts)
-
-- Part 1
- - Description of the experience using assistive tools to test the app (Accessibility Scanner, TalkBack etc.): 3 pts
- - Correctly documents all 10 or more accessibility issues including location of the fix: 10 pts
-- Part 2
- - Fixes the issues identified in part 1 by modifying / adding new attributes to the xml tags: 10 pts
- - Updated content descriptions are correct per Webaim's guidelines: 2 pts
diff --git a/assignments/consent.md b/assignments/consent.md
deleted file mode 100644
index 0d0ed84f..00000000
--- a/assignments/consent.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-layout: default
----
-
-# Consent Form for CSE340
-
-Contact information for person running study: _[Fill in]_
-
-# Introduction and Purpose of study (Beneficience)
-
-_[Fill in: Write 1-2 sentences about what this study is about]_
-
-# Requirements for participation (Respect for Persons)
-
-To participate in this study you must be _[Fill in: Requirements (only age:
-must be 18 or older)]_
-
-# Study procedures (Respect for Persons)
-You will complete a series of menu selections during this study. You
-will need to click on 108 menus to complete the session as
-mentioned above. You should expect this to take approximately _[Fill
-in: X Minutes]_
-
-_[Fill in: Tell the participant if they will be compensated or not]_
-
-# Voluntary nature of Study (Respect for Persons)
-Your participation is voluntary and you can stop at any time without
-penalty. Your decision not to participate will not have an impact on _[Fill
-in: What might be coercive to the participant]_
-
-# Benefits of Study (Beneficience)
-This study will not directly benefit you. However, it will help us to
-understand _[Fill in]_
-
-# Contact (of IRB typically; Me in this case)
-If you have any concerns about this study, you can reach out to the
-Professor in charge, {{site.author.name}}, bricker [at] uw.edu
-
-# Written Consent
-
-To affirm your consent to participate in this study, please fill out the following form
-[https://bit.ly/20sp-Menus-Consent](https://bit.ly/20sp-Menus-Consent).
diff --git a/assignments/act3-describing-video-image.md b/assignments/describing-video-image.md
similarity index 100%
rename from assignments/act3-describing-video-image.md
rename to assignments/describing-video-image.md
diff --git a/assignments/hw0-disabilityjustice.md b/assignments/disabilityjustice.md
similarity index 100%
rename from assignments/hw0-disabilityjustice.md
rename to assignments/disabilityjustice.md
diff --git a/assignments/act1-finding-accessibility.md b/assignments/finding-accessibility.md
similarity index 100%
rename from assignments/act1-finding-accessibility.md
rename to assignments/finding-accessibility.md
diff --git a/assignments/hw0-learninggoals.md b/assignments/hw0-learninggoals.md
deleted file mode 100644
index 7e35ae62..00000000
--- a/assignments/hw0-learninggoals.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-layout: assignment
-published: true
-
-title: Help us understand your learning goals
-code: act0
-
-assigned: March 29, 2021
-due: March 31, 2021 5PM Pacific
-
-revised: February 15, 2021
-
----
-* TOC
-{:toc}
-
-# Learning Goals
-
-The goal of this activity is to reflect on your motivations for wanting to aquire accessibility as a skill, and help the course staff understand the same so that we can do our best to cater to your learning objectives.
-
-
-# Turnin
-A one to two-page accessible document explaining:
-- Why are you taking this course?
-- What does accessibility mean to you?
-- Why do you think accessibility is important?
-- what role, if any does accessibility or access technology play in your professional life?
-- do you think accessibility can play a role in your professional work? how?
-
-# Grading
-This homework will receive points simply by being completed.
diff --git a/assignments/hw1-nvda.md b/assignments/hw1-nvda.md
deleted file mode 100644
index dccdbdcd..00000000
--- a/assignments/hw1-nvda.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-layout: assignment
-published: true
-
-title: Improve a screen reader
-code: as3
-
-assigned: April 5, 2021
-due:
- - April 21, 2021
-
-revised: April 21, 2021
-
-objective: Fix screen reader bugs; Contribute to the accessibility Community
-
----
-
-* TOC
-{:toc}
-
-# Learning Goals
-
-The goal of this activity is to
-- Learn more about how screen readers work
-- Be a contributor to the accessibility community
-- Get direct experience with the relation between web accessibility best practices and screen reader behavior
-
-# Overview
-
-People who are blind or visually impaired (BVI) access computers through screen readers. Simply put, screen readers are software that render the graphical user interface in audio (synthesized speech and sounds) or Braille (using a refreshable braille display). There are different types of screen readers, that run on a variety of platforms; from desktops, to smartphones, to smart-watches to smart speakers. One such screen reader is the Non Visual Desktop Access (NVDA) screen reader, a free, open source screen reader for windows. As per the [WebAIM: Screen Reader User Survey #8 Results](https://webaim.org/projects/screenreadersurvey8/), NVDA is the most used screen reader among respondents.
-
-In this homework, you will be working on a bug in the NVDA screen reader. Your approach should improve the usability of the NVDA screen reader for its intended audience. (remember, NVDA is developed by a huge community of developers who may be BVI so they are your target audience too!)
-
-To reduce the complexity of contributing to an open source project in a short time frame, we curated a list of potential github issues that you could work on. You are also free to pick other open issues from the NVDA github repository. We however recommend refraining from issues with high complexity or issues where a consensus has not been reached. You can find the full list of issues below.
-
-Once you decide the github issue that you would like to work on, please join the corresponding [group on Canvas](https://canvas.uw.edu/courses/1465814/groups#tab-122183). You may start working *individually* on a solution right away, but the group is there to share ideas and for phase 1's handin.
-
-
-# NVDA Issues
-
-
-
-1. [NVDA announces "Article" before every article while browsing the articles via quick keys #11103](https://github.com/nvaccess/nvda/issues/11103)
-2. [Failing the checkPot step should be more obvious. #10928](https://github.com/nvaccess/nvda/issues/10928)
-3. [Report status of screen curtain at startup when "Play a sound when toggling screen curtain" is disabled. · Issue #10692](https://github.com/nvaccess/nvda/issues/10692) (bug affecting screen reader announcement of screen curtain status. Picked up by a developer, but abandoned).
-4. [Add script for aria figure to input gestures and give the user the possibility to turn off reporing of this role in document formating settings · Issue #10826](https://github.com/nvaccess/nvda/issues/10826) (feature request to make NVDA announcement of “figure†optional.
-5. [Shorten "out of element" message #10446](https://github.com/nvaccess/nvda/issues/10446)
-6. [Selection not announced when jumping to Top/Bottom of Page · Issue #5549](https://github.com/nvaccess/nvda/issues/5549)
-7. [aria-labelledby element gets read twice #10512](https://github.com/nvaccess/nvda/issues/10512) (potentially a blocker on chrome?)
-8. [Grid cells with focusable controls get read twice #10096](https://github.com/nvaccess/nvda/issues/10096) (abandoned, and potentially a spec conformance but annoying behavior)
-9. [Table navigation doesn't respect colspan · Issue #7278](https://github.com/nvaccess/nvda/issues/7278)
-
-## Phase 1: Jointly prepare solution approach submission for NVDA (only for us)
-
-You will work as a group to prepare a solution approach, proposing one or multiple ways of working on a bug to improve the user experience for NVDA users. To do this you should all try to replicate the issue and think individually about solutions. Then summarize your results in a group-constructed document.
-
-You will not submit these to NVDA; you will submit these proposals as a group to [this Canvas Assignment](https://canvas.uw.edu/courses/1465814/assignments/6267341) for review by the course staff.
-
-You will also give a group presentation discussing:
-- The issue
- - What is it
- - Why do screen reader users care?
-- Reproducing the issue
- - Were any members of your group able to do so?
- - What did you learn from this
-- Solutions
- - What approaches did your group come up with?
- - If you couldn't come up with an approach, why?
-- What text you are proposing to submit to the NVDA Issue Tracker
-- Other Lessons Learned
-
-You will need to submit accessible slides to [this canvas assignment](https://canvas.uw.edu/courses/1465814/assignments/6148838). Please [make your presentations accessible, and present accessibly](http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-presentation-guide/) (here is [a short video](https://www.youtube.com/watch?v=L9TxhGv91kc) that provides some guidance)
-
-## Phase 2: Your personal perspective
-
-Please turn in an approximately 1 page write up answering the following questions
-
-- What did you learn from trying to use NVDA?
-- What issue did you address?
-- Were you able to replicate it?
-- What solution approach do you suggest?
-- What did you learn about how screen readers and web pages interact to make an experience more or less accessible?
-
-## Optional Phase 3: Submitting your solution to NVDA
-
-Your group may start communicating with NVDA after receiving approval from the staff. Please keep in mind that you should consider the opinions expressed by the NVDA user community through comments on the github issue of your choosing.
-
-If your approach is approved by the NVDA community, you and any other group members who use the same approach will have the opportunity to actually submit the best of your solutions.
-
-## NVDA setup and other pre-requisites
-
-You will need a Windows computer running Windows 10 and python 3.7 (32-bit) to install NVDA. If you do not have a Windows machine, please reach out to us as soon as possible. We have a limited number of machines that can be accessed remotely. The instructions to build NVDA are in the [NVDA github repository readme](https://github.com/nvaccess/nvda). Please also be sure to [read the contributing guide](https://github.com/nvaccess/nvda/wiki/Contributing).
-
-## Grading
-
-This is a 10 point assignment.
-
-- Two points for the presentation (including whether it is accessible and accessibly presented)
-- Two points to the group writeup (completeness)
-- 6 points the individual writeup based on its demonstration of the three learning goals stated at the beginning of the assignment.
- - Learn more about how screen readers work
- - Be a contributor to the accessibility community
- - Get direct experience with the relation between web accessibility best practices and screen reader behavior
-
-
diff --git a/assignments/hw2-soundRecognition.md b/assignments/hw2-soundRecognition.md
deleted file mode 100644
index 8403d011..00000000
--- a/assignments/hw2-soundRecognition.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-layout: assignment
-published: true
-
-title: Teach Machines to Recognise Sounds
-code: as4
-
-assigned: April 26, 2021
-due: May 5, 2021
-
-
-revised: April 26, 2021
-
-Objective: Teach machines to recognise non-speech sounds that occur around you and visualize these recognised sounds.
-
----
-
-# Learning goals
-
-1. Design a visualization and provide a rationale for its purpose and value in code/sketch
-2. Understand the difference between text for captioning speech and representations of nonspeech audio through the act of captioning a video that includes both speech and nonspeech audio
-2. Exploring how context may impact representation through the readings
-
-# Activities
-
-In this homework, you will do three things:
-1. Build a visualization of non-speech audio.
-2. Caption a video.
-3. Read related papers.
-4. Answer Reflection Questions
-
-All of these are described in more depth in the Jupyter Notebook
-
-## Build a visualization of non-speech audio
-
-We will provide a Jupyter notebook (linked on canvas) via Google Colaboratory that is pre-loaded with code to train a machine learning model to recognize sounds. Everything you need is in the notebook.
-
-To access it: Open it in your browser. You will be prompted to copy it. Then login to your UW CSE provided google account and open the notebook in google colab on your browser. [Here is a getting started tutorial on colab](https://colab.research.google.com/notebooks/intro.ipynb#).
-
-## Remainder of homework
-All of the information for captioning; papers to read; and the reflection questions can be found in the Jupyter notebook.
-
diff --git a/assignments/accessibility-img/1.png b/assignments/img/1.png
similarity index 100%
rename from assignments/accessibility-img/1.png
rename to assignments/img/1.png
diff --git a/assignments/accessibility-img/androidview.png b/assignments/img/androidview.png
similarity index 100%
rename from assignments/accessibility-img/androidview.png
rename to assignments/img/androidview.png
diff --git a/assignments/accessibility-img/avd.png b/assignments/img/avd.png
similarity index 100%
rename from assignments/accessibility-img/avd.png
rename to assignments/img/avd.png
diff --git a/assignments/accessibility-img/mdnavigator1.png b/assignments/img/mdnavigator1.png
similarity index 100%
rename from assignments/accessibility-img/mdnavigator1.png
rename to assignments/img/mdnavigator1.png
diff --git a/assignments/accessibility-img/mdnavigator2.png b/assignments/img/mdnavigator2.png
similarity index 100%
rename from assignments/accessibility-img/mdnavigator2.png
rename to assignments/img/mdnavigator2.png
diff --git a/assignments/accessibility-img/mdnavigator3.png b/assignments/img/mdnavigator3.png
similarity index 100%
rename from assignments/accessibility-img/mdnavigator3.png
rename to assignments/img/mdnavigator3.png
diff --git a/assignments/accessibility-img/mdnavigator4.png b/assignments/img/mdnavigator4.png
similarity index 100%
rename from assignments/accessibility-img/mdnavigator4.png
rename to assignments/img/mdnavigator4.png
diff --git a/assignments/accessibility-img/playstoreemulator.png b/assignments/img/playstoreemulator.png
similarity index 100%
rename from assignments/accessibility-img/playstoreemulator.png
rename to assignments/img/playstoreemulator.png
diff --git a/assignments/accessibility-img/projectview.png b/assignments/img/projectview.png
similarity index 100%
rename from assignments/accessibility-img/projectview.png
rename to assignments/img/projectview.png
--
GitLab