Accessibility Statement

Our commitment

We want everyone to be able to read this site and get in touch with us, including people using a screen reader, a keyboard alone, magnification, or reduced motion.

Accessibility is not a feature we added at the end. It shaped how the pages are marked up.

The standard we work to

We aim to meet WCAG 2.1 Level AA. We build to that standard and test against it as part of our own process.

We have not commissioned an independent third-party accessibility audit of this website, so we do not claim certified conformance. When we have one, we will publish the result here, including anything it finds against us.

What we have built in

• Semantic HTML. Pages use real headings, lists, navigation landmarks, and a single main region, so assistive technology can convey the structure rather than a wall of text.
• Skip link. A "Skip to main content" link is the first thing a keyboard user reaches on every page.
• Keyboard operable navigation. The main menu opens on focus as well as on hover, so it can be used without a mouse. Every menu item is a real link, which means it also works if JavaScript fails to load.
• Visible focus. A clear focus outline is shown on every interactive element.
• Text alternatives. Meaningful images carry descriptive alt text. Decorative images carry empty alt text so screen readers pass over them, and icons expose accessible names where they convey meaning.
• Labelled form fields. Every field on the contact form and the newsletter form has a real label, and status messages are announced through a live region. Where a field is required its label says so; where a field is optional its label says that instead, so the visible text always states the expectation rather than leaving it to be inferred from a missing asterisk.
• Colour contrast. Body text and interactive elements are chosen to meet AA contrast ratios, and colour is never the only way information is conveyed.
• Responsive and zoomable. Content reflows down to small screens and remains usable at high zoom.
• Reduced motion. Animations are suppressed for visitors whose system requests reduced motion.
• Language declared. Each page declares its language so screen readers pronounce it correctly.

Known limitations

Being specific here is more useful than a general assurance.

• Some technical illustrations and diagrams convey their meaning primarily visually. Where that happens, the surrounding text explains the same point, but a standalone long description is not always provided.
• Third-party review platform badges link to external sites whose accessibility we do not control.
• Older articles may contain content authored before our current standard was in place.

We treat each of these as work to be done rather than as acceptable.

Tell us if something does not work

If any part of this site is difficult to use, we want to hear about it, and we will treat it as a defect.

• Email hello@agiletech.vn with "Accessibility" in the subject line
• Phone (+84) 989 324 830

Please tell us the page and what happened. We aim to acknowledge within five working days. If you need information from this site in a different format, ask and we will provide it.

Accessibility in the software we build

We apply the same standard to client work. Accessibility requirements are captured during discovery rather than retrofitted, which matters most in sectors where it is a legal obligation. Our education platforms and healthcare systems are built to be usable by people with disabilities from the outset, because in those sectors an inaccessible system is an unusable one.