C ompliance With html standards




Скачать 14.67 Kb.
НазваниеC ompliance With html standards
Дата конвертации08.02.2016
Размер14.67 Kb.
ТипДокументы
источникhttp://www.ukoln.ac.uk/qa-focus/documents/briefings/briefing-01/briefing-01-A5.doc

Briefing-01 Briefing-01

C

ompliance With HTML Standards


A QA Focus Document

Why Bother?


Compliance with HTML standards is needed for a number of reasons:

  • HTML compliant resources are more likely to be accessible to a wide range of Web browsers including desktop browsers such as Internet Explorer, Firefox, Opera, Lynx and specialist browsers on PDAs, digital TVs, kiosks, etc.

  • HTML compliant resources are more easily processed and repurposed by other applications.

  • HTML compliant resources will be rendered more quickly by modern browsers.

  • HTML compliance is required by the AAA W3C WAI accessibility guidelines.

Which Standards?


The World Wide Web Consortium, W3C, recommend use of the XHTML 1.0 (or higher) standard. This has the advantage of being an XML application (allowing use of XML tools) and can be rendered by most browsers. However authoring tools which are widely deployed may not yet produce XHTML and there may be financial implications (licence costs, training, etc.) in upgrading. In such circumstances HTML 4.0 may be used.

Cascading style sheets (CSS) should be used in conjunction with XHTML/HTML to describe the appearance of Web resources.

Approaches To Creating HTML Resources


Web resources may be created in a number of ways. Often HTML authoring tools such as DreamWeaver, FrontPage, etc. are used, although experienced HTML authors may prefer to use a simple editing tool. Another approach is to make use of a Content Management System or server-side scripting facilities such as PHP or ASP. An alternative approach is to convert proprietary file formats (e.g. MS Word or PowerPoint). In addition sometimes proprietary formats are not converted but are stored in their native format.

C

ompliance With HTML Standards


A QA Focus Document

Why Bother?


Compliance with HTML standards is needed for a number of reasons:

  • HTML compliant resources are more likely to be accessible to a wide range of Web browsers including desktop browsers such as Internet Explorer, Firefox, Opera, Lynx and specialist browsers on PDAs, digital TVs, kiosks, etc.

  • HTML compliant resources are more easily processed and repurposed by other applications.

  • HTML compliant resources will be rendered more quickly by modern browsers.

  • HTML compliance is required by the AAA W3C WAI accessibility guidelines.

Which Standards?


The World Wide Web Consortium, W3C, recommend use of the XHTML 1.0 (or higher) standard. This has the advantage of being an XML application (allowing use of XML tools) and can be rendered by most browsers. However authoring tools which are widely deployed may not yet produce XHTML and there may be financial implications (licence costs, training, etc.) in upgrading. In such circumstances HTML 4.0 may be used.

Cascading style sheets (CSS) should be used in conjunction with XHTML/HTML to describe the appearance of Web resources.

Approaches To Creating HTML Resources


Web resources may be created in a number of ways. Often HTML authoring tools such as DreamWeaver, FrontPage, etc. are used, although experienced HTML authors may prefer to use a simple editing tool. Another approach is to make use of a Content Management System or server-side scripting facilities such as PHP or ASP. An alternative approach is to convert proprietary file formats (e.g. MS Word or PowerPoint). In addition sometimes proprietary formats are not converted but are stored in their native format.

Monitoring Compliance


A number of approaches may be taken to monitoring compliance with HTML standards. For example you can make use of validation features provided by modern HTML authoring tools, use desktop compliance tools or Web-based compliance tools.

The different tools can be used in various ways. Tools integrated with an HTML authoring tool are used by the page author. It is important that the author is trained to use such tools on a regular basis. It should be noted that it may be difficult to address systematic errors (e.g. all files missing the DOCTYPE declaration) with this approach.

A popular approach is to make use of SSIs (server-side includes) to retrieve common features (such as headers, footers, navigation bars, etc.). This can be useful for storing HTML elements (such as the DOCTYPE declaration) in a manageable form. However this may cause validation problems if the SSI is not processed.

Another approach is to make use of a Content Management System (CMS) or similar server-side technique, such as retrieving resources from a database. In this case it is essential that the template used by the CMS complies with standards.

It may be felt necessary to separate the compliance process from the page authoring. In such cases use of a dedicated HTML checker may be needed. Such tools are often used in batch, to validate multiple files. In many cases voluminous warnings and error messages may be provided. This information may provide indications of systematic errors which should be addressed in workflow processes.

A

n alternative approach is to use Web-based tools. This has the advantage that the service may be used in various ways: the service may be used directly by entering the URL of a resource to be validated or live access to the checking service may be provided by including a link from a validation icon as used at as shown (this approach could be combined with use of cookies or other techniques so that the icon is only displayed to an administrator).

Another approach is to configure your Web server so that users can access the validation service by appending an option to the URL. For further information on this technique see the QA Focus briefing document A URI Interface To Web Testing Tools at briefing-59/>. This technique can be implemented using a simple update to your Web server’s configuration file.

Monitoring Compliance


A number of approaches may be taken to monitoring compliance with HTML standards. For example you can make use of validation features provided by modern HTML authoring tools, use desktop compliance tools or Web-based compliance tools.

The different tools can be used in various ways. Tools integrated with an HTML authoring tool are used by the page author. It is important that the author is trained to use such tools on a regular basis. It should be noted that it may be difficult to address systematic errors (e.g. all files missing the DOCTYPE declaration) with this approach.

A popular approach is to make use of SSIs (server-side includes) to retrieve common features (such as headers, footers, navigation bars, etc.). This can be useful for storing HTML elements (such as the DOCTYPE declaration) in a manageable form. However this may cause validation problems if the SSI is not processed.

Another approach is to make use of a Content Management System (CMS) or similar server-side technique, such as retrieving resources from a database. In this case it is essential that the template used by the CMS complies with standards.

It may be felt necessary to separate the compliance process from the page authoring. In such cases use of a dedicated HTML checker may be needed. Such tools are often used in batch, to validate multiple files. In many cases voluminous warnings and error messages may be provided. This information may provide indications of systematic errors which should be addressed in workflow processes.

A

n alternative approach is to use Web-based tools. This has the advantage that the service may be used in various ways: the service may be used directly by entering the URL of a resource to be validated or live access to the checking service may be provided by including a link from a validation icon as used at as shown (this approach could be combined with use of cookies or other techniques so that the icon is only displayed to an administrator).

Another approach is to configure your Web server so that users can access the validation service by appending an option to the URL. For further information on this technique see the QA Focus briefing document A URI Interface To Web Testing Tools at briefing-59/>. This technique can be implemented using a simple update to your Web server’s configuration file.



Produced by QA Focus – see Dec 2004 Produced by QA Focus – see Dec 2004

Похожие:

C ompliance With html standards iconРеферат по информационным технологиям на тему «Интернет, html и html-редакторы»
Все документы для сервиса www пишутся на html (HyperText Markup Language) языке разметки гипертекста. Последний от обычного текста...
C ompliance With html standards iconChapter 4: html and html authoring Tools

C ompliance With html standards icon3 Баланс активтері мен олардың құралу көздерінің құрамы мен құрлымының динамикасын талдау 42
Стандартын – бехс және Қехс (International Accounting Standards, ias and International Financional Reporting Standards) жасайтын...
C ompliance With html standards iconHtml -ге кіріспе. Html тілінің атқаратын қызметі, командалары
Оқу құралын пайдалана отырып, сіздер Интернет үшін басылымдарды құру мүмкіндігін жүзеге асыратын негізгі командаларды меңгере отырып,...
C ompliance With html standards iconStandards of Quality and Effectiveness for

C ompliance With html standards iconРасписание занятий на вторник
Файлы html — это обычные текстовые файлы, имеющие расширение нтм. Будем использовать для создания и редактирования файлов html стандартную...
C ompliance With html standards iconTechnical standards for electromagnetic compatibility

C ompliance With html standards icon© 1996, 1997 Стефан Кох (Stefan Koch)
В свою очередь, язык JavaScript позволит Вам легко управлять объектами web-страницы, хотя для этого очень важно понимать иерархию...
C ompliance With html standards iconCommon Core State Standards for History/Social Studies, Sciences, and Technical Subjects

C ompliance With html standards iconDay Introduction To html

Разместите кнопку на своём сайте:
Документы


База данных защищена авторским правом ©kzdocs.docdat.com 2012
обратиться к администрации
Документы
Главная страница