Skip to content

Commit

Permalink
Address issues with consistency to originals (#259)
Browse files Browse the repository at this point in the history 
* Fix #257
* Fix #255
* Fix #247
* Fix #254
* Fix #198
  • Loading branch information
@iadawn
iadawn authored Aug 2, 2024
1 parent 177420b commit 7b70579
Showing 1 changed file with 59 additions and 163 deletions.
222 changes: 59 additions & 163 deletions _data/wcag22.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -97,10 +97,6 @@
"id": "TECH:H2",
"title": "Combining adjacent image and text links for the same resource"
},
{
"id": "TECH:H35",
"title": "Providing text alternatives on applet elements"
},
{
"id": "TECH:H37",
"title": "Using alt attributes on img elements"
Expand Down Expand Up @@ -149,10 +145,6 @@
"id": "TECH:H2",
"title": "Combining adjacent image and text links for the same resource"
},
{
"id": "TECH:H35",
"title": "Providing text alternatives on applet elements"
},
{
"id": "TECH:H37",
"title": "Using alt attributes on img elements"
Expand Down Expand Up @@ -192,10 +184,6 @@
"id": "TECH:G92",
"title": "Providing long description for non-text content that serves the same purpose and presents the same information"
},
{
"id": "TECH:H45",
"title": "Using longdesc"
},
{
"id": "TECH:H53",
"title": "Using the body of the object element"
Expand Down Expand Up @@ -276,10 +264,6 @@
"id": "TECH:H2",
"title": "Combining adjacent image and text links for the same resource"
},
{
"id": "TECH:H35",
"title": "Providing text alternatives on applet elements"
},
{
"id": "TECH:H37",
"title": "Using alt attributes on img elements"
Expand Down Expand Up @@ -324,10 +308,6 @@
"id": "TECH:H2",
"title": "Combining adjacent image and text links for the same resource"
},
{
"id": "TECH:H35",
"title": "Providing text alternatives on applet elements"
},
{
"id": "TECH:H37",
"title": "Using alt attributes on img elements"
Expand Down Expand Up @@ -372,10 +352,6 @@
"id": "TECH:H2",
"title": "Combining adjacent image and text links for the same resource"
},
{
"id": "TECH:H35",
"title": "Providing text alternatives on applet elements"
},
{
"id": "TECH:H37",
"title": "Using alt attributes on img elements"
Expand Down Expand Up @@ -1003,13 +979,6 @@
}]
}]
},
{
"advisory": [
{
"id": "TECH:H46",
"title": "Using noembed with embed"
}]
},
{
"failure": [
{
Expand Down Expand Up @@ -1158,10 +1127,6 @@
"id": "TECH:H39",
"title": "Using caption elements to associate data table captions with data tables"
},
{
"id": "TECH:H73",
"title": "Using the summary attribute of the table element to give an overview of data tables"
},
{
"id": "TECH:H63",
"title": "Using the scope attribute to associate header cells and data cells in data tables"
Expand Down Expand Up @@ -1308,10 +1273,6 @@
"id": "TECH:F48",
"title": "Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information"
},
{
"id": "TECH:F87",
"title": "Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using ::before and ::after pseudo-elements and the 'content' property in CSS"
},
{
"id": "TECH:F90",
"title": "Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes"
Expand Down Expand Up @@ -1489,8 +1450,26 @@
{ "text": "The input field serves a purpose identified in the Input Purposes for User Interface Components section; and" },
{ "text": "The content is implemented using technologies with support for identifying the expected meaning for form input data." }
]
}]
},
}],
"techniques": [
{
"sufficient": [
{
"id": "TECH:H98",
"title": "Using HTML 5.2 autocomplete attributes"
}]
},
{
"advisory": []
},
{
"failure": [
{
"id": "TECH:F107",
"title": "Failure of Success Criterion 1.3.5 due to incorrect autocomplete attribute values"
}]
}]
},
{
"id": "WCAG2:identify-purpose",
"alt_id": [],
Expand Down Expand Up @@ -2739,7 +2718,11 @@
"title": "All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.",
"techniques": [
{
"sufficient": []
"sufficient": [
{
"id": "TECH:text",
"title": "No additional techniques exist for this Success Criterion. Follow <a href=\"#keyboard\">techniques for Success Criterion 2.1.1</a>. If that is not possible because there is a requirement for path-dependent input, then it is not possible to meet this Level AAA Success Criterion."
}]
},
{
"advisory": []
Expand Down Expand Up @@ -2988,10 +2971,6 @@
"id": "TECH:G11",
"title": "Creating content that blinks for less than 5 seconds"
},
{
"id": "TECH:G187",
"title": "Using a technology to include blinking content that can be turned off via the user agent"
},
{
"id": "TECH:G152",
"title": "Setting animated gif images to stop blinking after n cycles (within 5 seconds)"
Expand Down Expand Up @@ -3345,15 +3324,8 @@
"title": "Providing headings by marking content with heading tags in PDF documents"
},
{
"and": [
{
"id": "TECH:H70",
"title": "Using frame elements to group blocks of repeated material"
},
{
"id": "TECH:H64",
"title": "Using the title attribute of the frame and iframe elements"
}]
"id": "TECH:H64",
"title": "Using the title attribute of the frame and iframe elements"
},
{
"id": "TECH:SCR28",
Expand Down Expand Up @@ -3461,8 +3433,8 @@
"title": "Inserting dynamic content into the Document Object Model immediately following its trigger element"
},
{
"id": "TECH:SCR37",
"title": "Creating Custom Dialogs in a Device Independent Way"
"id": "TECH:H102",
"title": "Creating modal dialogs with the HTML dialog element"
},
{
"id": "TECH:SCR27",
Expand Down Expand Up @@ -3655,10 +3627,6 @@
},
{
"advisory": [
{
"id": "TECH:H59",
"title": "Using the link element and navigation tools"
},
{
"id": "TECH:PDF2",
"title": "Creating bookmarks in PDF documents"
Expand Down Expand Up @@ -3783,12 +3751,7 @@
},
{
"id": "TECH:G127",
"title": "Identifying a Web page's relationship to a larger collection of Web pages",
"using": [
{
"id": "TECH:H59",
"title": "Using the link element and navigation tools"
}]
"title": "Identifying a Web page's relationship to a larger collection of Web pages"
}]
},
{
Expand Down Expand Up @@ -3918,6 +3881,24 @@
"type": "note",
"handle": "Note 2",
"text": "This success criterion covers sections within writing, not user interface components. User Interface components are covered under Success Criterion 4.1.2."
}],
"techniques": [
{
"sufficient": [
{
"id": "TECH:G141",
"title": "Organizing a page using headings"
},
{
"id": "TECH:H69",
"title": "Providing heading elements at the beginning of each section of content"
}]
},
{
"advisory": []
},
{
"failure": []
}]
},
{
Expand Down Expand Up @@ -4569,10 +4550,6 @@
{
"id": "TECH:H40",
"title": "Using description lists"
},
{
"id": "TECH:H60",
"title": "Using the link element to link to a glossary"
}]
},
{
Expand All @@ -4596,10 +4573,6 @@
{
"id": "TECH:H40",
"title": "Using description lists"
},
{
"id": "TECH:H60",
"title": "Using the link element to link to a glossary"
}]
},
{
Expand All @@ -4626,10 +4599,6 @@
{
"id": "TECH:H40",
"title": "Using description lists"
},
{
"id": "TECH:H60",
"title": "Using the link element to link to a glossary"
}]
},
{
Expand Down Expand Up @@ -4705,10 +4674,6 @@
"id": "TECH:G62",
"title": "Providing a glossary"
},
{
"id": "TECH:H60",
"title": "Using the link element to link to a glossary"
},
{
"id": "TECH:G70",
"title": "Providing a function to search an online dictionary"
Expand Down Expand Up @@ -5006,7 +4971,7 @@
"handle": "Consistent Identification",
"title": "Components that have the same functionality within a set of Web pages are identified consistently.",
"sufficientNotes": [
"Text alternatives that are \u201cconsistent\u201d are not always \u201cidentical.\u201d For instance, you may have an graphical arrow at the bottom of a Web page that links to the next Web page. The text alternative may say \u201cGo to page 4.\u201d Naturally, it would not be appropriate to repeat this exact text alternative on the next Web page. It would be more appropriate to say \u201cGo to page 5\u201d. Although these text alternatives would not be identical, they would be consistent, and therefore would satisfy this Success Criterion.",
"Text alternatives that are \u201cconsistent\u201d are not always \u201cidentical.\u201d For instance, you may have a graphical arrow at the bottom of a Web page that links to the next Web page. The text alternative may say \u201cGo to page 4.\u201d Naturally, it would not be appropriate to repeat this exact text alternative on the next Web page. It would be more appropriate to say \u201cGo to page 5\u201d. Although these text alternatives would not be identical, they would be consistent, and therefore would satisfy this Success Criterion.",
"A single non-text-content-item may be used to serve different functions. In such cases, different text alternatives are necessary and should be used. Examples can be commonly found with the use of icons such as check marks, cross marks, and traffic signs. Their functions can be different depending on the context of the Web page. A check mark icon may function as \u201capproved\u201d, \u201ccompleted\u201d, or \u201cincluded\u201d, to name a few, depending on the situation. Using \u201ccheck mark\u201d as text alternative across all Web pages does not help users understand the function of the icon. Different text alternatives can be used when the same non-text content serves multiple functions."
],
"techniques": [
Expand Down Expand Up @@ -5682,13 +5647,21 @@
}],
"techniques": [
{
"sufficient": []
"sufficient": [
{
"id": "TECH:G220",
"title": "Provide a contact-us link in a consistent location"
}]
},
{
"advisory": []
},
{
"failure": []
"failure": [
{
"id": "TECH:text",
"title": "Inconsistent Help Location"
}]
}]
},
{
Expand Down Expand Up @@ -5907,83 +5880,6 @@
"handle": "Compatible",
"title": "Maximize compatibility with current and future user agents, including assistive technologies.",
"successcriteria": [
{
"id": "WCAG2:parsing",
"alt_id": ["ensure-compat-parses"],
"num": "4.1.1",
"versions": [
"2.0",
"2.1"
],
"level": "A",
"handle": "Parsing",
"title": "In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.",
"details": [
{
"type": "note",
"handle": "Note 1",
"text": "This Success Criterion should be considered as always satisfied for any content using HTML or XML."
},
{
"type": "note",
"handle": "Note 2",
"text": "Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [HTML]<br><br>Although the HTML Standard treats some of these cases as non-conforming for authors, it is considered to “allow these features” for the purposes of this Success Criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.<br><br>Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different Success Criteria and should be reported under those criteria rather than as issues with 4.1.1."
}, ],
"techniques": [
{
"sufficient": [
{
"id": "TECH:G134",
"title": "Validating Web pages"
},
{
"id": "TECH:G192",
"title": "Fully conforming to specifications"
},
{
"id": "TECH:H88",
"title": "Using HTML according to spec"
},
{
"id": "TECH:text",
"title": "Ensuring that Web pages can be parsed by using one of the following techniques:",
"using": [
{
"and": [
{
"id": "TECH:H74",
"title": "Ensuring that opening and closing tags are used according to specification"
},
{
"id": "TECH:H93",
"title": "Ensuring that id attributes are unique on a Web page"
},
{
"id": "TECH:H94",
"title": "Ensuring that elements do not contain duplicate attributes"
}]
},
{
"id": "TECH:H75",
"title": "Ensuring that Web pages are well-formed"
}]
}]
},
{
"advisory": []
},
{
"failure": [
{
"id": "TECH:F70",
"title": "Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup"
},
{
"id": "TECH:F77",
"title": "Failure of Success Criterion 4.1.1 due to duplicate values of type ID"
}]
}]
},
{
"id": "WCAG2:name-role-value",
"alt_id": ["ensure-compat-rsv"],
Expand Down

0 comments on commit 7b70579

Please sign in to comment.