Accessibility Statement

Accessibility at chaplin-rueda.com

Last updated: 05/05/2026

I am Cristina Chaplin-Rueda, a UX designer committed to creating inclusive digital experiences. I strive to ensure my portfolio meets WCAG 2.1 Level AA standards. While I have full control over the content and custom forms on this site, this portfolio is built using the Infomaniak Site Creator. This builder tool introduces certain theme-level elements that currently fall short of full accessibility compliance, despite my best efforts to remediate them via custom code.

Current Known Issues & Limitations

  1. Theme Modal Close Button:
    • Issue: The default "Close" (X) button for image lightboxes/modals generated by the theme lacks a programmatically determinable label (aria-label).
    • Impact: Screen reader users may not understand the purpose of this button.
    • Status: Unresolved due to theme Shadow DOM restrictions. I have attempted multiple JavaScript injections, but the builder isolates this element from custom scripts.
  2. Header Search Bar:
    • Issue: The theme includes a global search bar in the header. Even though this feature is not actively used on this portfolio, the input field lacks an associated label and programmatic purpose (autocomplete).
    • Impact: Assistive technologies cannot identify the field's purpose.
    • Status: Unresolved. The search module is hard-coded into the theme header and cannot be removed or modified without access to the core theme files.

What I Have Fixed

Despite these theme limitations, I have ensured that all custom content I have created is fully accessible:

  • Custom Contact Form: Fully labeled, high-contrast, keyboard navigable, and includes autocomplete attributes.
  • "Go to Top" Button: Programmatically labeled and functional for keyboard/screen reader users.
  • Privacy Policy Checkbox: Correctly linked to its label with a static ID.
  • Colour Contrast: All text and interactive elements meet WCAG AA/AAA standards.
  • Semantic Structure: Headings, lists, and landmarks are used correctly throughout the content.

Feedback & Contact

I am continuously working to improve the accessibility of this site. If you encounter any barriers not listed here, or if you have suggestions for improvement, please contact me directly.

Search