Accessibility Statement
We are committed to making our website usable by everyone. We assess against WCAG 2.2 Level AA and publish a VPAT® to document the current status and roadmap.
Scope
This statement applies to app-stack.net and connected web experiences.
Our Standard & Current Status
We are committed to making our website usable by everyone. We work toward WCAG 2.2 Level AA. Our most recent assessment (VPAT® 2.5, August 15, 2025) evaluated the site against WCAG 2.0 A/AA and found overall “Partially Supports.”
How We Test
We combine automated checks and manual audits, including screen-reader and keyboard testing. Tools and AT used include axe, Colour Contrast Analyser, and NVDA, JAWS, VoiceOver on current Chrome/Firefox/Edge/Safari across Windows and macOS.
Compatibility
Our site is intended to work with current versions of major browsers on desktop and mobile OSs and with assistive technologies that follow platform accessibility APIs.
Known Accessibility Limitations
- Non-text content: some decorative images/icons are not hidden from screen readers.
- Info & relationships / landmarks: missing or incorrect heading levels and landmarks on certain pages (e.g., missing H1 on “About,” footer landmark not defined on “Login,” dashboard landmarks).
- Bypass blocks: “Skip to main content” link not present.
- Page titles: some pages lack descriptive/unique titles.
- Focus order & forms: focus can enter an unexpanded accordion; focus doesn’t move to first invalid field; required fields aren’t always announced.
- Name/Role/Value: accordion name/state not exposed; show/hide password control lacks accessible name.
- Contrast: certain texts (e.g., “Login,” placeholders, specific headings) fall below 4.5:1.
Feedback & Accommodation Requests
If you encounter an accessibility barrier or need content in an alternative format, email support@app-stack.net. We aim to reply within 2 business days and resolve issues within 10 business days.
Ongoing Improvements
We’re adding a global skip link, correcting heading hierarchy and landmarks, fixing low-contrast styles, ensuring required fields are programmatically conveyed, and labelling interactive controls. We review this page after major releases and at least annually.
Published: August 15, 2025