Mercurial > p > roundup > code

changeset 8476:93f9d8622111

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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.
author John Rouillard <rouilj@ieee.org>
date Sat, 08 Nov 2025 14:03:42 -0500
parents bc3d3c54e1f0
children d36bd4c521ac
files doc/_static/style.css doc/html_extra/accessibility-statement_2025-10-08.html website/www/_static/style.css website/www/index.txt
diffstat 4 files changed, 100 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/doc/_static/style.css	Sat Nov 08 00:40:39 2025 -0500
+++ b/doc/_static/style.css	Sat Nov 08 14:03:42 2025 -0500
@@ -186,6 +186,8 @@
 /* style */
 
 :link { color: rgb(220,0,0); text-decoration: none;}
+/* improve contrast to AA */
+.admonition.note :link { color: rgb(170,1,1); text-decoration: none;}
 :link:hover {
     text-decoration: underline solid clamp(1px, .3ex, 4px);
     text-underline-position: under;
@@ -438,6 +440,14 @@
     white-space: break-spaces;
 }*/
 
+/* improve color contrast to AA against yellowish highlight bg */
+div.highlight .c1 {
+    color: rgb(3,114,3);
+}
+div.highlight .na {
+    color: rgb(220,2,2);
+}
+
 /* Forcing wrap in a pre leads to some confusing line breaks.
    Use a horizontal scroll. Indicate the scroll by using
    rounded scroll shadows.
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/html_extra/accessibility-statement_2025-10-08.html	Sat Nov 08 14:03:42 2025 -0500
@@ -0,0 +1,75 @@
+<!DOCTYPE html>
+<h2>Accessibility Statement for <span class="basic-information website-name">Roundup Issue Tracker Main Website</span></h2>
+<p>
+	This is an accessibility statement from <span class="basic-information organization-name">Roundup Issue Tracker</span>.
+</p>
+<h3>Conformance status</h3>
+<p>
+	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.
+	<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>
+	is
+	<span class="basic-information conformance-status" data-printfilter="lowercase">partially conformant</span>
+	with
+	<span class="basic-information conformance-standard"><span data-negate="">WCAG 2.2 level AA</span>.</span>
+	<span>
+	<span class="basic-information conformance-status">Partially conformant</span>
+	means that
+	<span class="basic-information conformance-meaning">some parts of the content do not fully conform to the accessibility standard</span>.
+</span>
+</p>
+<h3>Feedback</h3>
+<p>
+	We welcome your feedback on the accessibility of
+	<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>.
+	Please let us know if you encounter accessibility barriers on
+	<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>:
+</p>
+<ul class="basic-information feedback h-card">
+	<li>
+	E-mail:
+	<a class="email u-email" href="mailto:roundup-users@lists.sourceforge.net">roundup-users@lists.sourceforge.net</a>
+</li>
+	<li class="contact-other p-note">See https://www.roundup-tracker.org/contact.html for more.</li>
+</ul>
+<h3>Technical specifications</h3>
+<p>
+	Accessibility of
+	<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>
+	relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
+</p>
+<ul class="technical-information technologies-used">
+	<li>HTML</li>
+	<li>WAI-ARIA</li>
+	<li>CSS</li>
+</ul>
+<p>These technologies are relied upon for conformance with the accessibility standards used.</p>
+<h3>Limitations and alternatives</h3>
+<p>
+	Despite our best efforts to ensure accessibility of
+	<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.
+</p>
+<p>
+	Known limitations for
+	<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>:
+</p>
+<ol class="technical-information accessibility-limitations">
+	<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>
+	<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>
+</ol>
+<h3>Assessment approach</h3>
+<p>
+	<span class="basic-information organization-name">Roundup Issue Tracker</span>
+	assessed the accessibility of
+	<span class="basic-information website-name">Roundup Issue Tracker Main Website</span>
+	by the following approaches:
+</p>
+<ul class="technical-information assessment-approaches">
+	<li>Self-evaluation</li>
+</ul>
+<hr noshade="noshade">
+<h3>Date</h3>
+<p>
+	This statement was created on
+	<span class="basic-information statement-created-date">8 November 2025</span>
+	using the <a href="https://www.w3.org/WAI/planning/statements/">W3C Accessibility Statement Generator Tool</a>.
+</p>
--- a/website/www/_static/style.css	Sat Nov 08 00:40:39 2025 -0500
+++ b/website/www/_static/style.css	Sat Nov 08 14:03:42 2025 -0500
@@ -186,6 +186,8 @@
 /* style */
 
 :link { color: rgb(220,0,0); text-decoration: none;}
+/* improve contrast to AA */
+.admonition.note :link { color: rgb(170,1,1); text-decoration: none;}
 :link:hover {
     text-decoration: underline solid clamp(1px, .3ex, 4px);
     text-underline-position: under;
@@ -438,6 +440,14 @@
     white-space: break-spaces;
 }*/
 
+/* improve color contrast to AA against yellowish highlight bg */
+div.highlight .c1 {
+    color: rgb(3,114,3);
+}
+div.highlight .na {
+    color: rgb(220,2,2);
+}
+
 /* Forcing wrap in a pre leads to some confusing line breaks.
    Use a horizontal scroll. Indicate the scroll by using
    rounded scroll shadows.
--- a/website/www/index.txt	Sat Nov 08 00:40:39 2025 -0500
+++ b/website/www/index.txt	Sat Nov 08 14:03:42 2025 -0500
@@ -197,17 +197,18 @@
 demo.py``" and load up the URL it prints out!
 
 Follow the source gratification mode with these steps (change the
-``-2.4.0`` version identifier to match your downloaded file).
+``-2.6.0`` version identifier to match the version of Roundup you want
+to use).
 
 1. ``python3 -m pip download roundup``
-2. ``tar -xzvf roundup-2.4.0.tar.gz``
+2. ``tar -xzvf roundup-2.6.0.tar.gz``
 
    * if you don't have a tar command (e.g windows), use::
 
-       python -c "import tarfile, sys; tarfile.open(sys.argv[1]).extractall();" roundup-2.4.0.tar.gz
+       python -c "import tarfile, sys; tarfile.open(sys.argv[1]).extractall();" roundup-2.6.0.tar.gz
 
 
-3. ``cd roundup-2.4.0``
+3. ``cd roundup-2.6.0``
 4. ``python3 demo.py``
 
 (The source download can also be used to `create a custom Docker
Roundup Issue Tracker: http://roundup-tracker.org/