Skip to content
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.

section 2.1 edits #83

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

section 2.1 edits #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
16 changes: 3 additions & 13 deletions WAET.html
View file
Open in desktop
Expand Up @@ -460,19 +460,9 @@ <h2 id="features">2 Features of an accessibility evaluation tool</h2>
tools can use this document to learn about relevant features to look
for.</p>

<h3 id="subjects">2.1 Retrieving and rendering web content</h3>

<p>This category includes features that help to retrieve and render different
types of web content. There are tools that may retrieve the content to be
analyzed from the file system or from a database. However, the majority of
them do it via a network connection through the <abbr>HTTP(S)</abbr>
protocol. This section focuses mostly on this latter scenario. </p>

<p>Due to the characteristics of the <abbr>HTTP(S)</abbr> protocol, the
rendering of a web resource implies the manipulation and storage of many
other components associated with it, like request and response headers,
session information, cookies, authentication information, etc. These
associated components are also considered in the following. </p>
<h3 id="resources">2.1 Resources to be Evaluated</h3>
<p>This category includes features that help evaluation tools to retrieve and render different types of web content. While there are evaluation tools that retrieve the content to be analyzed directly from file systems or from databases, the majority of evaluation tools retrieve the content through a network connection using the <abbr>HTTP(S)</abbr> protocol. This section focuses primarily on this latter situation.</p>
<p>Besides the primary web content resources, such as the <abbr>HTML</abbr> and <abbr>CSS</abbr> code, other aspects of the <abbr>HTTP(S)</abbr> protocol are relevant to retrieving and rendering web content. For example, the <abbr>HTTP</abbr> request and response headers may include important information about the content that was retrieved and provided to the user. Also session and authentication information, cookies, and other aspects might impact the particular content retrieved and rendered, especially in web applications. These characteristics of the <abbr>HTTP(S)</abbr> protocol are considered in this document.</p>

<h4 id="resformats">2.1.1 Resource formats</h4>

Expand Down