Web Accessibility

What to do if you cannot access parts of this website:

Christ Church is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

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

If you have difficulties accessing content or wish to discuss provision of an alternative format, please contact the Alumni and Development Office at: development.office@chch.ox.ac.uk

If you cannot find sufficient information on our ‘find us’ page, call +44 (0)1865 276150 or email us at porters@chch.ox.ac.uk for directions.

Reporting accessibility problems with this website:

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: webmaster@chch.ox.ac.uk

Web Accessibility Statement:

Perceivable – Information and user interface components must be presentable to users in ways they can perceive.
1. Text Alternatives – Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
  1. Non-text Content – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. – Sufficient
2. Time-based Media – Provide alternatives for time-based media.
  1. Audio-only and Video-only (Pre-recorded) – For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such. – Does Not Apply
  2. Captions (Pre-recorded) – Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labelled as such. – Does Not Apply
  3. Audio Description or Media Alternative (Pre-recorded) –An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labelled as such. – Does Not Apply
  4. Captions (Live) – Captions are provided for all live audio content in synchronized media. – Does Not Apply
  5. Audio Description (Pre-recorded) – Audio description is provided for all pre-recorded video content in synchronized media. – Does Not Apply
  6. Sign Language (Pre-recorded) – Sign language interpretation is provided for all pre-recorded audio content in synchronized media. – Does Not Apply
  7. Extended Audio Description (Pre-recorded) – Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all pre-recorded video content in synchronized media. – Does Not Apply
  8. Media Alternative (Pre-recorded) – An alternative for time-based media is provided for all pre-recorded synchronized media and for all pre-recorded video-only media. – Does Not Apply
  9. Audio-only (Live) – An alternative for time-based media that presents equivalent information for live audio-only content is provided. – Does Not Apply
3. Adaptable – Create content that can be presented in different ways (for example simpler layout) without losing information or structure. – Sufficient
  1. Info and Relationships – Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. – Sufficient
  2. Meaningful Sequence – When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. – Sufficient
  3. Sensory Characteristics – Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, colour, size, visual location, orientation, or sound. – Sufficient
  4. Orientation – Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. – Sufficient
  5. Identify Input Purpose – The purpose of each input field collecting information about the user can be programmatically determined when. – Sufficient
  6. Identify Purpose – In content implemented using mark-up languages, the purpose of User Interface Components, icons, and regions can be programmatically determined. – Advisory
4. Distinguishable – Make it easier for users to see and hear content including separating foreground from background.
  1. Use of Colour – Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. – Advisory
  2. Audio Control – If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. – Does Not Apply
  3. Contract (Minimum) – The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: – Sufficient
  4. Resize Text – Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. – Sufficient
  5. Images of Text – If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: – Advisory
  6. Contrast (Enhanced) – The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: – Sufficient
  7. Low or No Background Audio – For pre-recorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: – Does Not Apply
  8. Visual Presentation – For the visual presentation of blocks of text, a mechanism is available to achieve the following:
    - Foreground and background colours can be selected by the user. – Sufficient
    - Width is no more than 80 characters or glyphs (40 if CJK). – Sufficient
    - Text is not justified (aligned to both the left and the right margins). – Sufficient
    - Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. – Sufficient
    - Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. – Sufficient
  9. Images of Text – Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. – Sufficient
  10. Reflow – Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
    - User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; – Advisory
    - Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. – Advisory
  11. Non-text Contrast – The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent colour(s): – Sufficient
  12. Text Spacing – In content implemented using mark-up languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: – Advisory
  13. Content on Hover or Focus – Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: – Sufficient
Operable – User interface components and navigation must be operable.
1. Keyboard Accessible – Make all functionality available from a keyboard.
  1. Keyboard – All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. – Advisory
  2. No Keyboard Trap – If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. – Sufficient
  3. Keyboard (No Exception) – All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. – Sufficient
  4. Character Key Shortcuts – If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
    - Turn off: A mechanism is available to turn the shortcut off; – Failures
    - Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt); – Failures
    - Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus. – Failures
2. Enough Time – Provide users enough time to read and use content.
  1. Timing Adjustable – For each time limit that is set by the content, at least one of the following is true:
    - Turn off: The user is allowed to turn off the time limit before encountering it; or – Advisory
    - Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or – Advisory
    - Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or – Advisory
    - Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or – Advisory
    - Essential Exception: The time limit is essential and extending it would invalidate the activity; or – Advisory
    - 20 Hour Exception: The time limit is longer than 20 hours. – Advisory
  2. Pause, Stop, Hide – For moving, blinking, scrolling, or auto-updating information, all of the following are true: Show full description – Sufficient
  3. No Timing – Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. – Sufficient
  4. Interruptions – Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. – Sufficient
  5. Re-authenticating – When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. – Failures
  6. Timeouts – Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions. – Advisory
3. Seizures and Physical Reactions – Do not design content in a way that is known to cause seizures or physical reactions.
  1. Three Flashes or Below Threshold – Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. – Sufficient
  2. Three Flashes – Web pages do not contain anything that flashes more than three times in any one second period. – Sufficient
  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. – Sufficient
4. Navigable – Provide ways to help users navigate, find content, and determine where they are.
  1. Bypass Blocks – A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. – Advisory
  2. Page Titled – Web pages have titles that describe topic or purpose. – Sufficient
  3. Focus Order – If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. – Sufficient
  4. Link Purpose (In Context) – The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. – Sufficient
  5. Multiple Ways – More than one way is 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. – Advisory
  6. Headings and Labels – Headings and labels describe topic or purpose. – Sufficient
  7. Focus Visible – Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. – Sufficient
  8. Location – Information about the user's location within a set of Web pages is available. – Sufficient
  9. Link Purpose (Link Only) – A mechanism is 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. – Advisory
  10. Section Headings – Section headings are used to organize the content. – Sufficient
5. Input Modalities – Make it easier for users to operate functionality through various inputs beyond keyboard.
  1. Pointer Gestures – All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. – Sufficient
  2. Pointer Cancellation – For functionality that can be operated using a single pointer, at least one of the following is true: – Sufficient
  3. Label in Name – For user interface components with labels that include text or images of text, the name contains the text that is presented visually. – Sufficient
  4. Motion Actuation – Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: – Does Not Apply
  5. Target Size – The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: – Advisory
  6. Concurrent Input Mechanisms – Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. – Sufficient
Understandable – Information and the operation of the user interface must be understandable.
1. Readable – Make text content readable and understandable.
  1. Language of Page – The default human language of each Web page can be programmatically determined. – Advisory
  2. Language of Parts – The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. – Sufficient
  3. Unusual Words – A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. – Failures
  4. Abbreviations – A mechanism for identifying the expanded form or meaning of abbreviations is available. – Failures
  5. Reading Level – When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. – Sufficient
  6. Pronunciation – A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. – Failures
2. Predictable – Make Web pages appear and operate in predictable ways.
  1. On Focus – When any user interface component receives focus, it does not initiate a change of context. – Sufficient
  2. On Input – Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component. – Advisory
  3. Consistent Navigation – Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. – Sufficient
  4. Consistent Identification – Components that have the same functionality within a set of Web pages are identified consistently. – Sufficient
  5. Change on Request – Changes of context are initiated only by user request or a mechanism is available to turn off such changes. – Advisory
3. Input Assistance – Help users avoid and correct mistakes.
  1. Error Identification – If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. – Sufficient
  2. Labels or Instructions – Labels or instructions are provided when content requires user input. – Advisory
  3. Error Suggestions – If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. – Sufficient
  4. Error Prevention (Legal, Financial, Data) – For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: – Advisory
  5. Help – Context-sensitive help is available. – Sufficient
  6. Error Prevention (All) – For Web pages that require the user to submit information, at least one of the following is true: – Sufficient
Robust – Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
1. Compatible – Maximize compatibility with current and future user agents, including assistive technologies.
  1. Parsing – In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. – Advisory
  2. Name, Role, Value – For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. – Failures
  3. Status Message – In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. – Failures