RC2J Consulting

Accessibility

Accessibility

RC2J Consulting wants this site to be usable by as many people as possible, including people using a keyboard, a screen reader, screen magnification, or a small screen.

What this site does today

  • Pages are built from semantic HTML — headings, lists, landmarks, and a “Skip to content” link that comes first in the tab order.
  • Every interactive control is a real button or link, operable by keyboard, with a visible focus indicator.
  • The cookie preferences panel is a non-modal region rather than a dialog: it does not trap keyboard focus, and the rest of the page stays usable while it is open.
  • Text and interface colours were checked against the WCAG AA 4.5:1 contrast threshold on both the light and dark surfaces used across the site.
  • Touch targets for icon-only controls are sized to at least 44 by 44 pixels.
  • Layouts are responsive and were checked for horizontal overflow down to a 390-pixel-wide viewport, so pages do not require sideways scrolling.
  • Expandable FAQ answers are present in the page source whether or not they are expanded, and their controls report their state to assistive technology.
  • Images that carry meaning have text alternatives; decorative artwork is hidden from assistive technology.

What has not been tested

Being straightforward about the limits matters more than a badge:

  • This site has not been independently audited, and RC2J does not claim conformance to a specific accessibility standard.
  • Testing to date has been carried out with keyboard navigation and automated checks. It has not yet included a full manual review with screen-reader users.
  • Some opportunity imagery is illustrative and its text alternative describes the merchandise category rather than the individual items shown.

Reporting a barrier

If any part of this site prevents you from finding information or contacting RC2J, please say so and RC2J will work with you to get you the information another way.

Email rc2jconsulting@gmail.com — it helps to include the page address and a short description of what went wrong, and the assistive technology and browser you were using if you know them.