Accessibility statement

Target standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. Level AA is the benchmark most widely required by legislation and public procurement worldwide.

Where we are now

Every main page — home, schedule, programs, for organizations, blog, the legal pages, all four pages with a form (contact, request information, for organizations, course registration), and the sign-in, password-reset and “page not found” pages — is tested at two widths: desktop (1280 pixels) and mobile (375 pixels). The test covers every automatically checkable rule at levels A and AA of WCAG 2.0, 2.1 and 2.2. The most recent run found no violations. Blog posts are not tested one by one: they all use the same template, so one representative post is tested.

This is not a one-off report. The test is kept alongside the site's code and is run again after every change, so this statement does not go stale.

Automated testing does not catch every accessibility barrier. That is why the known limitations are listed separately below, and why hearing from you matters.

What is in place

• Every page starts with a “Skip to main content” link — it appears as soon as you start moving through the page from the keyboard (the Tab key).
• Navigation, links, buttons and form fields all work from the keyboard alone. There are no custom mouse-only controls; everything is built on standard browser elements. The focused element is always shown with a clear outline.
• Menu items, buttons and form fields have a 44-pixel touch target (menu items on narrow screens are 40 pixels). Filter and choice chips are 36 pixels. All of these are above the 24-pixel WCAG minimum. Links inside text and in link lists keep the height of their line — the standard exempts those where neighbouring links are at least 24 pixels apart, and the automated test checks that on every page.
• Fonts are served from our own server, so text does not depend on an outside font service being available.
• There are no advertising scripts. Google Analytics, which counts visits, loads only after you choose “Allow” in the bar near the top of the page; if you decline, or make no choice at all, no request is ever sent to Google. You can change your choice at any time with the “Cookie settings” button in the footer.
• The Mongolian and English versions each declare their own language, so screen readers use the right pronunciation.

Known limitations

We are aware of the following and have not yet fixed them:

• The four pages with a form (contact, request information, for organizations, course registration) load the Cloudflare Turnstile bot-protection widget from a third-party server. For most visitors it passes silently, but it can present an extra challenge, and the accessibility of that challenge is outside our control. If it blocks you, please call or email us instead — you can register without the form.
• The tugrik sign ₮ is missing from the site's main font, so the browser draws it from a substitute font. Prices remain readable, but the sign looks slightly different from the digits beside it.
• A few images in older blog posts migrated from the previous site carry no descriptive text — they were treated as decorative, so screen readers skip them. Where an image carries meaning, we add a description.

Reporting a problem

If anything on this site is hard to use, please tell us. Saying which page it was, and which device, browser or assistive software (screen reader, magnifier) you were using, makes it far easier to fix.

Contact us:

• info@dalecarnegie.mn
• +976 7000 0330
• Contact form

We reply within 30 days of receiving your message — the same period stated in our privacy policy.