-
Notifications
You must be signed in to change notification settings - Fork 0
/
akarsh.html
101 lines (75 loc) · 8.9 KB
/
akarsh.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Hegemony and Meritocracy Survey</title>
<meta name="description" content="Hegemony and Meritocracy Survey">
<link rel="icon" href="survey.jpeg">
<meta name="author" content="Markus Priede">
<meta name="viewport" content="width=device-width,initial-scale=1">
<link rel="stylesheet" type="text/css" href="indexstyle.css">
</head>
<body>
<header>
<div class="navlinks">
<ul>
<li ><a href="index.html">About</a></li>
<li><a href="surveyhome.html">Take The Survey</a></li>
<li><a href="results.html">Results</a></li>
<li><a href="analysis.html">Analysis</a></li>
</ul>
</div>
</header>
<div class="home-content">
<section class="home-content-blurb">
<h2 class="home-content-blurb-title">Akarsh's Reflection</h2>
<article>
<p style="font-size:16px;">Recognizing intersectionality in technology and information technology as a complicated, multifaceted issue and addressing it requires a proactive and ongoing effort. By considering our target audience's diverse needs and perspectives, we can create tech and information technology solutions that are more inclusive, accessible, and equitable for all.</p>
<p style="font-size:16px;">Our project's use of responsive design, which made the site accessible to people with various devices and abilities, was a crucial component. This includes making the site more accessible to people with varying English language skills by optimizing it for viewing on various devices and adding features like alt text and clear, concise wording.</p>
<p style="font-size:16px;">We considered concerns of inclusion and diversity in addition to accessibility during the design and development process. This involved considering the variety of our intended audience and ensuring the website was friendly and inclusive of all visitors. In addition to being useful and user-friendly, we also wanted to design a website that was inviting and inclusive of people from various backgrounds and abilities.</p>
<p style="font-size:16px;">We were able to interact and share our various experiences and opinions while participating in a remote-paired programming session, which further allowed us to become more conscious of these difficulties. This made it possible for us to find and remove any obstacles to accessibility and inclusion that we would not have otherwise known about.</p>
<p style="font-size:16px;">For instance, one of our team members remarked that their location and internet access made it impossible for them to use several tools and services. This led us to brainstorm several solutions that would be more available and inclusive for every team member, regardless of where they were or if they had an internet connection.</p>
<p style="font-size:16px;">Our project's overall goal was to promote intersectionality in technology and information technology by taking into account the varied requirements and viewpoints of our target audience. We were able to jointly identify and solve possible accessibility and inclusiveness hurdles during a remote-paired programming session, which eventually resulted in the development of a more accessible and inclusive website. We believe that by addressing these problems, we may develop technological and informational solutions that are more equal, inclusive, and accessible to all.</p>
<p style="font-size:16px;">It's crucial to understand that intersectionality in technology and information technology is a complicated and multifaceted issue that calls for proactive and continuous effort to solve. We can design tech and information technology solutions that are more inclusive, accessible, and fair for everyone by taking into account the varied demands and views of our target audience. We believe that through promoting more inclusive and accessible design and development techniques, our initiative will act as a paradigm for future technological and informational endeavors.</p>
<p style="font-size:16px;">Examining the IT sector requires taking into account hegemony and meritocracy. Who has access to leadership roles and decision-making processes within this industry may be significantly impacted by how power and resources are distributed. It's crucial to think about the ways that some groups could be overrepresented or excluded from these possibilities, as well as the possible effects of these imbalances.</p>
<p style="font-size:16px;">The idea of a meritocracy, which refers to the idea that people are rewarded and acknowledged based on their merit or competence, is pertinent to the IT sector as well. The criteria employed to choose the "meritorious" individuals, however, are frequently prejudiced or distorted, which results in unequal chances and outcomes. It is crucial to take into account how these prejudices could maintain or aggravate current power disparities within the IT sector.</p>
<p style="font-size:16px;">It's also critical to acknowledge the frequent intersections and synergies between hegemony and meritocracy. For instance, certain groups may be more likely to be seen favorably because of their privilege or access to resources, whilst others may be adversely affected by institutionalized prejudice or restrictions. This may result in a vicious cycle of disadvantage and exclusion that is hard to reverse.</p>
<p style="font-size:16px;">Examining and challenging these power relations is crucial to solve these problems and encourage more fair and inclusive practices within the IT sector. In order to do this, it may be necessary to look into and eliminate biases in the standards used to determine merit, as well as to seek to build more diverse and representative leadership and decision-making bodies. We can work toward establishing a more fair and equitable IT economy for everybody by taking into account these concerns and acting to rectify them.</p>
<p style="font-size:16px;">Working on the types of questions was a crucial part of our approach. We worked together as a group to create the questions because they are so important in comprehending the users. All of the questions were created so that respondents could choose whether they agreed, disagreed, or were neutral about the statement or subject being discussed.</p>
<p style="font-size:16px;">It's critical to properly construct questions if you want to collect information from users that is both relevant and valuable. In order to create successful questions, it is crucial to take into account the project's goal and the kind of data required.</p>
<p style="font-size:16px;">There are several question kinds that may be applied to a project, each having advantages and cons of their own. For instance, closed-ended inquiries may be helpful for obtaining precise, factual data, but they might not offer as much depth or complexity as open-ended inquiries. Open-ended questions, on the other hand, can be helpful for obtaining more in-depth data and examining the respondent's ideas and feelings, but they could be more challenging to analyze and interpret owing to the vast variety of possible replies.</p>
<p style="font-size:16px;">We were able to properly evaluate the kind of questions being utilized and how they might effect the project's outcomes by cooperating as a group. This aided in ensuring that the questions were well-crafted and successful in eliciting the required data from the consumers.</p>
<p style="font-size:16px;">References:<br>
1. Noble, Safiya Umoja. Algorithms of Oppression: How Search Engines Reinforce Racism. New York University Press, 2018.<br>
2. Tiku, Nitasha. ‘The Dirty War Over Diversity Inside Google’. Wired. www.wired.com,https://www.wired.com/story/the-dirty-war-over-diversity-inside-google.</p>
</article>
</section>
<section class="home-content-blurb">
<h2 class="home-content-blurb-title">Individual Essays</h2>
<article id="group-members-container">
<ul style="line-height: 1.5;">
<li><a href="markus.html" style="color: darkslategray;">
Markus's Reflection
</a></li>
<li><a href="akarsh.html" style="color: darkslategray;">
Akarsh's Reflection
</a></li>
<li><a href="anwita.html" style="color: darkslategray;">
Anwita's Reflection
</a></li>
<li><a href="irasema.html" style="color: darkslategray;">
Irasema's Reflection
</a></li>
</ul>
</article>
</section>
</div>
<footer>
<div id = "foot" style="line-height: 2.0;">
<br>Survey created by Akarsh, Anwita, Irasema, and Markus
<br>LIS 500
<br>University of Wisconsin-Madison
</div>
</footer>
</body>
</html>