accessibility-resources/manifesto.html at main · codelikeagirlau/accessibility-resources · GitHub

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
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <link rel="stylesheet" type="text/css" href="styles.css" />
    <link
      href="https://fonts.googleapis.com/css2?family=Gabarito:wght@400;500;600&family=Inter:wght@400;500;700&display=swap"
      rel="stylesheet"
    />
    <title>Manifesto - Accessibility Resources</title>
  </head>
  <body>
    <header>
      <div class="container">
        <div class="logo">CLG Community Accessibility Resources</div>
      </div>
    </header>
    <main>
      <div class="container main-content">
        <!-- NOTE: If you update the navigation, please also update it on all other pages  -->
        <nav class="sidebar-nav">
          <ul>
            <li><a href="accessibility-resources/index.html">Home</a></li>
            <li><a href="accessibility-resources/tools-and-resources.html">Tools & Resources</a></li>
            <li><a href="#">Applying Accessibility</a></li>
            <li><a href="accessibility-resources/accessibility-resources/manifesto.html" class="active">Manifesto</a></li>
            <li><a href="accessibility-resources/accessibility-resources/about.html">What is this thing?</a></li>
            <li><a href="accessibility-resources/people-to-follow.html">People to follow</a></li>
            <li class="btn">
              <a href="accessibility-resources/sub-page/web-developer-pledge.html">Take the pledge!</a>
            </li>
          </ul>
        </nav>
        <article>
        <h1>Accessibility Manifesto: Making the web better for everyone</h1>
        <!-- the manifesto is a place for our big-picture, lofty thinking about accessibility. Values, ethics, etc.   -->
        <section>

          <h2>What are we talking about when we talk about accessibility?</h2>
          <ul>
            <li>
              We subscribe to the POUR principles: perceivable, operable,
              understandable, robust
            </li>
            <li>
              We are not bound or limited by common understandings of what
              accessibilty includes. We want to make the web better for everyone,
              whatever that involves.
            </li>
            <li>
              "Digital" isn't just about web - how do we consider accessibility in
              webinars and online events, emails, audio, etc
            </li>
            <li>
              How do we consider people who aren't as tech savvy in how we set up
              our websites / apps/ digital products?
            </li>
            <li>
              Not using dark patterns (e.g. burying "unsubscribe" to service
              options).
            </li>
          </ul>
        </section>
        <section>
          <h2>
            Who in an organisation is responsible, accountable, consulted and
            informed when it comes to accessibility?
          </h2>

          <h3>Responsible</h3>
          <ul>
            <li>Designers</li>
            <li>Content Writers</li>
            <li>Devs and techies</li>
            <li>QA and testers</li>
          </ul>

          <h3>Accountable</h3>

          We suggest organisations form an "accessibiliy committee".

          <h3>Consulted</h3>

          <ul>
            <li>Clients</li>
          </ul>

          <h3>Informed</h3>
          <ul>
            <li>Executives / board members</li>
            <li>External stakeholders where relevant (e.g. grant reporting)</li>
          </ul>
        </section>
        <section>
          <h2>Ethical Considerations</h2>
          <li>
            Making websites and digital experiences accessibile is an ethical
            imperative. While it is a legal requirement in some legislations and
            contexts, we shouldn't let the legal requirements drive our work towards
            accessibility.
          </li>
          <li>
            Use of AI (sometimes the robot is good). How can we ensure we are using
            AI tools ethically, e.g. Otter AI for transcripts and meeting summaries,
            ChatGPT for digesting information and reducing overwhelm etc. What are
            the ethical concerns with these technologies, and how can we mitigate
            them?
          </li>
        </section>
        <section>
          <h2>Context is key</h2>
          <ul>
            <li>
              Autoplay of music and video - MySpace songs. Context is key. TikTok
              "mute on entry" setting.
            </li>
          </ul>
          <h2>We need to challenge our preconceptions</h2>
          <ul>
            <li>
              How can we go above and beyond what we thought possible - e.g.
              <a
                href="https://www.freecodecamp.org/news/helping-blind-people-learn-to-code-c47c68d4a237"
                target="_blank"
                >Helping blind people learn to code</a
              >
            </li>
          </ul>
        </section>
    </main>
  </body>
</html>