Accessibility Statement: What We Have Tested

Our position

This statement covers the whole site, which is run as described on the about page. We have not commissioned an independent accessibility audit, and we have not tested the site against the Web Content Accessibility Guidelines (WCAG). We therefore make no statement that the site is fully, partly or not conformant. What follows is what we know, and it may be incomplete.

What is built in

These are design and code choices you can verify in the page itself:

• Pages are plain HTML, written in British English and marked as such (lang="en-GB").
• A “Skip to main content” link is the first thing a keyboard user reaches on each page.
• Pages use landmark regions (header, navigation, main, footer), a single main heading and headings in order.
• Navigation regions have labels, and the menu buttons report whether they are open or closed. The desktop menu panels can be closed with the Escape key.
• Links and buttons show a visible focus outline when you tab to them.
• Data tables are real HTML tables with captions and header cells, and sit in a container that scrolls sideways on narrow screens instead of breaking the layout.
• Text is set in normal HTML text and can be enlarged in your browser. Fonts are served from this site.
• The layout is built for small screens first and includes a viewport setting, and there is a print style that removes menus and banners.
• The site does not use autoplaying audio or video, or flashing content.

What we have actually checked

On 8 October 2026 we ran a scripted structural check on all 54 pages of the site as it then stood. It looked for the following: the language attribute, exactly one main heading, no skipped heading levels, duplicate element identifiers, a working skip link, main, header and footer landmarks, labelled navigation regions, images without text alternatives, links and buttons without an accessible name, tables without captions or header cells, and external links opening in a new tab without safe-link attributes. It found no problems. Thirty-seven of those pages carry images, which are featured pictures and explanatory diagrams. The check confirmed that every image has a non-empty text alternative, but it cannot judge whether each description is good, and we have not reviewed every one by eye.

We also calculated the colour contrast of the main text colours against the page background. Body text, secondary text, muted text, links and the deeper coral used for warnings all came out above 4.5 to 1, the WCAG 2.2 AA minimum for normal text. We did not measure every colour combination on the site.

That is the full list. A scripted check can catch only some problems, and passing it is not the same as being accessible.

What we have not tested

• We have not tested with screen readers, screen magnifiers, voice control or switch devices, and we have not tested with disabled users.
• We have not tested every page, every browser or every screen size.
• We have not checked every colour combination, or how the site looks in high-contrast or forced-colour modes.
• We have not measured the size of touch targets or tested zoom to 400%.
• We have not evaluated whether the plain-English reading level of every page is suitable for every reader.

Known limitations

• The cookie banner sits at the end of the page code, so a keyboard or screen-reader user reaches it last, and it does not move focus to itself when it appears. It can be used by keyboard, but not as conveniently as it should be.
• There is not yet a control to reopen the banner after you have made a choice. The cookie policy explains how to reset it.
• Some guides are long. We use headings and short summaries to help, but we have not tested how well they work with assistive technology.
• Where we link to sources, such as National Health Service (NHS) pages, research papers and government sites, we do not control their accessibility.

Tell us about a problem

If you cannot read or use something on the site, or you need information in another format, email us at info@bestdentalturkey.clinic with the page address and a description of the difficulty. We will try to fix the problem or find another way to give you the information. You can also use the contact page. We will update this statement as we test more. How we handle any personal details you send us is explained in our privacy policy.

Last updated October 2026.