Some forms and booking pages we publish are hosted on Microsoft platforms (Microsoft Forms, Microsoft Bookings and Dynamics 365 marketing forms). Some elements of the forms do not meet WCAG 2.2 accessibility standards.
The underlying code for these pages is generated by Microsoft and we are not able to change it.
Testing of a sample of these forms in May 2026 identified the issues listed below. Because the code is the same across each platform, these issues are likely to affect other forms we publish using the same tools:
- The page does not declare which language it is written in, so screen readers may pronounce content incorrectly. This particularly affects our bilingual Welsh and English pages. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page)
- Some interactive controls, including service selection options and "read more" controls, cannot be reached or operated using a keyboard alone. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard)
- Sets of radio buttons and checkboxes are not grouped together with a group name, so screen reader users may not hear what the set of options relates to. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)
- Page layout is built using tables that are not hidden from assistive technology, and some text that looks like a heading is coded as ordinary text. This means screen readers announce the structure of the page incorrectly. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships)
- Longer pages do not have enough headings to navigate by, and some headings contain no text at all. This makes it harder for screen reader users to move around the page. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels)
- Pages do not include a skip link or a main content landmark, so keyboard and screen reader users have to move through the header content every time. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks)
- Fields that collect personal details, such as name, email address, telephone number, address, postcode and date of birth, do not identify their purpose. This stops browsers offering to fill them in automatically and removes support that some assistive technology relies on. This fails WCAG 2.2 success criterion 1.3.5 (Identify Input Purpose)
- Date pickers and other custom controls do not describe themselves correctly to assistive technology. The calendar is presented as a flat list of buttons with no week or day-of-week structure, and some text that is not interactive can be given keyboard focus. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)
- In places, two separate controls share the same identifier in the code. This can cause screen readers to announce the wrong label for a control or to miss it altogether. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value)
- Some links open in a new tab or window without telling you in advance. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context))
What we are doing about it
We have reported these issues to Microsoft. As the code is created and controlled by Microsoft, we cannot fix them ourselves and we cannot give a date by which they will be resolved.
If you are unable to use one of our forms or booking pages, contact us on 0800 028 4844 or at post@careerswales.gov.wales and we will complete it with you, or provide the same information and service in a format that works for you. We aim to respond within 2 working days.