1. A centre of expertise in digital information managementwww.ukoln.ac.uk QA For Web Sites: Developing Your Own QA Brian Kelly UKOLN University of Bath Bath Email B.Kelly@ukoln.ac.uk UKOLN is supported by: http://www.ukoln.ac.uk/qa-focus/presentations/ili-2004/ Talk 5

2. A centre of expertise in digital information managementwww.ukoln.ac.uk 2 Exercise: Developing Your Own QA In your groups choose 1 of 3 exercises: QA for accessibility QA for Web site metadata QA for software (selection of, use of and development of software) In addition if you have time give some thought to QA in 'softer' areas such as: QA for usability QA for Web site procurement Summarise relevant QA policies and procedures E

3. A centre of expertise in digital information managementwww.ukoln.ac.uk 3 Exercise 2A: QA For Accessibility Web Accessibility Policy A simple, understandable approach would be to say: The University Web site will comply with WAI WCAG AA guidelines But: Is this realistic? How do you measure compliance? Will it drive out other important aspects – e.g. usability, learning objectives, …?

4. A centre of expertise in digital information managementwww.ukoln.ac.uk 4 Holistic Accessibility UKOLN & TechDis are developing a holistic approach to accessibility Need to address: Usability IT accessibility Learning objectives Learner's needs (as opposed to universal solutions) Resource issues….

5. A centre of expertise in digital information managementwww.ukoln.ac.uk 5 Exercise 2B: QA For Web Site Metadata (1) QA Focus's policies: Purpose of metadata: To pull in appropriate style sheets Resource discovery – potential for fielded searches (author, document type, abstract, etc.) Architecture (management): Metadata defined in PHP fragments ($author="Brian Kelly") and pulled in and transformed to HTML/XHTML Architecture (deployment): Metadata will be deployed as tags embedded in XHTML. Note although this architecture allows for metadata transformation & reuse, it is poor for metadata management & control of content. However the QA must reflect the real system which has been implemented and not a desired alternative. Note although this architecture allows for metadata transformation & reuse, it is poor for metadata management & control of content. However the QA must reflect the real system which has been implemented and not a desired alternative.

6. A centre of expertise in digital information managementwww.ukoln.ac.uk 6 Exercise 2B: QA For Web Site Metadata (2) Policy - Purpose: Metadata will be used to (a) define structure of Web site (Documents, Presentations, …) for visual identity and allow potential for fielded searches and (b) to support resource discovery Policy – Content: Structural metadata will be chosen from set of keywords Resource discovery metadata will be based on a brief abstract and a small number of appropriate keywords. A similar style will be used across all resource

7. A centre of expertise in digital information managementwww.ukoln.ac.uk 7 Exercise 2B: QA For Web Site Metadata (3) Checking Procedures: Structural metadata will be checking visually to ensure that the correct style sheet is used Resource discovery metadata will be reused in the printed QA Focus handbook. Visual checking of the printed resources will be used to ensure the accuracy and appropriateness of the metadata HTML validation procedures will ensure the tags comply with HTML Learning Experiences: Metadata management to avoid data duplication Tools to spot incorrect structural metadata Searching for common content errors (e.g. null fields, template data, …

8. A centre of expertise in digital information managementwww.ukoln.ac.uk 8 Exercise 2C: QA For Software (1) Choosing Software: Open sources vs licensed issues Possible dangers of sustainability if non- mainstream See Top Tips For Choosing Open Source Software briefing document Creation Tools: Need to ensure that output (e.g. metadata creation tools) complies with appropriate standards Need for systematic checking of output

9. A centre of expertise in digital information managementwww.ukoln.ac.uk 9 Exercise 2C: QA For Software (2) Workflow: Need to ensure that workflow does not corrupt data Need to validate output against range of inputs (e.g. MS Windows characters (©, —, £) input to news feed authoring systems Web Forms: Need to ensure that Web forms work – esp. if used for critical systems such as online bookings Need for systematic checking – e.g. names with unusual characters; non-standards browsers; JavaScript disabled; …

10. A centre of expertise in digital information managementwww.ukoln.ac.uk 10 Exercise 2D: QA For Usability Usability Some objective aspects, but mostly about people See Jakob Neilson’s Alertbox column QA: Provided structured tasks for (small) group of users accessing typical resources Watch, record and observe user behaviour – don’t help users! Complement with other tests such as browsing with:  JavaScript switched off  CSS switched off  Other browsers  Using PDA  …

11. A centre of expertise in digital information managementwww.ukoln.ac.uk 11 Exercise 2E: QA For Procurement (1) Learn From Experiences Danger that Web agencies may be design or application-led and not understand broader issues In ITT Clarify standards to be used (e.g. see Selection of Standards document) Clarify architecture to be used Specify acceptance tests such as: HTML, CSS validation of key resources Pages must be usable with JavaScript switched off, … Make use of QA examples used today

12. A centre of expertise in digital information managementwww.ukoln.ac.uk 12 Accompanying Resources Use of Automated Tools Use of Automated Tools For Testing Web Site Accessibility, Briefing Document No. 02 Evaluating A Web Site's Accessibility How To Evaluate A Web Site's Accessibility Level, Briefing Document No. 12 Accessibility Testing In Web Browsers Accessibility Testing In Web Browsers, Briefing Document No. 57 Introduction To Metadata An Introduction To Metadata, Briefing Document No. 41 Metadata Deployment Metadata Deployment, Briefing Document No. 42 QA For Metadata Quality Assurance For Metadata, Briefing Document No. 43 Top Tips For Selecting Open Source Software Top Tips For Selecting Open Source Software, Briefing Document No. 60