Accessibility Statement - Royal Navy
How is our website accessible?
Accessiblity statement
This website is run by the Ministry of Defence. We want as many people as possible to be able to use this website. For example, that means you should be able to:
change colours, contrast levels and fonts
zoom in up to 200% without the text spilling off the screen
navigate most of the website using just a keyboard
navigate most of the website using speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
How accessible this website is
We know some parts of this website are not fully accessible:
Zoom to 200% when on any forms will cause the dropdown options to not render correctly and some buttons which have a fixed width.
Zoom to 200% on change of circumstances causes the table of contents when compared difficult to navigate.
Search input field is missing an associated label
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: People-DMBfeedback@mod.gov.uk
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
The Ministry of Defence is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Non accessible content
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Disproportionate burden
When zooming 200% some dropdown options will not render correctly and same for some fixed width buttons. This fails WCAG 1.4.4 Resize text.
The search benefits text input field is missing a associate label. This fails WCAG 2.1 1.3.1, 3.3.2 Form <input> elements must have labels.
We’ve assessed the cost of fixing the above issues. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in August 2021.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value). Some of our PDFs and Word documents are essential to providing further information on our services. For example, we have PDFs with information on how users can access our services.
How we tested this website
This website was last tested on 8th June 2020. The test was carried out by Great State.To help us make the Discover My Benefits website a positive place for everyone, we've been using the Web Content Accessibility Guidelines (WCAG) 2.1. These guidelines explain how to make web content accessible for people with disabilities, and more user friendly for everyone. This site has been built using code compliant with W3C standards for HTML and CSS. The guidelines have three levels of accessibility (A, AA and AAA). We’ve chosen Level AA as the target for the Discover My Benefits website. Discover My Benefits website was built to achieve level Double-A of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines 2.1.Discover My Benefits website allows for (WCAG) 2.1 Level AA, as with all websites with dynamic content and the need for regular content changes, this depends on the content being compliant to the Web Content Accessibility Guidelines 2.1. All templates were checked manually for keyboard navigation, hover states and colour contrast. Automated tools were used to aid the necessary checks needed and speed up reporting of potential issues.We tested:
our main website platform, available at
This statement was prepared on 25th October 2019. It was last updated on 9th June 2020.