Skip to content

Commit f67cf64

Browse files
committed
doc: update styles to WCAG AAA; add accessibility statement; reword
Update to AA WCAG 2.2 contrast: in note admonitions, link contrast was too low in python code examples, comments were too low contrast Added accessability statement. It is only in the tree and not linked to the website currently. Updated install directions for future 2.6 release. Updated paragraph to make it clearer.
1 parent 65b50f3 commit f67cf64

File tree

4 files changed

+100
-4
lines changed

4 files changed

+100
-4
lines changed

doc/_static/style.css

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,8 @@ div[class^=highlight-], div[class^=highlight-] * { width:
186186
/* style */
187187

188188
:link { color: rgb(220,0,0); text-decoration: none;}
189+
/* improve contrast to AA */
190+
.admonition.note :link { color: rgb(170,1,1); text-decoration: none;}
189191
:link:hover {
190192
text-decoration: underline solid clamp(1px, .3ex, 4px);
191193
text-underline-position: under;
@@ -438,6 +440,14 @@ dd > ul:first-child {
438440
white-space: break-spaces;
439441
}*/
440442

443+
/* improve color contrast to AA against yellowish highlight bg */
444+
div.highlight .c1 {
445+
color: rgb(3,114,3);
446+
}
447+
div.highlight .na {
448+
color: rgb(220,2,2);
449+
}
450+
441451
/* Forcing wrap in a pre leads to some confusing line breaks.
442452
Use a horizontal scroll. Indicate the scroll by using
443453
rounded scroll shadows.
Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
<!DOCTYPE html>
2+
<h2>Accessibility Statement for <span class="basic-information website-name">Roundup Issue Tracker Main Website</span></h2>
3+
<p>
4+
This is an accessibility statement from <span class="basic-information organization-name">Roundup Issue Tracker</span>.
5+
</p>
6+
<h3>Conformance status</h3>
7+
<p>
8+
The <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG)</a> defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
9+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>
10+
is
11+
<span class="basic-information conformance-status" data-printfilter="lowercase">partially conformant</span>
12+
with
13+
<span class="basic-information conformance-standard"><span data-negate="">WCAG 2.2 level AA</span>.</span>
14+
<span>
15+
<span class="basic-information conformance-status">Partially conformant</span>
16+
means that
17+
<span class="basic-information conformance-meaning">some parts of the content do not fully conform to the accessibility standard</span>.
18+
</span>
19+
</p>
20+
<h3>Feedback</h3>
21+
<p>
22+
We welcome your feedback on the accessibility of
23+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>.
24+
Please let us know if you encounter accessibility barriers on
25+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>:
26+
</p>
27+
<ul class="basic-information feedback h-card">
28+
<li>
29+
E-mail:
30+
<a class="email u-email" href="mailto:[email protected]">[email protected]</a>
31+
</li>
32+
<li class="contact-other p-note">See https://www.roundup-tracker.org/contact.html for more.</li>
33+
</ul>
34+
<h3>Technical specifications</h3>
35+
<p>
36+
Accessibility of
37+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>
38+
relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
39+
</p>
40+
<ul class="technical-information technologies-used">
41+
<li>HTML</li>
42+
<li>WAI-ARIA</li>
43+
<li>CSS</li>
44+
</ul>
45+
<p>These technologies are relied upon for conformance with the accessibility standards used.</p>
46+
<h3>Limitations and alternatives</h3>
47+
<p>
48+
Despite our best efforts to ensure accessibility of
49+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span> , there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.
50+
</p>
51+
<p>
52+
Known limitations for
53+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>:
54+
</p>
55+
<ol class="technical-information accessibility-limitations">
56+
<li><strong>Search input does not have a visible label</strong>: The visible label is in the [Search] button next to the input but it not tied to the input directly. because The button acts as a visible label from proximity. The input has an aria-label describing the input.</li>
57+
<li><strong>Multi-language tab panel examples do not scroll</strong>: Multi-language example panels require two tabs to get to the element that will scroll. The Sphinx tab extension is used to show different language examples for the same item. It adds a focusable container around the example container. So the outer container must be tabbed/focused through to scroll the example when using the keyboard.</li>
58+
</ol>
59+
<h3>Assessment approach</h3>
60+
<p>
61+
<span class="basic-information organization-name">Roundup Issue Tracker</span>
62+
assessed the accessibility of
63+
<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>
64+
by the following approaches:
65+
</p>
66+
<ul class="technical-information assessment-approaches">
67+
<li>Self-evaluation</li>
68+
</ul>
69+
<hr noshade="noshade">
70+
<h3>Date</h3>
71+
<p>
72+
This statement was created on
73+
<span class="basic-information statement-created-date">8 November 2025</span>
74+
using the <a href="https://www.w3.org/WAI/planning/statements/">W3C Accessibility Statement Generator Tool</a>.
75+
</p>

website/www/_static/style.css

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,8 @@ div[class^=highlight-], div[class^=highlight-] * { width:
186186
/* style */
187187

188188
:link { color: rgb(220,0,0); text-decoration: none;}
189+
/* improve contrast to AA */
190+
.admonition.note :link { color: rgb(170,1,1); text-decoration: none;}
189191
:link:hover {
190192
text-decoration: underline solid clamp(1px, .3ex, 4px);
191193
text-underline-position: under;
@@ -438,6 +440,14 @@ dd > ul:first-child {
438440
white-space: break-spaces;
439441
}*/
440442

443+
/* improve color contrast to AA against yellowish highlight bg */
444+
div.highlight .c1 {
445+
color: rgb(3,114,3);
446+
}
447+
div.highlight .na {
448+
color: rgb(220,2,2);
449+
}
450+
441451
/* Forcing wrap in a pre leads to some confusing line breaks.
442452
Use a horizontal scroll. Indicate the scroll by using
443453
rounded scroll shadows.

website/www/index.txt

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -197,17 +197,18 @@ install Roundup. After you've unpacked the source, just run "``python
197197
demo.py``" and load up the URL it prints out!
198198

199199
Follow the source gratification mode with these steps (change the
200-
``-2.4.0`` version identifier to match your downloaded file).
200+
``-2.6.0`` version identifier to match the version of Roundup you want
201+
to use).
201202

202203
1. ``python3 -m pip download roundup``
203-
2. ``tar -xzvf roundup-2.4.0.tar.gz``
204+
2. ``tar -xzvf roundup-2.6.0.tar.gz``
204205

205206
* if you don't have a tar command (e.g windows), use::
206207

207-
python -c "import tarfile, sys; tarfile.open(sys.argv[1]).extractall();" roundup-2.4.0.tar.gz
208+
python -c "import tarfile, sys; tarfile.open(sys.argv[1]).extractall();" roundup-2.6.0.tar.gz
208209

209210

210-
3. ``cd roundup-2.4.0``
211+
3. ``cd roundup-2.6.0``
211212
4. ``python3 demo.py``
212213

213214
(The source download can also be used to `create a custom Docker

0 commit comments

Comments
 (0)