[RfR] Accessibility statement first draft

_toc.yml

@@ -350,4 +350,5 @@ parts:
     chapters: 
       - file: cfrr_program_details/code_of_conduct
       - file: cfrr_program_details/code_of_conduct_violations
+      - file: cfrr_program_details/accessibility
       - file: cfrr_program_details/programme_policies

cfrr_program_details/accessibility.ipynb

@@ -0,0 +1,80 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "id": "dc9784f2-22a4-4e37-a5de-af1b60bc5961",
+   "metadata": {},
+   "source": [
+    "# Accessibility Statement for CfRR Courses\n",
+    "\n",
+    "University of Exeter is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.\n",
+    "\n",
+    "This accessibility statement applies to the [Coding for Reproducible Research (CfRR) website](https://coding-for-reproducible-research.github.io/CfRR_Courses/).\n",
+    "\n",
+    "This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.\n",
+    "\n",
+    "To notify us of any accessibility compliance failures or to request information or content excluded from the scope of the Directive, please use one of the following methods:\n",
+    "- **GitHub issue**: [Submit an issue](https://github.com/coding-for-reproducible-research/CfRR_Courses/issues/new)  \n",
+    "  Please include the URL of the page where you encountered the issue and a brief description.\n",
+    "- **Email**: [email protected]\n",
+    "\n",
+    "All enquiries and requests sent through the feedback mechanism will be handled by the Coding for Reproducible Research team. \n",
+    "\n",
+    "This statement was prepared on 6th August 2025. The statement was last reviewed on 8th August 2025.\n",
+    "\n",
+    "The [Equality and Human Rights Commission (EHRC)](https://www.equalityhumanrights.com/) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).\n",
+    "\n",
+    "If you’re not happy with how we respond to your complaint, contact the [Equality Advisory and Support Service (EASS)](https://www.equalityadvisoryservice.com/).\n",
+    "\n",
+    "```{important}\n",
+    "## Non-Accessible Content\n",
+    "\n",
+    "### 1. Tables Generated from R\n",
+    "\n",
+    "Some tables created within our R-based teaching materials use multiple header rows or columns but do not include `headers` attributes in `<td>` elements. This affects screen reader usability, particularly for complex tables. These are autogenerated from R output and are presented as-is to reflect authentic results and maintain consistency with the source language’s conventions. We believe altering these outputs post-generation would compromise the educational integrity of the material, and have decided to leave them as they are originally. \n",
+    "\n",
+    "### 2. Teal-Coloured Julia Warning Text\n",
+    "\n",
+    "Some warning messages from the Julia programming language are displayed using a teal color that does not meet minimum contrast standards (WCAG 2.2 requires 4.5:1 for normal text). These warnings are auto-generated outputs when making use of `@code_warntype`. We have left these warnings in their original form to preserve the realism of the programming environment. \n",
+    "\n",
+    "### 3. Missing `scope` Attribute on `<th>` Elements\n",
+    "\n",
+    "Certain tables generated from statistical model outputs in R use `<th>` elements without including a `scope` attribute to indicate whether the header applies to a row or a column. This can impair the ability of screen readers to correctly associate headers with corresponding data cells, especially in summary or regression tables. These outputs reflect the default rendering of R model summaries and have been retained to represent R’s output format accurately, and have so been left within the website for authenticity. \n",
+    "\n",
+    "### 4. Auto-Generated Output with Insufficient Color Contrast\n",
+    "\n",
+    "Several pages contain output generated directly from R or Python packages, where the text color does not meet WCAG 2.2 contrast requirements. These outputs are left in their original form to maintain fidelity with the tools being taught and to avoid presenting altered or potentially misleading results. These instances are the result of direct console or library output from R and Python, and modifying them would be disingenuous to the pedagogical intent of teaching the tools in their real-world usage context.\n",
+    "```\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "03af971c-5c99-4620-a3c2-d632f8c9190a",
+   "metadata": {},
+   "outputs": [],
+   "source": []
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "Python 3 (ipykernel)",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.9.19"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}