Our commitment
Accessibility
We build and deliver to WCAG 2.2 Level AA. This page describes our conformance target, the technical measures we have implemented, known limitations, and how to report barriers.
Accessibility statement for automationstreet.com. Statement date: May 2026. Next review: November 2026.
Conformance target
WCAG 2.2 Level AA
Automation Street targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AA conformance for this website and for all client-facing digital deliverables where accessibility requirements are included in the engagement scope. Our accessibility programme is continuous; known limitations are disclosed below and tracked on our internal remediation backlog.
Technologies relied upon: HTML5, CSS3, JavaScript (React / Next.js App Router), WAI-ARIA 1.2. Content is tested against current versions of Chrome, Firefox, Safari, and Edge, and with JAWS, NVDA, VoiceOver (macOS and iOS), and TalkBack (Android).
We also pursue selected WCAG 2.2 Level AAA criteria where they materially improve the experience for users of assistive technology, including enhanced focus appearance (2.4.12), consistent help mechanisms (3.2.6), and accessible authentication without cognitive function tests (3.3.8).
Technical measures
What we have implemented
The following measures are in production on this site. We conduct quarterly accessibility reviews against our internal audit backlog.
Skip navigation
A visible "Skip to main content" link is provided at the top of every page for keyboard and screen reader users, allowing them to bypass repetitive navigation.
Semantic HTML landmarks
All pages use proper <header>, <main>, <nav>, <footer>, and <section> elements to support assistive technology navigation and provide a clear document structure.
Logical heading hierarchy
All pages maintain a logical heading order (H1 through H3) with no skipped levels. Headings describe the content of each section rather than serving a visual-only purpose.
Visible focus indicators
All interactive elements display a 3px offset focus ring meeting WCAG 2.4.11 (Focus Appearance) criteria. Focus is never removed from interactive elements via CSS.
Colour contrast
All text targets a minimum 4.5:1 contrast ratio (WCAG AA) for normal text and 3:1 for large text. Body copy is designed to meet 7:1 (AAA) against background surfaces.
Full keyboard operability
All interactive components are fully operable by keyboard alone. No keyboard traps exist. Navigation menus and dialogs close on Escape. Tab order follows visual layout.
ARIA labels and states
Navigation menus, dialogs, accordions, and form fields include appropriate ARIA roles, aria-label, aria-expanded, and aria-live attributes where native HTML semantics are insufficient.
Meaningful alternative text
All meaningful images include descriptive alt attributes that convey equivalent information. Decorative images use empty alt attributes to be correctly ignored by screen readers.
Accessible forms
All form inputs are associated with visible labels using <label> elements. Error messages are descriptive, associated programmatically, and not reliant on colour alone. Autocomplete attributes follow WCAG 1.3.5.
Motion and animation
All animations and transitions respect the prefers-reduced-motion CSS media query. No content blinks, flashes at a rate above 3 Hz, or auto-plays audio without user consent.
Touch target sizing
All interactive elements meet a minimum touch target area of 44x44 CSS pixels, exceeding the WCAG 2.5.5 (Target Size) criterion to ensure usability on touch devices.
Responsive and reflow
Content is fully usable at viewport widths from 320px to 1920px without horizontal scrolling at 400% zoom, meeting WCAG 1.4.10 (Reflow). All functionality is preserved at all breakpoints.
Assessment approach
How we test
Accessibility assessment is conducted through multiple methods to catch issues that automated tools alone cannot detect.
Automated scanning
axe-core is integrated into our CI/CD pipeline and runs against every deployed build, flagging violations before they reach production.
Manual keyboard review
Each major page template is reviewed using keyboard-only navigation to verify tab order, focus management, and interaction patterns.
Screen reader testing
Pages are tested with NVDA on Firefox and VoiceOver on Safari to verify that dynamic content, landmarks, and interactive components behave correctly.
Contrast audit
Colour contrast ratios are checked against WCAG AA thresholds using the WebAIM Contrast Checker and browser developer tools.
Annual specialist review
An external accessibility specialist conducts an annual in-depth audit of the full site, including specialist user testing where feasible.
Known limitations
Current known issues
We are committed to transparency. The following issues have been identified and are on our remediation backlog with target dates for resolution:
PDF documents
Some downloadable resources may not be fully tagged for screen reader accessibility. Contact us and we will provide the content in an accessible alternative format within five business days.
Third-party scripts
Analytics and form scripts from third-party providers may not fully conform to WCAG 2.2. We minimise third-party scripts, require accessibility provisions in vendor contracts, and test these integrations as part of our quarterly review cycle.
Formal complaints
If you are not satisfied with our response to an accessibility complaint, you may contact the ADA National Network at 1-800-949-4232, or file a complaint with the U.S. Department of Justice Civil Rights Division.
Client deliverables
Accessibility in every engagement
For client engagements that include custom interfaces or portals, we incorporate accessibility requirements at the discovery phase. Acceptance criteria for client-facing deliverables include conformance testing against WCAG 2.2 AA using axe-core and manual keyboard and screen reader review.
We are available to assist clients in scoping accessibility requirements for regulated industries, including healthcare systems with Section 508 obligations and financial services firms with ADA compliance programmes.
Discuss accessibility requirementsNeed help accessing this content?
Report a barrier and our team will respond within five business days with a resolution or accessible alternative.