Weeksolved is built to be usable by people who cannot see the screen, cannot use a
mouse, need larger text, or rely on assistive technology. This page says what has
been done, what has not, and how to tell us when we have got it wrong.
The standard we build to
WCAG 2.2 Level AA.
We chose 2.2 rather than an older version deliberately. Section 508 of the
Rehabilitation Act still points at WCAG 2.0 AA; the Department of Justice's Title II
rule for state and local government (compliance dates in April 2027 and April 2028)
requires 2.1 AA; the Department of Health and Human Services' Section 504 rule
requires the same; and New York State requires 2.2 AA from January 2027. WCAG 2.2 is
a superset of all of them, so building to it satisfies every one at once rather than
making our customers check which version we happened to pick.
What has actually been done
These are measured results across every page of the application, in both light and
dark appearance, at widths from 320 pixels upward:
Contrast. Every piece of text meets the 4.5:1 minimum, and every control
boundary and focus ring meets 3:1. Nineteen failures were found and all nineteen
were fixed.
Tables. Every column and row header is associated with its cells, and every
table announces what it is rather than "table, six columns". Sixty-three unassociated
headers were fixed.
Forms. Every field has a real label. A placeholder is never used as the only
label, because it disappears the moment somebody types and voice control cannot see it.
Keyboard. Everything is reachable and operable without a mouse, every focusable
element shows a visible focus ring, dialogs trap focus while open and hand it back
to the button that opened them when they close, and Escape closes them.
Reflow. No page scrolls sideways at 320 pixels, which is the same as a 1280-pixel
window at 400% zoom. Wide tables scroll inside their own container and that container
is reachable by keyboard.
Text spacing. Nothing clips or overlaps when line height, letter spacing and word
spacing are forced wider, which is what a reader stylesheet does.
Target size. Every control meets the 24×24 pixel minimum, apart from links inside
a sentence and controls whose label is the target — both of which the standard exempts.
Status messages. Confirmations and warnings are announced without moving focus,
from a live region that exists before the message does.
Landmarks and titles. A skip link, a real main landmark, and a page title that
changes when you move between pages so a screen reader says where you have landed.
Motion. Animation is removed for anyone whose system asks for reduced motion.
You can also change text size and spacing yourself, in Settings, on any device.
It scales the whole layout together rather than only the type, so nothing overlaps, and
it does not affect what prints.
What has not been done, and we would rather say so
No independent audit. Everything above was tested by us. An outside expert has
not reviewed this product.
No independent accessibility audit. If you need one, ask us. We will
commission an independent audit and publish what it finds; we will not write one
ourselves and call it independent.
No screen-reader testing by a person who uses one daily. Behavior has been
verified programmatically and by keyboard. That catches a great deal, and it does not
replace someone who actually lives with a screen reader telling us what is awkward.
Automated checking finds only part of the problem. Depending on how it is counted,
automated tools catch somewhere between a fifth and a half of what the standard requires.
We are not going to pretend that a clean automated report is the same as an accessible
product.
Printed output and exported PDFs have not been separately assessed against
PDF/UA. Every report is also available as CSV, which is the more accessible format,
and we would rather point you there than overstate the PDFs.
If something does not work
Tell us and we will fix it. This is a small company, which cuts both ways: there is no
ticket queue between you and the person who can change the code.
Email support@weeksolved.com with what you were trying to do, what happened, and what
you were using — the browser, and any assistive technology. We will acknowledge quickly,
tell you honestly whether it is a quick fix or a long one, and come back to you when it
is done.