Accessibility Statement
Last updated: ยท Version 2026-11-05
I aim to make the QAwork public website and test-management workspace usable for people with different access needs. This statement describes current features and known limitations. It is not an independent certification or a claim that every WCAG requirement has been met.
Public website and legal pages
The Accessibility button offers text size, a readable font, line spacing, high contrast, greyscale, image visibility, reduced motion, underlined links and stronger focus outlines. Settings can be reset and are saved across visits only after optional preference storage is allowed. Your device's reduced-motion preference is also respected.
These pages include skip links, visible keyboard focus, labelled controls and descriptive text for meaningful images. The accessibility panel supports Escape to close and returns focus to its button. The public navigation and controls can be operated without a mouse.
Workspace and public demo
The workspace uses labelled forms, status controls, test-detail and bug dialogs, and visible keyboard focus. On small screens, tests use a compact layout instead of requiring sideways scrolling through the full desktop table. The scenario list offers sorting and selection; environment tabs can scroll when they contain many items. Project actions still depend on your role; the public demo is read-only.
The public-site accessibility toolbar is not currently installed in the private workspace or on the external-bug example page. Browser zoom and built-in accessibility tools remain available there. Some workspace values update while a timer is running; pause your timer before a longer interruption if you have editing access.
Known limitations and alternatives
Some website visuals are illustrations. Uploaded client images or third-party issue trackers may not have sufficient text alternatives. Ask for a written description or another suitable format where needed.
A toolbar does not replace accessible design or testing. Not every combination of browser, device, screen reader or user-provided content has been assessed. Modern browsers with JavaScript are needed for some menus, dialogs and workspace controls. External Google sign-in, messaging services and bug trackers have their own accessibility behaviour.
Report a barrier
Write to [email protected] with the page, the problem and, if you are comfortable sharing it, your device, browser or assistive technology. Do not include passwords or confidential client screenshots in an initial report. I can discuss a suitable written alternative through email, Telegram or WhatsApp.