Accessibility

This statement describes what Stackyfull aims for, what has actually been tested, and what is still outstanding. It is written to be honest rather than reassuring — a statement that claims more than it has verified is worth nothing to the person who cannot use the site.

What we aim for

We target WCAG 2.1 Level AA. There is no published technical standard for private websites under the Americans with Disabilities Act, so WCAG 2.1 AA is the benchmark courts and regulators have generally applied, and it is the one we work to.

What the site does

• Semantic HTML throughout — real headings, lists, tables and form labels.
• Every calculator input has a visible, programmatically associated label. Result areas are announced as live regions.
• All functionality works from the keyboard. Focus is always visible and never removed.
• Data tables use row and column headers with scope, so a screen reader announces which figure belongs to which line item.
• Motion is limited to one small animation, which is disabled entirely under prefers-reduced-motion.
• Text is set in relative units and reflows to 320px without horizontal scrolling. Colour is never the only means of conveying information.
• No pop-ups, no interstitials, no auto-playing media, no time limits.

What we have not done

Being straightforward about this matters more than the list above:

• The site has not yet been audited by a third party, and it has not been tested end-to-end with screen readers on every page. Conformance is our intent, not a verified claim.
• Colour contrast has been designed to meet AA but has not been measured on every element in both colour schemes.

We would rather publish that than imply a level of assurance we have not earned. This section will shrink as testing is done, and this page will say when.

What we will not do

We will not install an accessibility overlay or accessibility widget. These products claim to make a site conformant with a line of JavaScript, they routinely make things worse for the people they claim to help, and the accessibility community has consistently advised against them. The Federal Trade Commission has taken enforcement action over such claims. Accessibility here comes from how the pages are built.

Reporting a barrier

If any part of this site is difficult or impossible for you to use, please tell us at hello@metricmind.io. Describe the page and what happened; you do not need to know the technical cause. We treat access barriers as defects, and they take priority over new features.