The WCAG 2.2 design principles are supported by 13 guidelines. Each of these is broken down into specific requirements (or ‘success criteria’) that your service needs to meet. You should use a combination of automated tools and manual tests (including those listed in Testing for accessibility) to identify potential problems. Tel (during 9am - 5pm (GMT) Monday to Friday): (+44) (0)20 7930 4832. Please note, calls to this number may be recorded

By focusing on principles, not technology, they emphasise the need to think about the different ways that people interact with content. For example, users might:The postal code system in the UK can pinpoint a location precisely and is therefore used for accurate information about location. make sure your service works well with assistive technologies - for example, important messages are marked up in a way that the screen readers knows they’re important

use the proper markup for every feature (for example, forms and data tables), so the relationships between content are defined properly Media enquiries regarding the Royal Collection and visiting the Royal residences should be directed to the Royal Collection Trust Press Office.make sure your code lets assistive technologies know what every user interface component is for, what state it’s currently in and if it changes To meet WCAG 2.2 Principle 1: Perceivable you need to make sure users can recognise and use your service with the senses that are available to them. You’ll also need to get an accessibility audit before your beta assessment to provide evidence that your service meets level AA. Principle 1: Perceivable make it easy for people to identify and correct errors in forms - you can find best practice for form design in the GOV.UK Design System