Old Joe accessibility

At the University of Birmingham, we want to ensure that as many people as possible can use our website, and we are working to improve our digital services.

This accessibility statement covers the website www.oldjoe.co.uk. This accessibility statement is currently being reviewed to confirm that the Old Joe website now meets the recommended government standard for web accessibility (WCAG 2.1 AA).

We aim to achieve the recommended government standard for web accessibility (WCAG 2.1 AA). As a user with accessible needs, 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

We also aim to make the website text as simple as possible to understand.

If you have a disability, AbilityNet has advice on making your device easier to use.

How accessible this website is

We know some parts of this website aren’t fully accessible. We are working on these parts of the site and are committed to producing an accessible site for all users. The accessibility problems affect the following areas:

  • Non-text content should have a text alternative eg alt tags or be marked up to be ignored by assistive technology
  • Information and relationships should be accessible if conveyed through presentation, well organised and regions of a page should be identifiable.
  • Form fields should include autocomplete attributes where appropriate
  • Meaning should not be conveyed solely through colour
  • The site should avoid using low-contrast text/backgrounds, graphics and interactive UI components and elements
  • To make it easy to resize text, texts and text containers should be defined in relative units rather than in pixels.
  • Text spacing should not use pixels for defining the height and spacing (e.g. height, line height, etc) of text boxes.
  • Content that appears on Hover or Focus should be fully accessible.
  • All functionality should be available to a keyboard to avoid relying exclusively on pointer-driven events.
  • The content should be operable through a keyboard interface
  • Motion animation triggered by interaction can be disabled, unless essential
  • Blocks of content that are repeated on multiple web pages should be able to be bypassed.
  • Each web page should have a title tag that is descriptive, informative, and unique.
  • Link purpose should be clear from the link text alone, or from the link text and surrounding content
  • Multiple ways should be available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
  • The website should support keyboard focus styles that are highly visible
  • Information about the user's location within a set of Web pages should be available.
  • The accessible name for a UI element must contain any visual label for the element.
  • The size of the target for pointer inputs should be large enough to use easily.
  • The website should provide a language attribute on the page's html element.
  • Errors when completing forms should be clearly indicated for all users.
  • Labels or instructions should be provided when content requires user input, with text instructions that describes the necessary input.
  • If an input error is automatically detected and suggestions for correction are known, then the suggestions should be provided to the user where possible.

What to do if you can’t access parts of the www.oldjoe.co.uk website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please email accessibility@contacts.bham.ac.uk. We’ll consider your request and get back to you within 10 days.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website and are continuing to audit our content. If you find something that you are unable to access, or we have failed to identify a barrier, please let us know. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, please email accessibility@contacts.bham.ac.uk

Enforcement procedure

If you are unhappy with the response you have received from the University about your accessibility-related issue, you can make a complaint to the University by emailing accessibility-complaint@contacts.bham.ac.uk.

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 University of Birmingham is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

 

Non accessible content

The content listed below is non-accessible for the following reasons:

1.1.1: Non-text content:

  • All non-text content that is presented to the user should have a text alternative that serves the equivalent purpose
  • Short text alternatives for non-text content should be provided that serves the same purpose and presents the same information as the non-text content (if a short description will suffice) eg alt tags
  • If the non-text content should be ignored by assistive technology, the non-text content should be marked or implemented so that it will be ignored by assistive technology

1.3.1: Information and relationships

  • Information, structure, and relationships conveyed through presentation should be programmatically determined or are available in text.
  • Pages should be organised using properly nested HTML headings. For example, the Old Joe Edition page has no headings, and articles do not have proper heading nesting.
  • ARIA landmarks and labels should be used to identify regions of a page.

1.3.5: Identify input purpose

  • If a form field asks for information about the user and if there is an appropriate HTML autocomplete attribute, the form should include that autocomplete attribute.

1.4.1 Use of Colour

  • Links should always be easily identifiable through non-colour means, including both default and hover states. The easiest and most conventional way to signify links is underlining. In this case, the Old Joe brand logo link has no hover or obvious indication it is a hyperlink.

1.4.3 Contrast (Minimum)

  • Text (including images of text) should have a contrast ratio of at least 4.5:1. For text and images of that is at least 24px and normal weight or 19px and bold, use a contrast ratio that is at least 3:1. The Old Joe website includes some very low-contrast text/backgrounds such as the Contact Us page title and some of the footer.

1.4.4 Resize text

  • Texts and text containers should be defined in relative units (percents, ems, rems) rather than in pixels.

1.4.11 Non-text Contrast

  • Colour contrast for graphics and interactive UI components must be at least 3:1 so that different parts can be distinguished.
  • When providing custom states for elements (e.g. hover, active, focus), colour contrast for those states should be at least 3:1.

1.4.12 Text Spacing

  • The site should not use pixels for defining the height and spacing (e.g. height, line height, etc) of text boxes.

1.4.13 Content on Hover or Focus

  • Tooltips should follow corresponding ARIA authoring practice.
  • For content that appears on hover and focus: the content should be dismissible with the escape key; the content itself can be hovered over; and the content should remain available unless it is dismissed, it is no longer relevant, or the user removes hover and focus. On the Old Joe website, the Edition page read-more hovers are not dismissable and do not appear when using keyboard-only navigation.
  • To the extent possible, content that appears on hover or focus should not obscure other content, unless it presents a form input error or can be dismissed with the escape key.

2.1.1 Keyboard

  • All functionality should be available to a keyboard without requiring specific timing of keystrokes, unless the functionality cannot be provided by a keyboard alone.
  • The site should avoid relying exclusively on pointer-driven events, such as on mouseover, to provide functionality when scripting. Generally, such functionality will also require scripting for keyboard operability.

2.1.3 Keyboard (No Exception)

  • All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

2.3.3 Animation from Interactions

  • Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.

2.4.1 Bypass Blocks

  • A mechanism should be available to bypass blocks of content that are repeated on multiple web pages.

2.4.2 Page Titles

  • Each web page should have a title tag that is descriptive, informative, and unique. The Old Joe Edition page titles are not descriptive enough nor unique.

2.4.4 Link Purpose (In Context)

  • The purpose of each link should be able to be determined from the link text alone, or from the link text and the containing paragraph, list item, or table cell, or the link text and the title attribute.
  • If the visible text alone is not sufficient to convey meaning, the site should use advanced techniques to provide additional meaning, such as ARIA attributes, screen reader only text, or the title attribute.

2.4.5 Multiple Ways

  • More than one way should be available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. The Old Joe article pages do not provide hierarchy info for their parent edition. 

2.4.7 Focus Visible

  • The website should support keyboard focus styles that are highly visible, and make sure that a visible element has focus at all times when using a keyboard. Do not rely on browser default focus styles. The article links on the Old Joe edition pages are not clearly highlighted when tabbed to.

2.4.8 Location

  • Information about the user's location within a set of Web pages should be available.

2.4.9 Link Purpose (Link Only)

  • A mechanism should be available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. The Old Joe Article links on edition pages do not provide clear text identifying the target page. 

2.5.3 Label in Name

  • The accessible name for a UI element must contain any visual label for the element. Accessible names for UI elements should match visual labels as closely as possible.

2.5.5 Target Size

  • The size of the target for pointer inputs should be at least 44 by 44 CSS pixels except when the target is available through an equivalent link or control on the same page that is at least 44x44; the target is in a sentence or block of text; the size of the target is determined by the user agent and is not modified by the author; or a particular presentation of the target is essential to the information being conveyed. Most items on the Old Joe website conform but the social media buttons are too small. 

3.1.1 Language of Page

  • The website should provide a language attribute on the page's html element.

3.3.1 Error Identification

  • The website should programmatically indicate required fields using the required or aria-required attributes. Also, the site should visually indicate required fields in the form's instructions or form labels. Do not indicate required fields for CSS alone.
  • The site should make errors easy to discover, identify, and correct.
  • The site should identify errors using aria-invalid.

3.3.2 Labels or Instructions

  • Labels or instructions should be provided when content requires user input.
  • The site should provide text instructions at the beginning of a form or set of fields that describes the necessary input.
  • When providing inline help text, the site should use aria-described by to associate the help text with the input.

3.3.3 Error Suggestion

  • If an input error is automatically detected and suggestions for correction are known, then the suggestions should be provided to the user, unless they would jeopardise the security or purpose of the content.

 

Content that is not within the scope of the accessibility regulations

PDFs and other documents

  • Many of our older PDFs and Word documents published before 23 September 2018 do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2.
  • The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. Any new PDFs or Word documents we publish will meet accessibility standards.

How we tested this website

This website was last tested in December 2019. The test was carried out by our trusted agencies, focusing on representative pages which contain the main features used across the site.

What we’re doing to improve accessibility

We aim that the following changes will be made:

  • We will address out of date elements, custom code and features (identified as Non-Accessible Content above) by May 2020.
  • We will update video captions, or remove older videos without captions, by September 2020
  • We will update our alt-text on images by September 2020

Change log

This statement was prepared on 27 January 2020. It was first published on 13 February 2020.