混合过关错一场有奖吗 混合过关3串1中两场 qq彩票混合过关 竞彩混合过关奖金计算 竞猜混合过关 竞猜足球混合过关 竞彩网混合过关计算器 竞彩混合过关怎么玩 昨晚竞彩足球混合过关 竞彩篮球混合过关玩法 足球混合过关是什么意思 竞彩混合过关咋打票 竞彩足球单场混合过关 中国体育彩票竞彩篮球混合过关 竞彩网混合过关

W3C

Accessibility Conformance Testing (ACT) Rules Format 1.0

W3C Proposed Recommendation,

This version:
http://www.fyrkh.live/TR/2019/PR-act-rules-format-1.0-20190730/
Latest published version:
http://www.fyrkh.live/TR/act-rules-format-1.0/
Highest version of ACT Rules Format:
http://www.fyrkh.live/TR/act-rules-format/
Latest editor's draft:
https://w3c.github.io/wcag-act/act-rules-format.html
Implementation report:
https://w3c.github.io/wcag-act/act-implementations.html
Previous version:
http://www.fyrkh.live/TR/2019/CR-act-rules-format-1.0-20190416/
Editors:
Wilco Fiers (Deque Systems)
Maureen Kraft (IBM Corp.)
Mary Jo Mueller (IBM Corp.)
Shadi Abou-Zahra (W3C)

Abstract

The Accessibility Conformance Testing (ACT) Rules Format 1.0 defines a format for writing accessibility test rules. These test rules can be used for developing automated testing tools and manual testing methodologies. It provides a common format that allows any party involved in accessibility testing to document and share their testing procedures in a robust and understandable manner. This enables transparency and harmonization of testing methods, including methods implemented by accessibility test tools.

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.fyrkh.live/TR/.

This document is a Proposed Recommendation of Accessibility Conformance Testing Rules Format 1.0 (ACT Rules Format 1.0), published by the Accessibility Guidelines Working Group. ACT Rules Format 1.0 was published as a Candidate Recommendation on 16 April 2019. Since then the Working Group has collected implementations in the form of conforming rules. No changes were made to normative requirements clauses. A history of changes to ACT Rules Format 1.0 is available in the appendix.

The primary purpose of the Proposed Recommendation is to collect feedback from the Advisory Committee. W3C Advisory Committee Members are invited to send formal review comments to the W3C Team until 24 September 2019. Comments should be made using the Call for Review WBS form. Advisory Committee Representatives should consult their WBS questionnaires.

The W3C Membership and other interested parties are invited to review the document and send comments. Note that substantive technical comments were expected during the Candidate Recommendation review period that ended 28 May 2019. To comment, aside from Advisory Committee comments, file an issue in the W3C ACT TF GitHub repository. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to [email protected] (comment archive). Comments are requested by 24 September 2019. In-progress updates to the document may be viewed in the publicly visible editors' draft.

Please see the Working Group's implementation report.

Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 March 2019 W3C Process Document.

1. Introduction

There are currently many test procedures and tools available which aid their users in testing web content for conformance to accessibility standards such as the Web Content Accessibility Guidelines [WCAG]. As the Web develops in both size and complexity, these procedures and tools are essential for managing the accessibility of resources available on the Web.

This format is intended to enable a consistent interpretation of how to test conformance to WCAG and other accessibility requirements documents and promote consistent results in accessibility testing. The rules format is designed to describe both manual accessibility tests, as well as automated tests as performed by accessibility testing tools.

Documenting how to test accessibility requirements will result in accessibility tests that are transparent, with test results that are reproducible. The Accessibility Conformance Testing (ACT) Rules Format defines the requirements for these test descriptions, known as Accessibility Conformance Testing Rules (ACT Rules).

An ACT Rule is a plain language description of how to test a specific type of content for a specific aspect of an accessibility requirement. An ACT Rule describes what kind of content it applies to and which conditions are true about the applicable elements for them to meet all expectations of the rule. In the context of WCAG, ACT Rules test for failures in satisfying Success Criteria. Such failures are often described in common failures documented for WCAG. ACT Rules are written for the testing process and are usually more specific than common failures.

The ACT Rules Format defines the requirements and rule structure for the types of information each rule needs to include to be called an ACT Rule. The structure of the ACT rule is defined in the ACT Rule Structure section. Each ACT Rule also contains a plain language description of the type of content under test, the test to perform, and the expected result. Where the test result affects conformance, the rule documents the particular requirement being tested. The resulting outcomes from the test can be used to help determine conformance or non-conformance to the requirement. Test cases are also written as part of the ACT rule to provide a way to verify that implementations of the rule can successfully determine the expected outcomes.

2. Scope

The ACT Rules Format defined in this specification is designed for rules that can be used in testing content created using web technologies, such as Hypertext Markup Language [HTML], Cascading Style Sheets [css-2018], Accessible Rich Internet Applications [WAI-ARIA], Scalable Vector Graphics [SVG2], EPUB 3, and more. The ACT Rules Format is designed to be technology agnostic, meaning that it can conceivably be used to describe test rules for other technologies.

The ACT Rules Format can be used to describe ACT Rules dedicated to testing the accessibility requirements defined in the Web Content Accessibility Guidelines [WCAG], which are specifically designed for web content. Other accessibility requirements applicable to web technologies can also be testable with ACT Rules. For example, ACT Rules could be developed to test the conformance of web-based user agents to the User Agent Accessibility Guidelines [UAAG20]. The ACT Rules Format might not always be suitable to describe tests for other types of accessibility requirements.

3. ACT Rule Types

In accessibility, there are often different technical solutions to make the same type of content accessible. For example, there are multiple methods for giving an img element in HTML an accessible name. Multiple solutions could be tested in a single rule; however, such a rule tends to be quite complex, making it difficult to understand and maintain. The ACT Rules Format solves this by providing two types of rules:

Composite rules cannot contain other composite rules. Any time a nested composite rule would be needed, all of the relevant atomic rules can be combined directly into the new composite rule.

Not all atomic rules have to be part of a composite rule. Composite rules are used when the outcomes of multiple atomic rules need to be combined to determine if a test subject does not satisfy an accessibility requirement.

The separation between atomic rules and composite rules creates a division of responsibilities. Atomic rules test if web content is correctly implemented in a particular solution. Composite rules can test if a combination of outcomes from other atomic rules satisfy the accessibility requirement, in part or as a whole.

4. ACT Rule Structure

An ACT Rule must consist of at least the following items:

An ACT Rule MAY also contain:

The ACT Rules format does not prescribe what format ACT Rules can be written in (e.g. HTML, DOCX, PDF, etc.). However, ACT Rules must be written in a document that conforms to the Web Content Accessibility Guidelines [WCAG] or a comparable accessibility standard. This ensures that ACT Rules are accessible to people with disabilities. ACT Rule test cases are allowed to contain inaccessible content. If any test case contains accessibility issues listed in WCAG 2.1 Section 5.2.5 Non-Interference, users must be warned of this in advance. In addition to supporting people with disabilities, using an accessible format also makes internationalization of ACT Rules easier.

4.1. Rule Identifier

An ACT Rule must have an identifier. This identifier must be unique when the rule is part of a ruleset. The identifier can be any text, such as plain text, URL, or a database identifier.

In addition to the identifier, each new release of an ACT Rule must be versioned with either a date or a number. A reference to the previous version of that rule must be available. The identifier must not be changed when the rule is updated. For substantial changes, a new rule should be created with a new identifier, and the old rule should be deprecated.

4.2. Rule Description

An ACT Rule must have a description that is in plain language which provides a brief explanation of what the rule does.

4.3. Rule Type

An ACT Rule must have a rule type which is one of the following:

Refer to the Rule Type section for detailed definitions of the rule types.

4.4. Accessibility Requirements Mapping

When an ACT Rule is designed to test conformance to one or more Accessibility requirements documents, the rule must list all accessibility requirements from those documents that are not satisfied when one or more of the outcomes of the rule is failed. For example, when designing a rule for WCAG that tests if image buttons have alternative text, the rule maps to success criteria 1.1.1 Non-text content, and 4.1.2 Name, Role, Value. That ACT Rule will list both success criteria in its accessibility requirements mapping.

Each accessibility requirement in the mapping must include the following:

  1. either the name, title, identifier or summary of the accessibility requirement, and

  2. the name of the accessibility requirements document, and

  3. a link or reference to the accessibility requirements document if one exists, and

  4. the conformance level associated with the accessibility requirement, if one exists.

4.4.1. Outcome Mapping

For each accessibility requirement in the mapping, an ACT Rule must indicate what the outcomes of the rule mean for satisfying that accessibility requirement for that test subject. When one or more of the outcomes for a test target is failed, the accessibility requirements are not satisfied for the test subject. When all of the outcomes are passed or inapplicable, the accessibility requirements could be satisfied, or further testing is needed. Rules that can be used to determine if an accessibility requirement is satisfied are called satisfying tests.

Note: In the Web Content Accessibility Guidelines [WCAG], success criteria do not evaluate to passed, failed or inapplicable. Rather they can be satisfied (or not). (See the WCAG 2.1 definition: satisfies a success criterion.) If a success criterion is not satisfied, a web page can only conform if there is a conforming alternative version, as described in WCAG 2.1 Conformance Requirement 1.

4.4.2. Mapping Outside WCAG

ACT Rules can be used to test accessibility requirements that are not part of a W3C accessibility standard, such as accessibility requirements in Hypertext Markup Language [HTML], or tests in a methodology like RGAA 3 2016. An ACT Rule must indicate whether or not the accessibility requirement it maps to is required for conformance in its accessibility requirements document. Examples of accessibility requirements that are not required for conformance are WCAG sufficient techniques, or a company style guide that includes both requirements and optional "best practices". The distinction between what is required and what is optional has to be clear.

4.4.3. Rules Without Accessibility Requirements

If the rule does not map to any accessibility requirement, the accessibility requirement mapping will only contain the explainer that it is not required for conformance to the accessibility requirements document. This is common with atomic rules used in composite rules.

If the failed outcome cannot be mapped to an accessibility requirement, there must not be an accessibility requirement in the accessibility requirements mapping. The optional Background section could be used to list accessibility requirements documents when they are thematically related, but for which the rule is not a failure test.

4.4.4. External Accessibility Requirements Mapping

This section is non-normative.

While rules are often designed for one, or possibly a small collection of accessibility requirements documents, it is likely that other accessibility requirements documents also map to those ACT Rules. For example, rules can be written for the Web Content Accessibility Guidelines [WCAG], but many of those could also map to a company’s internal accessibility policy. In such a scenario, an external accessibility requirements mapping could be created. An external accessibility requirements mapping amends the accessibility requirements mapping of an ACT rule by adding mapping to a different accessibility requirements document. An external accessibility requirements mapping avoids duplication of a rule for the sole purpose of changing the mapping.

4.5. Rule Input

To evaluate content using an ACT Rule, the rule requires some information from the test subject. This is the input for the rule. What input is required is made explicit, to help testers understand what capabilities are required to use a rule. Atomic rules and composite rules have different input.

4.5.1. Input Aspects (Atomic rules only)

An input aspect is a distinct part of the test subject. Rendering a particular piece of content to an end user commonly involves different technologies, some or all of which are required as input for an atomic rule. For example, some rules need to operate directly on the Hypertext Transfer Protocol [http11] messages exchanged between a server and a client, while others need to operate on the Document Object Model [DOM] tree exposed by a web browser.

Atomic rules must list the aspects used as input for the applicability and expectations of the atomic rule. Rules can operate on several aspects simultaneously, such as both the HTTP messages and the DOM tree.

Some input aspects are well defined in a formal specification, such as HTTP messages, the DOM tree, and CSS styling [css-2018]. For these, a reference to the corresponding section in the Common Input Aspects note is sufficient as a description of the aspect. For input aspects that are not well defined, an ACT Rule must include either a detailed description of the aspect in question, or a reference to a well defined description.

The method through which an input aspect is served is not relevant. For example a DOM tree can be served through HTTP as HTML, it can be bundled as several pages in an EPUB publication, or it can be inferred from a JSX source file. All rules that have only DOM tree as an input aspect can be applied to those technologies.

4.5.2. Input Rules (Composite rules only)

A composite rule uses outcomes from atomic rules and applies logic to them so that a single outcome can be determined for each test target. The identifier and descriptive title of all the atomic rules used in the expectations must be listed in the composite rule. The input rules describe the input for composite rules, similar to how input aspects describe the input for atomic rules.

4.6. Applicability

The applicability describes what parts of the test subject are tested.

4.6.1. Applicability for Atomic Rules

The applicability section is a required part of an atomic rule. It must contain a precise description of the parts of the test subject to which the rule applies. For example, specific nodes in the DOM [DOM] tree, or tags that are incorrectly closed in an HTML [HTML] document. These are known as the test targets. The applicability must only use information made available through the listed input aspects in the rule. No other information can be used in the applicability. Applicability must be described objectively, unambiguously and in plain language.

An objective description is one that can be resolved without uncertainty, in a given technology. Examples of objective properties in HTML are tag names, their computed role, the distance between two elements, etc. Subjective properties on the other hand, are concepts like decorative, navigation mechanism and pre-recorded.

Even concepts like headings and images can be misunderstood. These terms could refer to the tag name, the semantic role, or the element’s purpose on the web page because they are ambiguous. The latter of which is almost impossible to define objectively. When used in applicability, potentially ambiguous concepts must be defined objectively. Definitions can be put in the rule glossary, or they can be defined in the section where they are used.

4.6.2. Applicability for Composite Rules

The applicability of a composite rule is defined as the union of all applicability definitions from the rules listed in the input rules. Rule authors may omit a description of the applicability for composite rules. This can be useful if it is difficult to express the combined applicability in plain language. If the composite rule includes applicability, it must be the union of all the applicability in the input rules.

Note that input rules in a composite rule may have different applicability. Because of this, not every test target applicable within the composite rule is tested by every input rule.

4.7. Expectations

An ACT Rule must contain one or more expectations. The expectations describe what the requirements are for the test targets derived from the applicability. An expectation is an assertion about a test target. When a test target meets all expectations, the test target passed the rule. If the test target does not meet all expectations, the test target failed the rule. If there are no test targets, the outcome for the rule is inapplicable.

Each expectation must be distinct, unambiguous, and be written in plain language.

4.7.1. Expectations for Atomic Rules

All expectations of an atomic rule must describe the logic that is used to determine a single passed or failed outcome for a test target. The expectation must only use information available in the input aspects, from the applicability, and other expectations of the same rule. No other information can be used in the expectation. So for instance, an expectation could be "Expectation 1 is true and ...", but it can’t be "Rule XYZ passed and ...". This ensures that atomic rules are encapsulated.

Note: Sometimes there is the need for rules with more complex aggregation, for example that X% of all images on a web page are expected to have text alternatives. In this case, the page itself needs to become the test target. The expectation would then be "The test target (the page) has a text alternative for X% of all img elements". The logic for calculating the expectations in such rules is left to the implementations, to avoid over-complexity of this rules format.

4.7.2. Expectations for Composite Rules

All expectations of a composite rule must describe the logic that is used to determine a single passed or failed outcome for a test target, based on the outcomes of rules in its input rules. A composite rule expectation must not use information from input aspects. The outcome for a composite rule is inapplicable when all input rules are inapplicable.

4.8. Assumptions

An ACT Rule must list any known assumptions, limitations or any exceptions for the evaluation, the test environment, technologies being used or the subject being tested. For example, a rule that would partially test WCAG 2.1 success criterion 1.4.3 Contrast (Minimum) based on the inspection of CSS properties could state that it is only applicable to HTML text content styleable with CSS, and that the rule does not support images of text.

Sometimes there are multiple plausible ways that an accessibility requirement can be interpreted. For instance, it is not immediately obvious if emoji characters are "text" or "non-text content" in the Web Content Accessibility Guidelines [WCAG]. Whatever the interpretation is, this must be documented in the rule.

While the assumptions must be included in the ACT Rule, it may be empty when there are no known assumptions, limitations or exceptions.

4.9. Accessibility Support

Content can be designed to rely on the support for particular accessibility features by different assistive technologies and user agents. For example, content using a particular WAI-ARIA 1.1 feature relies on that feature to be supported by assistive technologies and user agents. This content would not work for assistive technologies and user agents that do not support WAI-ARIA. See the WCAG definition for accessibility supported use of a web technology.

An ACT Rule must include known limitations on accessibility support.

While an accessibility support section must be included in the ACT Rule, it may be empty when there are no known accessibility support issues.

Note: The Website Accessibility Conformance Evaluation Methodology (WCAG-EM) provides guidance on defining an accessibility support baseline for test scenarios, which can help users of ACT Rules to select the appropriate rules for their own circumstance.

4.10. Test Cases

Test cases are (snippets of) content that can be used to validate the implementation of ACT Rules. Each rule must have one or more test cases for passed, failed, and inapplicable outcomes. A test case consists of two pieces of data, a snippet of each input aspect for a rule, and the expected outcome for that rule. Test cases serve two functions, firstly as example scenarios for readers to understand when the outcome of a rule is passed, failed, or inapplicable. It also serves developers and users of accessibility testing tools and methodologies to validate that a rule is correctly implemented.

4.11. Change Log

It is important to keep track of changes to the ACT Rules so that users of the rules can understand if changes in test results are due to changes in the rules used when performing the tests, or from changes in the content itself. All changes to an ACT Rule that can change the outcomes of an evaluation must be recorded in a change log. The change log can either be part of the rule document itself or be referenced from it.

4.12. Glossary

ACT Rules must have a glossary section. The glossary must contain the outcome definition, as well as any definitions used in applicability and expectations sections in the rule. Since changes to the definition change the rule, those definitions cannot be maintained independently of the rule. If a shared glossary is used for rules, any definition changes must be included in the change log of all rules that use that definition.

4.13. Issues List (optional)

An ACT Rule may include a list or a reference to a list of any known issues. The issues list would be used to record cases where an outcome of an ACT Rule was failed where it ought to have been passed or inapplicable, or vice versa. There are several reasons why this might occur. See rule accuracy for more information.

The issues list serves two purposes. For users of ACT Rules, the issues list gives insight into why an inaccurate result occurred, as well as provide confidence in the result of that rule. For the designer of the rule, the issues list is also useful to plan future updates to the rule. In a new version of the rule, resolved issues would be moved to the change log.

4.14. Background (optional)

An ACT Rule may contain information about the background for the development of the rule, or references to relevant reading. The background information is optional, but whenever it is included in the rule, the relationship to the relevant reading can be specified. Examples of relevant background references for a rule for a Web Content Accessibility Guidelines [WCAG] success criterion could be WCAG 2.1 Understanding documents, WCAG 2.1 Techniques, or WAI-ARIA 1.1, CSS [css-2018], or HTML [HTML] specifications.

4.15. Acknowledgements (optional)

An ACT Rule may contain acknowledgements. This can include, but is not limited to:

5. Rule Accuracy

This section is non-normative.

While test cases can be used to determine if an ACT Rule was correctly implemented, they do not guarantee that implementations will never produce incorrect results. When writing ACT Rules, it is almost inevitable that edge cases will be overlooked. Technologies are always evolving, and content authors are constantly coming up with new and unexpected ways to use them. Some examples of causes for inaccuracy are:

There are two types of inaccuracies that can produce incorrect results. Inaccuracies in the implementation can be addressed with test cases, but inaccuracies in the ACT Rule itself cannot. After all, rule inaccuracies come from the rule author being unaware of a particular edge case.

When a test result incorrectly indicates non-conformance to an accessibility requirement, this is known as a false positive. Opposite, when a rule incorrectly indicates conformance, this is a false negative. A percentage of false positives and false negatives can be calculated by comparing it to results from an accessibility audit:

The ever present possibility of false positives and false negatives with ACT Rules means they will likely require ongoing maintenance. Designing a process for maintaining ACT Rules is outside the scope of the ACT Rules Format, which is limited to the rules themselves. Nevertheless, it is suggested that rule authors work out a process for maintaining their rules.

6. Harmonization

This section is non-normative.

While the ACT Rules Format is designed to stimulate harmonization, there are no direct requirement in the ACT Rules Format that prevent a rule author from writing rules inconsistent with already established ACT Rules. Neither are there requirements for ACT Rules to have a certain number of implementations, or to have a certain level of accuracy. This allows quality requirements to be different for different rulesets, and allows them to develop over time.

Harmonization occurs when a group of rule implementors collectively accept the validity of an ACT Rule. For example, a community group of accessibility testing tool vendors could declare they have harmonized on a particular set of ACT Rules. Such a group can set acceptance criteria for rules, and have quality requirements that go beyond the ACT Rules Format.

An example of such a process is the WCAG ACT Review Process.

7. Definitions

Accessibility requirement

A requirement is a condition that has to be satisfied in order to conform to a standard, or to comply with a contract, policy or regulation. An accessibility requirement is a requirement aimed at improving access for people with disabilities to an ICT product.

A common example of accessibility requirements are the WCAG success criteria. There are other standards, including W3C standards, that have recommendations for accessibility, such as WAI-ARIA and HTML. Accessibility requirements are also often found in company policies, regional standards or in legislation.

Accessibility requirements document

A document, such as a standard, contract, policy or regulation, that includes accessibility requirements. For example, WCAG 2.1, WAI-ARIA 1.1, HTML 5.2, EPUB Accessibility 1.0, BBC HTML Accessibility Standards v2.0

Outcome

A conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:

  • Inapplicable: No part of the test subject matches the applicability
  • Passed: A test target meets all expectations
  • Failed: A test target does not meet all expectations

Note: A rule has one passed or failed outcome for every test target. When there are no test targets the rule has one inapplicable outcome. This means that each test subject will have one or more outcomes.

Note: Implementers using the [EARL10-Schema] can express the outcome with the outcome property. In addition to passed, failed and inapplicable, EARL 1.0 also defined an incomplete outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such "interim" results can be expressed with the incomplete outcome.

Test Subject

A resource or collection of resources that can be evaluated by an ACT Rule.

Note: Implementers using the [EARL10-Schema] can express the test subject with the subject property

Test Target

A distinct part of the test subject, as defined by the applicability.

Note: Implementers using the [EARL10-Schema] can express the test target with the pointer property

Appendix 1: Expressing ACT Rule results with JSON-LD and EARL

This section is non-normative.

This section provides examples of expressing results from carrying out ACT Rules using EARL and JSON-LD (See Evaluation and Report Language and A JSON-based Serialization for Linked Data (JSON-LD)). More examples and background is proivided on the JSON-LD serialization of EARL GitHub repository.

Examples in this section include:

Example 1: Minimal outcome for one Assertion

{
	"@context": "context.json",
	"@type": "Assertion",
	"assertedBy": "https://example.org/MyTool",
	"subject": "https://example.org/page1.html",
	"test": "ACT-CG:rules/23a2a8",
	"result": {
		"outcome": "earl:failed",
		"pointer": "html > body > h1:first-child"
	}
}

Example 2: Results for more than one Assertion

{
	"@context": "context.json",
	"@graph": [{
		"@type": "Assertion",
		"assertedBy": "https://example.org/MyTool",
		"subject": "https://example.org/page1.html",
		"test": "ACT-CG:rules/23a2a8",
		"result": {
			"outcome": "earl:failed",
			"pointer": "html > body > h1:first-child"
		}
	}, {
		"@type": "Assertion",
		"assertedBy": "https://example.org/AnotherTool",
		"subject": "https://example.org/page1.html",
		"test": "ACT-CG:rules/23a2a8",
		"result": {
			"outcome": "earl:passed",
			"pointer": "html > body > h1:nth-child(2)"
		}
	}]
}

Example 3: Aggregating based on Requirement (eg. WCAG Success Criteria)

{
	"@context": "context.json",
	"@type": "Assertion",
	"assertedBy": "https://example.org/MyTool",
	"subject": "https://example.org/page1.html",
	"test": {
		"@type": "earl:TestRequirement",
		"@id": "WCAG21:non-text-content"
	},
	"result": {
		"outcome": "earl:failed",
		"source": [{
			"test": "ACT-CG:rules/23a2a8",
			"result": {
				"outcome": "earl:failed",
				"pointer": "html > body > h1:first-child"
			}
		}, {
			"test": "ACT-RULES-CG:rules/23a2a8",
			"result" : {
				"outcome": "earl:passed",
				"pointer": "html > body > h1:nth-child(2)"
			}
		}]
	}
}

Example 4: Aggregating based on 'Test Subject' (eg. for a website)

{
	"@context": "context.json",
	"@type": "Assertion",
	"assertedBy": {
		"@type": "Organization",
		"@id": "_:myOrg",
		"title": "My Organization",
		"description" : "Accessibility testing service",
		"homepage" : "http://example.org/myOrg/"
	},
	"subject": {
		"@type": ["WebSite", "TestSubject"],
		"@id": "https://example.org/"
	},
	"test": {
		"@type": "earl:TestRequirement",
		"@id": "http://www.fyrkh.live/WAI/WCAG2A-Conformance"
	},
	"result": {
		"outcome": "earl:failed",
		"source": [{
			"test": {
				"@type": "earl:TestRequirement",
				"@id": "WCAG21:non-text-content"
			},
			"result": {
				"outcome": "earl:failed",
				"source": []
			}
		}, {
			"test": {
				"@type": "earl:TestRequirement",
				"@id": "WCAG21:audio-only-and-video-only-prerecorded"
			},
			"result": {
				"outcome": "earl:passed",
				"source": []
			}
		}, {
			"test": {
				"@type": "earl:TestRequirement",
				"@id": "WCAG21:captions-prerecorded"
			},
			"result" : {
				"outcome": "earl:passed",
				"source": []
			}
		},]
	}
}

Example 5: Assumed Context for this section

{
	"@vocab": "http://www.fyrkh.live/ns/earl#",

	"cnt": "http://www.fyrkh.live/2011/content#",
	"dct": "http://purl.org/dc/terms/",
	"earl": "http://www.fyrkh.live/ns/earl#",
	"foaf": "http://xmlns.com/foaf/0.1/",
	"htp": "http://www.fyrkh.live/2011/http#",
	"ptr": "http://www.fyrkh.live/2009/pointers#",
	"schema": "http://schema.org/",
	"xsd": "http://www.fyrkh.live/2001/XMLSchema#",

	"WCAG20": "http://www.fyrkh.live/TR/WCAG20#",
	"WCAG21": "http://www.fyrkh.live/TR/WCAG21#",
	"ACT-RULES-CG": "https://act-rules.github.io/",

	"WebSite": "schema:WebSite",
	"WebPage": "schema:WebPage",

	"title": "dct:title",
	"description": "dct:description",
	"date": "dct:date",
	"hasVersion": "dct:hasVesion", 
	"isPartOf": "dct:isPartOf", 
	"hasPart": "dct:hasPart",
	"source": "dct:source",

	"Agent": "foaf:Agent",
	"Person": "foaf:Person",
	"Organization": "foaf:Organization",
	"Group": "foaf:Group",
	"Document": "foaf:Document",
	"name": "foaf:name",
	"firstName": "foaf:firstName",
	"surname": "foaf:surname",
	"mbox": "foaf:mbox",
	"mbox_sha1sum": "foaf:mbox_sha1sum",
	"member": "foaf:member",
	"homepage": "foaf:homepage",

	"assertedBy": { "@type": "@id" },
	"subject": { "@type": "@id" },
	"test": { "@type": "@id" },
	"mode": { "@type": "@id" },
	"outcome": { "@type": "@id" },
	"pointer": {
		"@id": "earl:pointer",
		"@type": "ptr:CSSSelectorPointer"
	}
}

Appendix 2: Acknowledgments

This section is non-normative.

Participants of the AG WG active in the development of this document

Shadi Abou-Zahra, Trevor Bostic, Romain Deltour, Kathy Eng, Wilco Fiers, Alistair Garrison, Kasper Isager, Maureen Kraft, Mary Jo Mueller, Jey Nandakumar, Charu Pandhi, Stein Erik Skotkjerra, Anne Thyme N?rregaard, Kathleen Wahlbin

Enabling funders

This publication has been developed with support from the WAI-Tools Project, co-funded by the European Commission (EC) under the Horizon 2020 Program (Grant Agreement 780057). The content of this publication does not necessarily reflect the views or policies of the European Commission (EC) or any of the European Union (EU) Member States.

Appendix 3: Change History

This section is non-normative.

No substantial changes have been made since the previous Candidate Recommendation draft of 16 April 2019. The following editorial changes have been made since the previous draft:

All changes from the previous published version can be viewed using the April 2019 to July 2019 diff link

Conformance

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

References

Normative References

[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119

Informative References

[ACCNAME-1.1]
Joanmarie Diggs; Bryan Garaventa; Michael Cooper. Accessible Name and Description Computation 1.1. 18 December 2018. REC. URL: http://www.fyrkh.live/TR/accname-1.1/
[CSS-2018]
Tab Atkins Jr.; Elika Etemad; Florian Rivoal. CSS Snapshot 2018. 22 January 2019. NOTE. URL: http://www.fyrkh.live/TR/css-2018/
[DOM]
Anne van Kesteren. DOM Standard. Living Standard. URL: https://dom.spec.whatwg.org/
[EARL10-Schema]
Shadi Abou-Zahra. Evaluation and Report Language (EARL) 1.0 Schema. 2 February 2017. NOTE. URL: http://www.fyrkh.live/TR/EARL10-Schema/
[HTML]
Anne van Kesteren; et al. HTML Standard. Living Standard. URL: https://html.spec.whatwg.org/multipage/
[HTTP11]
R. Fielding, Ed.; J. Reschke, Ed.. Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. June 2014. Proposed Standard. URL: https://tools.ietf.org/html/rfc7230
[SVG2]
Amelia Bellamy-Royds; et al. Scalable Vector Graphics (SVG) 2. 4 October 2018. CR. URL: http://www.fyrkh.live/TR/SVG2/
[UAAG20]
James Allan; et al. User Agent Accessibility Guidelines (UAAG) 2.0. 15 December 2015. NOTE. URL: http://www.fyrkh.live/TR/UAAG20/
[WAI-ARIA]
Joanmarie Doggs; et al. Accessible Rich Internet Applications (WAI-ARIA) 1.1. 14 December 2018. REC. URL: http://www.fyrkh.live/TR/wai-aria/
[WCAG]
Andrew Kirckpatrick; et al. Web Content Accessibility Guidelines 2.1. 5 June 2018. REC. URL: http://www.fyrkh.live/TR/WCAG/
混合过关投注技巧
混合过关错一场有奖吗 混合过关3串1中两场 qq彩票混合过关 竞彩混合过关奖金计算 竞猜混合过关 竞猜足球混合过关 竞彩网混合过关计算器 竞彩混合过关怎么玩 昨晚竞彩足球混合过关 竞彩篮球混合过关玩法 足球混合过关是什么意思 竞彩混合过关咋打票 竞彩足球单场混合过关 中国体育彩票竞彩篮球混合过关 竞彩网混合过关
国际原油能赚钱吗 玩极速赛车技巧稳赚方法 残疾人飞镖比赛视频 新蒲萄京棋牌388怎么下载 天天计划手机版下载 老奶奶的关东煮游戏 开心棋牌app下载 北京pk10赚钱方法大全 广东手机彩票投注 pt下降是什么意思 在国外打工赚钱怎样带回国内 彩票赢本金的百分之三 高尔夫球游戏下载破解 天津十一选五预测 开机号近福彩3d开机号近10期 网赌怎么锁定你让你输