Skip to main content
We use essential cookies to make our site work. We'd also like to set optional cookies to help us improve it. Select ‘Accept’ if you wish to accept optional cookies. A link to the full Cookies Policy can be found at the bottom of this page.
Settings
Official Injury Claim homepage
English |
| Cymraeg
  • Content has heading markup, but is not a heading. This fails under: 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA)
  • Heading markup is missing for headings. This fails under: 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA)
  • Empty heading element is used. This fails under: 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA)
  • Tabular data is provided using layout or CSS without table markup. This fails under: 1.3.1 Info and Relationships (Level A)
  • Data tables are missing table header markup. This fails under: 1.3.1 Info and Relationships (Level A)
  • List markup is missing for list items. This fails under: 1.3.1 Info and Relationships (Level A)
  • Landmarks are not used correctly on the page. This fails under: 1.3.1 Info and Relationships (Level A)
  • Content is being misread by screen readers. This fails under: 1.3.1 Info and Relationships (Level A) and 4.1.2 Name, Role, Value (Level A)
  • List markup used on non-list items. This fails under: 1.3.1 Info and Relationships (Level A)
  • Information conveyed through the presentation is not replicated programmatically. This fails under: 1.3.1 Info and Relationships (Level A)
  • Content is not keyboard accessible. This fails under: 2.1.1 Keyboard (Level A)
  • Content is causing a keyboard trap. This fails under: 2.1.2 No Keyboard Trap (Level A)
  • Form fields are not associated with text labels. This fails under: 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A)
  • (HTML) Groups of related form fields are not grouped using Fieldset and Legend. This fails under: 1.3.1 Info and Relationships (Level A), 3.3.2 Labels or Instructions (Level A) and 4.1.2 Name, Role, Value (Level A)
  • An input has an incorrect programmatic purpose. This fails under: 1.3.1 Info and Relationships (Level A) and 1.3.5 Identify Input Purpose (Level AA)
  • Required fields are not clearly marked. This fails under: 3.3.2 Labels or Instructions (Level A)
  • Labels for form fields are missing or are not accurate. This fails under: 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A)
  • It is difficult for non-sighted users to identify which form has an error. This fails under: 3.3.1 Error Identification (Level A), 3.3.2 Labels or Instructions (Level A) and 3.3.3 Error Suggestion (Level AA)
  • When a user submits a form and an error is detected, non-sighted users aren't aware of the error notification. This fails under: 3.3.1 Error Identification (Level A), 3.3.3 Error Suggestion (Level AA) and 4.1.3 Status Messages (Level AA)
  • Error messages are not programmatically associated with the relevant input. This fails under: 3.3.1 Error Identification (Level A)
  • Error suggestion is not clear. This fails under: 3.3.3 Error Suggestion (Level AA)
  • Dynamic changes or status updates are not being conveyed to assistive technologies. This fails under: 1.3.3 Sensory Characteristics (Level A) and 4.1.3 Status Messages (Level AA)
  • Content becomes lost or obscured at low resolution or scrolling in 2 dimensions is required (reflow 320 x 256). This fails under: 1.4.10 Reflow (Level AA)
  • There is no feature available that allows a user to skip blocks of repetitive content. This fails under: 2.4.1 Bypass Blocks (Level A)
  • The page title does not accurately describe the page content. This fails under: 2.4.2 Page Titled (Level A)
  • Focus order is incorrect or illogical. This fails under: 2.4.3 Focus Order (Level A)
  • Link text is not descriptive of the destination page. This fails under: 2.4.4 Link Purpose (In Context) (Level A)
  • Content changes on input without informing the user. This fails under: 3.2.2 On Input (Level A)
  • Code quality issues (parsing) mean that some of the content may not be accessible via software used by people with disabilities. This fails under: 4.1.1 Parsing (Level A)
  • Expanding controls need appropriate name, role and value. This fails under: 4.1.1 Parsing (Level A)
  • Components are missing appropriate name, role or value. This fails under: 4.1.1 Parsing (Level A)
  • Additional information should be programmatically associated with relevant data. This fails under: 1.3.1 Info and Relationships (Level A) and 4.1.2 Name, Role, Value (Level A)
  • Content is restricted when orientation changes. This fails under: 1.3.4 Orientation (Level AA)
  • A down-event selects a function. This fails under: 2.5.2 Pointer Cancellation (Level A)
  • Button text is not descriptive of purpose

Links

About Official Injury Claim
Accessibility and Inclusion Information
Claimant resources
Ministry of Justice Whiplash Reforms Programme
Cross