Tower House Surgery
Map PointerTower House Surgery, 169 West Wycombe Road, High Wycombe, Bucks, HP12 3AF
Appointments: 01494 526840
Out of Hours Service: 111

Surgery Opening Times

Monday7.15am - 1.00pm, 2.00pm - 6.30pm
Tuesday8.00am - 1.00pm, 2.00pm - 6.30pm
Wednesday7.15am - 1.00pm, 2.00pm - 8.00pm
Thursday8.00am - 1.00pm, 2.00pm - 6.30pm
Friday8.00am - 1.00pm, 2.00pm - 8.00pm


How accessible this website is

It was assessed that it would not be reasonable to make this website accessible because it is a disproportionate burden.

Compliance Status

This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, and the non-compliances are listed below.

Non-accessible content

1. Perceivable

  • 1.1 Non-text Content
    • Non-text content do not always have text alternatives.
  • 3.1 Info and Relationships
    • Headings are not always structured.
    • Regions of a page are not identified.
    • Form interface controls use table layout.
    • Form controls are not grouped.
    • Errors are not announced to screen readers.
  • 3.2 Meaningful Sequence
    • Content is not provided entirely in the correct reading sequence.
  • 3.4 Orientation
    • Content is not responsive and restrict its view and operation to a single display orientation.
  • 3.5 Identify Input Purpose
    • The purpose of input fields cannot always be programmatically determined
  • 3.6 Identify Purpose
    • The purpose of icons, regions and user interface components cannot be programmatically determined.
  • 4.3 Contrast (Minimum)
    • Many elements on the page have low contrast ratio.
  • 4.4 Resize text
    • Text cannot be resized without loss of content or functionality.
  • 4.5 Images of Text
    • Images of text are sometimes used to convey information.
  • 4.6 Contrast (Enhanced)
    • Many elements on the page have low contrast ratio.
  • 4.8 Visual Presentation
    • Width is more than 80 characters.
    • Line spacing is not sufficient.
    • Text cannot be resized without horizontal scroll.
  • 4.10 Reflow
    • Content cannot be presented without loss of information or functionality in mobile screens.
  • 4.11 Non-text Contrast
    • User interface components and graphical objects do not have sufficient contrast ratio.
  • 4.12 Text Spacing
    • Changing some style properties as line height, spacing following paragraphs, letter spacing and word spacing can cause loss of content or functionality.

2. Operable

  • 1.1 Keyboard
    • The website is not completely operable through a keyboard interface.
  • 1.3 Keyboard (No Exception)
    • The website is not completely operable through a keyboard interface.
  • 4.1 Bypass Blocks
    • There is no mechanic available to bypass blocks of content that are repeated on multiple pages.
  • 4.3 Focus Order
    • Content cannot be always navigated sequentially.
  • 4.4 Link Purpose (In Context)
    • The purpose of each link cannot always be determined from the link text alone.
  • 4.7 Focus Visible
    • Multiple keyboard operable user interfaces do not have any keyboard focus indicator.
  • 4.8 Location
    • There is no way for the user to orient himself within a set of pages.
  • 4.9 Link Purpose (Link Only)
    • The purpose of each link cannot always be determined from the link text alone.
  • 4.10 Section Headings
    • Headings do not always provide titles to sections or are organized in a comprehensive order.
  • 5.5 Target Size
    • The target size for pointer inputs is not sufficient.

3. Understandable

  • 1.4 Abbreviations
    • There is not mechanism for identifying the expanded form or meaning of abbreviations.
  • 2.2 On Input
    • Changing the setting of some user interface components automatically cause a change of context.
  • 2.4 Consistent Identification
    • Components that have the same functionality can have different layouts and structures.
  • 3.1 Error Identification
    • Errors during form submissions are not alerted to assistive technologies.
  • 3.3 Error Suggestion
    • Errors suggestions are not always provided while filling a form.
  • 3.6 Error Prevention (All)
    • Users are not able to reverse, check or confirm any information that is submitted.

4. Robust

  • 1.1 Parsing
    • Content does not have complete start and end tags.
  • 1.2 Name, Role, Value
    • Some user interface components do not have names and roles that can be programmatically determined.
  • 1.3 Status Messages
    • Status messages cannot be programmatically determined and presented by assistive technologies.