SECRETARY’S DEPARTMENT OFFICIAL DOCUMENT

This document is an official publication of the University. Queries about the content should be addressed to the department responsible.

Title: Web Development Requirements and Guidelines (2.2) Department Responsible: Marketing Approved by: Directorate Approval Date: 23 January 2003 Review Arrangements (if any). None specified

Web Development Requirements and Guidelines (Version 2.2)

Contents

1.0 Background 2.0 Requirements 3.0 Guidelines 4.0 Complaints and Dispute Procedure 5.0 Contacts, Feedback and Support

1.0 Background 1.1 Scope and Philosophy

This document is split into two sections: requirements and guidelines. Almost all content needs to comply with the requirements and it is hoped that all web authors will strive to meet as many of the guidelines as possible. These requirements and guidelines are intended to strike an appropriate balance between the freedom for individuals, projects, departments, Faculties and Divisions to publish information on the world wide web, and the desire to promote good practice in web publishing, promote the University by having a professional presence on the World Wide Web, and comply with certain legal requirements.

These requirements and guidelines apply to:

�� any web pages published within the IP domain mmu.ac.uk or any other domain registered to the University.

�� any web pages published on any computer with an IP address registered to the University.

They do not apply to:

�� FTP (file transfer protocol) sites �� Web pages published outside the University's IP domains and IP address

ranges

The requirements and guidelines have been produced by the University’s Web Development Team, and approved by Directorate. The requirements and guidelines have been drawn together from the results of extensive internal and external research, together with consultation throughout the University, and reflect good industry practice. The key concept behind these requirements and guidelines is to improve usability. It has been developed to help all web developers design unique sites that collectively combine to form one cohesive MMU web site. All

1

users, on entering mmu.ac.uk or any other domain owned by the University, should be able to:

�� view the content whatever their ability (as so far is reasonably

practicable) �� navigate to the Division/Faculty/Department’s top-level pages

(preferably the University's home page too) �� get in contact with someone concerning the content �� view their legal rights concerning the content

Another key concept of the requirements and guidelines is accessibility. The University wants to take a proactive stance to the needs of the visually and physically impaired community. Whilst also being good web development practice, making the University’s web pages accessible is a requirement of The Special Educational Needs and Disability Act 2001 (SENDA). The SENDA places a legal requirement on the University not to discriminate against disabled students in the supply of educational services. It must be stressed that these requirements and guidelines do not prohibit or inhibit the ability of faculties/departments/institutes/projects to publish content that is geared towards their subjects or are branded to their specifications.

1.2 Implementation Timetable and Compliance

All web pages must comply with the requirements by October 2003. The web development team will advise and actively assist web authors in order to achieve compliance by these dates. New content, however, should already comply with these requirements. Where content is created dynamically using legacy software or scripts authors should make reasonable efforts to ensure compliance. It is expected that all web authors will make every effort to make any necessary changes to their new and existing web pages within these timescales. However, if any difficulties are anticipated, you should contact the appropriate member of the Web Development Team or the Internet Manager, who will be able to advise on how to proceed. In the unlikely event of not being able to reach agreement on a way forward, a procedure for resolving difficulties is outlined in section 4.2 below. Contact details for the Web Development Team are available at: http://www.mmu.ac.uk/web/contacts.php

2

1.3 General Web Development Procedures

Before starting any major web development project*, web authors should inform either the Internet Manager or their relevant member of the Web Development Team.

* - Major web development means, for example, a new site. Certain core content is to be provided centrally, such as maps, “About the University” etc. Authors should not attempt to replicate or design their own but link back to the core content which is located in the resources section.

It is the author’s responsibility to remove their old content from the server.

1.4 Exceptions

Certain types of web resources may be unable to comply with these requirements and guidelines.

These are summarised in the requirements matrix (2.0). Web authors of these types of sites should make every reasonable effort to comply with as many requirements and guidelines as possible and can also contact the Internet Manager or a member of the web team for advice.

1.5 Revision

The Internet is a developing medium and these requirements and guidelines will be periodically revised (at least annually) by the Web Development Team following user testing and in response to major changes in technology. Comments and feedback will be considered during the annual review process.

3

2.0 REQUIREMENTS The following chart gives authors a summary of which types of content are required to adhere to which web requirements to ensure accessibility and usability. A glossary of the types of pages and a number of examples follow. �= Required R = Recommended

WEB REQUIREMENTS

Accessibility (2.1)

Meta Tags (2.2)

Search Link (2.3)

Department/ Faculty link

(2.3)

Identity/ Logo (2.4)

Contact us (2.3)

Legal Notice (2.5)

Guidelines (3.0)

Key Entry Pages �� � � � � � � R Documents

� � ���OR���

R R R

Large images PDF’s Interactive Pages

� R R

Personal Home Pages � � � � R FTP sites

Partnership or Joint Pages � � � Top

level � Top level Recommended

to have own disclaimer

R

Hosted sites � R

TYPE

S O

F PA

GES

3rd Party sites R R

5

2.1 Breakdown of Definitions and glossary of “Types of Pages” on MMU N.B. Pages that are dynamically generated using software or scripts have to adhere to the requirements of whatever types of pages that are being generated.

2.1.1 Key Entry Pages Pages that contain:

�� University wide information. For example http://www.mmu.ac.uk/news and http://www.mmu.ac.uk/academic.

�� Faculty or Department wide information. For example

http://www.business.mmu.ac.uk/ and http://www.mmu.ac.uk/h-ss/lan/.

�� Distinct entry points and navigation elements for recognisable

sections of the site. Such pages could be anywhere on the site including top level, faculty and department sites. For example http://www.mmu.ac.uk, http://www.fin.mmu.ac.uk, and http://www.mmu.ac.uk/h-ss/eng/welcome.html.

These pages must meet all the requirements:

�� Accessibility (2.1) �� Meta Tags (2.2) �� Search Link (2.3) �� Department/ Faculty link (2.3) �� Identity/ Logo (2.4) �� Contact us (2.3) �� Legal Notice (2.5)

It is recommended that they comply with:

�� Design and technical guidelines (3)

2.1.2 Documents These are pages that would be recognised as ‘end points’ in the navigation process rather than ‘way points’. This category covers the majority of web pages on any site, and would include:

�� Academic papers - pages that display academic material. For example http://www.docm.mmu.ac.uk/RESEARCH/virtual-museum/Pubs/dmu98pap.html

�� Course Materials inc. lecture notes - educational information made

available to students via the web. For example

6

http://www.msa.mmu.ac.uk/bioclimatic/stud_res.html and http://www.doc.mmu.ac.uk/online/IT-IS-Context/is14home.htm.

�� Discussion lists - Publication of discussions. For example

http://ehlana.mmu.ac.uk/archives/is-policy/maillist.html and http://cra.als.aca.mmu.ac.uk/wwwboard/bics99/default.htm.

�� Other Documents – Including policy statements, for example

http://www.isu.mmu.ac.uk/general/strategy-policies/policies/policy0002.shtml

These pages must meet the following requirements:

�� Accessibility (2.1) �� Meta Tags (2.2) �� Department/ Faculty link (2.3) OR Identity/Logo (2.4)

It is recommended that they comply with:

�� Contact us (2.3) �� Legal Notice (2.5) �� Design and technical guidelines (3)

2.1.3 Large images, PDF’s, Interactive Pages

Files that are clearly navigationally ‘stand alone’, and are not HTML or similar pages. Having arrived at the page, the user would not expect any navigation to other locations. For example http://www.mmu.ac.uk/news/mmyou/pdf/june_2002.pdf These pages must meet the following requirement:

�� Accessibility (2.1)

It is recommended that they comply with: �� Legal Notice (2.5) �� Design and technical guidelines (3)

2.1.4 Personal Home Pages

Pages that are expressly personal. Such pages could include http://www.doc.mmu.ac.uk/STAFF/D.Whiteley/index.html and http://www.mmu.ac.uk/h-ss/eco/Albertson/More.htm. These pages must meet the following requirements:

�� Accessibility (2.1) �� Meta Tags (2.2)

7

�� Department/ Faculty link (2.3) �� Legal Notice (2.5)

It is recommended that they comply with:

�� Design and technical guidelines (3)

2.1.5 FTP sites FTP (file transfer protocol) sites are beyond the remit of these guidelines.

2.1.6 Partnership or Joint Sites This category of pages include content that is jointly owned by different organisations including the Manchester Metropolitan University, but hosted on University servers or domains. For example: - http://www.thecontactpartnership.ac.uk/. These pages must meet the following requirements:

�� Accessibility (2.1) �� Meta Tags (2.2) �� Identity/ Logo (2.4) on the top level page �� Contact us (2.3) on the top level page

It is recommended that they comply with:

�� A suitable legal notice �� Design and technical guidelines (3)

2.1.7 Hosted Sites

Pages the University explicitly host for legal entities distinct from the University – for example http://www.syo.org.uk These pages must meet the following requirements:

�� Accessibility (2.1)

It is recommended that they comply with:

�� Design and technical guidelines (3)

2.1.8 3rd Party sites

8

Where an employee or student of the University publishes information or has information published on a web site by a third party, for example a discussion list hosted by another University, the publisher of an academic journal etc, they become the publisher of the information, and have ultimate control over the way in which it is presented. The University would wish to see all web publishers adopt sensible approaches to accessibility and usability, but recognise that the University have no control over this.

2.2 Examples of Requirements Example 1: If you are publishing course materials on your web site authors are required to make every reasonable effort to ensure that the content:

�� Complies with the accessibility guidelines �� Includes all five meta tags �� Includes either the MMU logo or a link to the top-level pages of your

site (departmental/faculty) �� Includes a link to the legal notice

It is recommended that the content also includes a contact mechanism and adheres to as many guidelines as possible. Example 2: If you are publishing on a personal home page you must make every reasonable effort to ensure that the content:

�� Complies with the accessibility guidelines �� Includes all five meta tags �� Includes a link to the top-level pages of your site

(departmental/faculty) �� Includes a link to the legal notice

It is recommended that the content also adheres to as many guidelines as possible.

Example 3:

If you are publishing a site which is a joint partnership with another organisation you are required to ensure that the content:

�� Complies with the accessibility guidelines �� Includes all five meta tags �� Includes the MMU logo on it’s top-level

It is recommended that the content also contains its own disclaimer and also adheres to as many guidelines as possible.

9

2.3 Accessibility Requirements

These requirements apply to all types of content except 3rd party sites. There may be limited exceptions to these requirements. Such reasons for not making pages accessible could be:

�� It is necessary to maintain academic standards �� It is necessary to maintain standards of any other prescribed kind

To maintain accessibility all web pages:

�� Must meet W3C priority 1 checkpoints of the W3C Web Accessibility Guidelines (http://www.w3.org/WAI/).

�� Should meet priority 2 checkpoints �� May meet priority 3 checkpoints The following is a summary of the Priority 1 level checklist that MMU web pages must meet. The full W3C checklists are maintained on the WC3 website - http://www.w3.org/TR/WCAG10/full-checklist.html.

2.3.1 Text equivalents

Always provide a text equivalent where the web page uses non-text element. This means use the alt tag for images, applets, scripts, spacers, frames, video etc.

2.3.2 Colour

Ensure that all information conveyed with colour is also available without colour. It is important that colour is not used to convey important information. "Click the green button to start" or "Required fields are in red." are obvious examples.

2.3.3 Language changes

Clearly identify changes in the natural language of a document's text and any text equivalents. For example, if you have sentence of French in your page, use <span lang="fr">raison d'être</span> to identify this.

2.3.4 Style sheet independence

Create documents so they may be read without style sheets. It is possible for users to apply their own style sheet to the documents, specifying, for example, a larger font size or a custom background colour.

2.3.5 Updating multiple versions

Ensure that equivalents for dynamic content are updated when the dynamic content changes. If you are offering audio or visual content such as sound

10

clips, QuickTime movies, photos, animations, diagrams etc, make sure to offer alternative formats. For example, transcripts of audio files, captions for video or detailed descriptions of the content of photographs.

2.3.6 Flickering

Do not cause the screen to flicker - either via animations, the BLINK tag or other means.

2.3.7 Content

Use the clearest and simplest language appropriate for a site's content. For example you should give a page a meaningful title.

Other tips are:

�� Keep paragraphs short. �� Limit each paragraph to one main idea. �� Highlight keywords. �� Use meaningful headings and sub-headings. �� Use bulleted lists. �� Use clear and simple language.

2.3.8 Images and image maps

Try to use client-side image maps rather than server-side ones (e.g. the co-ordinates should be within the HTML). If you do use server-side image maps, then you should provide textual links.

2.3.9 Tables

For data tables, identify row and column headers. For data tables that have two or more logical levels of row or column headers, use mark-up to associate data cells and header cells.

2.3.10 Frames

If you must use frames then TITLE each frame. Also use NOFRAMES at the end of every frameset with a textual equivalent of the frame content, including links.

2.3.11 Scripts and applets

Ensure that pages are usable when scripts, applets, or other objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.

2.3.12 If all else fails...

11

If you can't meet any of these requirements (e.g. the page doesn't work if JavaScript is turned off) then you need to provide an alternative page, e.g. a

text only page. It is recommended that the link to this page appears at the top of the original web page.

2.4 Meta Tags

This requirement applies to all types of content except pdf’s, interactive games, hosted pages and 3rd party sites.

There are five minimum tags, which are required to be in every HTML page. These help ensure consistency and enable your pages to be easily picked up and displayed correctly by search engines, including MMU’s:

2.2.1 Title

e.g.) <title>MMU - This is the Title</title>

N.B. Include “MMU -“ 2.2.2 Description

<meta name="description" content="This is the description"> Most search engines use this description on their result pages. It appears under the page title and gives users an overview of what the page is about. Pages without this tag usually have the first few lines of the page displayed.

2.2.3 Keywords

<meta name="keywords" content="keyword, keyword, keyword">

Search engines use the meta keywords field to find pages relevant to the enquiry made by the user. A page without keywords will appear much further down a listing than a page with keywords regardless of the content of the page.

2.2.4 Author

<meta name="author" content="author's name"> This is the name of the person who physically developed the page.

2.2.5 Sponsor

<meta name="sponsor" content="sponsor's name">

Every page must have a sponsor who is a member of MMU’s staff and is responsible for the content of the page. The sponsor may or may not be the same as the author. Under no circumstances is it permissible to publish a page which declares a sponsor who is not aware of this nomination.

12

Requirements are given below for who the sponsor must be for various types of content.

Academic Content - Author

Publishing of work in a field of academic endeavour in pursuance of an individual's employment with the University is the sole responsibility of the Author.

Contractual Content - University Secretary Contractual content is content that might reasonably be construed to enter the University into a contractual obligation notwithstanding the Disclaimer, for example advertising consultancy in specific areas at specific rates with 'guaranteed results'. Such content must be sponsored by the University Secretary. Avoiding specifics should generally be enough to stay clear of this category. If in doubt consult your Faculty Secretary.

University Information Content - Vice Chancellor, Deputy VC, University Secretary or External Relations Director

Any information which represents the University as a whole, must be sponsored by the Vice Chancellor, the Deputy Vice Chancellor, the University Secretary or the External Relations Director.

Faculties and Central Division Information Content - Dean or Director Any information which represents a faculty must be sponsored by the relevant Dean of Faculty. Similarly, such information regarding a central division shall be sponsored by the relevant Director.

Departmental Content Any information which represents a department must be sponsored by the relevant Head of Department.

2.3 Links This requirement applies to various types of content. The table at the start of

section 2 summarises which links are required for which types of pages.

�� A link to the Division/Faculty/Department’s top-level pages. �� A link (or form) to the University’s search engine

13

�� A “contact us” link or similar mechanism such as an email address for feedback.

�� Every web page which describes courses at MMU must have a link to

The Prospectus –. 2.4 Identity This requirement applies to key entry pages, documents and joint pages.

The University logo should provide a link back to the University homepage and preferably be placed in the top left hand corner of the page. Only the logos available from http://www.mmu.ac.uk/web/logo.php are acceptable, to be used with the following placement guidelines which have been prepared to ensure that the Manchester Metropolitan University brand mark is presented consistently throughout http://www.mmu.ac.uk. The logo comprises two elements: the "boxed star" symbol and the text "Manchester Metropolitan University" in a fixed relationship. Both elements must be used at all times. No attempt should be made to re-draw, distort or modify the logo in any way. The logo files already contain the University's clean space requirements. The logo must be allowed a visual separation from other elements and not be crowed or dominated by other images or typography. No attempt should be made to remove this clear space from the logo. Please note that the different styles of the logo have been designed to be used together but still achieve consistency. For example a page could use a block style (500 version) and the next page a banner style (500 version) but the star would remain in the same place. Please link the logo back to the MMU homepage and alt tag it - "MMU Homepage". The web colour of the logo is #003366 and has been provided in the different versions available from http://www.mmu.ac.uk/web/logo.php.

2.5 Legal Notice

This requirement applies to all key entry pages and personal home pages. It is a recommendation for all other types of pages published by the University within its own domain. It is recommended that third party sites and joint sites etc publishing within MMU’s domains should carry their own form of legal notice.

Pages shall carry a link to the legal notice that contains the University’s web disclaimer and notices on copyright and privacy - http://www.mmu.ac.uk/legal/.

14

2.5.1 Additional Privacy Statement and Data Protection All web pages that retrieve personal data from users must:

a) Include the following additional privacy statement:

Manchester Metropolitan University is fully committed to protecting your privacy.

MMU promises to keep your personal details private and secure. This means we will not pass any information you give us to a third party unless required to do so by law.

MMU welcomes your comments about privacy and this web site. Please send e-mails to web@mmu.ac.uk. For further information about privacy please see http://www.mmu.ac.uk/legal#privacy. b) Give people the option of not being contacted again by also including the following: “From time to time we may contact you with details of MMU products or services that we believe may be of interest to you. If you would prefer not to be contacted in this way, please check the box here.”

3.0 DESIGN AND TECHNICAL GUIDELINES

Below are detailed guidelines and suggestions, such as fonts, language and URL’s, which web authors could employ in their developments. The guidelines have been drawn up to improve the usability of the whole

15

mmu.ac.uk site. It is recommended that all authors will strive to meet as many of the guidelines as possible.

3.1 Consistency

When creating web pages, authors should aim towards consistency of design and navigation.

3.2 Standard Page Layout

Web authors should strive to design their pages to the MMU Standard Page Layout:

A – Identity

B – Navigation

C – Content

3.3 Typography

To promote consistency authors should use one of the University’s preferred web fonts; Verdana, Arial, Helvetica, Geneva – preferably in a style sheet.

3.4 Frames

Authors should avoid using frames unless they can provide a compelling reason to do so. Frames cause problems for search engines and for the user.

3.5 Under Construction

Do not publish any pages with the words “under construction” or “in development”. If they are not ready yet, please do not publish them!

3.6 Animations plus Flash/Shockwave and similar

Animation should be avoided, but if used should not loop indefinitely. Flash should only be used when there is an alternative version of the site for users without the appropriate plug-in, to conform to accessibility standards. Flash should be used with care, especially when used for navigation.

3.7 Design Credibility

16

Web authors should seriously consider the design credibility of their web pages prior to uploading or during any redesign programme. MMU’s top-level pages are designed to stand alongside high-profile commercial standard websites and give the impression of a professional organisation with high standards and a commitment to quality. Using amateur 'gizmos' can severely damage your professional credibility. The graphical design of your site, while not the most important aspect, is the first thing a user sees upon entering and is the first opportunity you have for establishing credibility.

3.8 Language

It is recommended that content on mmu.ac.uk should only be developed in English. It is preferable that html tags etc are also in English.

3.8 URL’s

URL’s (Uniform Resource Locator) should be marketed as short as possible for your department/faculty etc. e.g. http://www.mmu.ac.uk/english. Please see http://www.mmu.ac.uk/web/shorturl.php.

3.9 Page Width

To prevent horizontal scrolling try to design pages to a flexible or liquid design. However the maximum width of all pages should be 750 pixels and preferably 600 pixels. Most users will print pages straight from their browser, rather than using/downloading a printable version. A 600-pixel page will just fit on an A4 page. Pages designed at a larger width will not print correctly.

3.10 Plug-ins

Web authors should always assume that a visitor does not have any plug-ins installed. If publishing content that requires a plug-in, clear links to the relevant download should be provided for the visitor. For example a pdf document should always have a link to instructions for downloading and using Adobe Acrobat.

3.11 HTML Standards

It is recommended that authors should at least use HTML 4.01 or above as the standard HTML version. This should be declared in the “Document Type Definition” (DTD) at the head of HTML pages.

17

e.g. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

3.12 Maximum Page Size

Endeavour to design your pages to load within 15 seconds over a 28.8k modem. Remember that if a page doesn't load in 8 seconds you could lose 1/3 of your visitors. For a page to download in ten seconds the ‘page size’ (i.e. the sum of the file sizes for all the elements that make up a page including the HTML file and all embedded objects (e.g. image files) should be no greater than 80Kb. The user should be presented with predicted download times and/or file size details when downloading a document, video clip or other multimedia element, when the file size exceeds 80Kb.

3.13 Server Standards

Only use lower case when naming files and ensure that no filename contains spaces. If you wish to use a longer file name then use an underscore “_” to connect the words. No filename should include more than one period “.”.

No directory should exist without an index file in it. Allowing http directory browsing should be avoided on University servers due to security risks.

Old or out of date files should be deleted from the server or at least have their file extension altered. Just removing links to these files is unacceptable - search engines and the University search facility will still find these files.

All servers should have generic pages for (at least) 403 and 404 errors.

E.g. www.mmu.ac.uk/errors/403.html

www.mmu.ac.uk/errors/404.html 3.14 Testing

It is recommend that web authors should test their pages on as many different environments as possible. This includes different browsers and Windows/Macintosh computers: Netscape Navigator 4 to latest version Internet Explorer 4 to latest version Opera and Mozilla are also increasingly popular browsers Lynx can be used to test that pages work in a text only environment as can the popular screen reader – Jaws. Linux users could also test on Konqueror.

18

4.0 COMPLAINTS AND DISPUTE PROCEDURES

Below are two procedures that will be followed in the case of a complaint about pages within an MMU domain.

4.1.1 Complaints of an Non-Academic Nature

The following procedure is to be followed if a complaint is received regarding content or presentation on websites that are covered by these guidelines, excluding the academic content of published work in a field of academic endeavour in pursuance of an individual’s employment with the University. The latter type of complaint has a separate procedure below (4.1.1). All other complaints received by MMU staff should be referred to the Internet Manager.

This procedure should only be used for complaints of a serious nature and not for complaints such as broken links or missing images. Records of all complaints will be kept by the Internet Manager. This procedure will be invoked at the discretion of the Internet Manager if complaints cannot be resolved immediately.

a. Attempt to resolve the complaint by discussion between the author,

the Internet Manager, and if necessary the sponsor (please refer to 2.2.5 for sponsor definition) plus the relevant member of the Web Development Team.

b. The content is to be removed by the end of the working day if the Internet Manager or Web Development Team member decides that this is warranted by the nature of the material.

c. The complainant is to be informed that the content has been removed and an investigation underway.

d. The complaint will be investigated and a decision reached by the Internet Manager, the University Secretary, a member of the Web Steering Group, the author, the sponsor and, if different, the faculty Dean or divisional director (or their nominee).

e. The complainant is to be informed of the decision. 4.1.2 Complaints of an Academic Nature

The following procedure can be followed when a complaint is received regarding the academic content of published work in a field of academic endeavour in pursuance of an individual’s employment with the University.

a. The complaint should be directed for consideration to the relevant

academic. If the academic cannot be reached within a reasonable time, the complaint will be referred to their Head of Department or Dean to act in lieu of the academic. If the Head of Department or Dean cannot be reached within a reasonable time, the complaint will be referred to the University Secretary.

19

b. If the academic rejects the complaint, the relevant Dean, Line Manager, Head of Department and University Secretary must be informed.

20

c. If the University Secretary considers the material in question is unlawful, he or she will offer advice to the academic on the legal aspects of the issue.

d. If, following this advice, the academic decides that the material should remain, but the University Secretary still considers that the material is such that the University is likely to be prosecuted or sued successfully, then the Secretary will arrange for an independent legal opinion to be obtained urgently (usually within one working day). If that opinion so advises, the material shall be temporarily removed pending consideration by a panel consisting of the VC, Deputy VC and the Dean of the Faculty concerned. The academic involved and the University Secretary may both make representations to this panel.

e. The complainant is to be informed of the decision. 4.2 Disputes

Where the author of a web page feels unable to comply with the University requirements, the difficulty should be discussed with the relevant member of the web development team or the Internet Manager (see http://www.mmu.ac.uk/web/contacts.php for contact details.) It is expected that in almost all cases this will result in a mutually acceptable solution. However if a difficulty arises which cannot be resolved by this approach, the following dispute procedure can be followed at the discretion of the Internet Manager. It is envisaged that the procedure would be invoked only in exceptional circumstances. a. Attempts will be made by the Internet Manager, the author, and if

necessary the sponsor (and author’s Line Manager, if different) plus the relevant member of the Web Development Team to resolve the dispute by discussion.

b. The dispute will be investigated and a decision reached by the Internet Manager, University Secretary, a member of the Web Steering Group, the author, the sponsor and, if different, the faculty Dean or divisional director (or their nominee).

c. An appeal can be made to the Vice Chancellor for the final decision if the dispute is still not resolved.

5.0 Contacts, Feedback and Support

If you have any questions or wish to comment on these guidelines please get in touch with the Internet Manager or your relevant Web Development Team Member. Contact details for the Internet Manager and the Web Development Team are available at http://www.mmu.ac.uk/web/contacts.php