Web Accessibility Assessment Methodology in JSON-LD (Level AA)

• Documentation
• Questions or comments?

Here are the instructions to complete the assessment of each success criterion according the Web Accessibility Assessment Methodology (Level AA):

1. Copy the baseline JSON-LD file. (Download the baseline template)

2. Name your file according to the rules below.

   The proposed naming convention starts with the type of report (like acr which means Accessibility Conformance Report), followed by a dash, followed by a unique identifier and then:

   JSON-LD report

   Followed by a file extension suggesting the JSON file format. The pattern is : acr-{identifier}.json. Here are some examples: acr-1.json, acr-2023-03-16.json

   WET-BOEW - Report publication page

   Followed by a dash, followed by the 2 letters language code and followed by the file extension hbs. The pattern is : acr-{identifier}-{language}.hbs. Here are some examples: acr-1-en.hbs, acr-1-fr.hbs, acr-2023-03-16-en.hbs, acr-2023-03-16-fr.hbs

   GCWeb - Report publication page

   Followed by a dash, followed by the 2 letters language code and followed by the file extension html. The pattern is : acr-{identifier}-{language}.html. Here are some examples: acr-1-en.html, acr-1-fr.html, acr-2023-03-16-en.html, acr-2023-03-16-fr.html

3. Configure the HTML report template page

   WET-BOEW - Report publication page

   Use the following front-matter and adapt the page metadata to match the ACR publication context.

   ---
   {
   	"title": "Accessibility assessment #{identifier} - Topic",
   	"language": "{language}",
   	"altLangPage": "acr-{identifier}-fr.html",
   	"dateModified": "YYYY-MM-DD",
   	"layout": "acr-{language}.hbs",
   	"reportURL": "acr-{identifier}.json"
   }
   ---

   Update the following page properties:

   title

   Title of the Accessibility Conformance Report

   language

   2 letters language code of this published report

   altLangPage

   Filename of the language alternate page

   dateModified

   Date modified

   layout

   English report template: acr-en.hbs

   French report template: acr-fr.hbs

   reportURL

   JSON URL of the accessibility conformance report

   GCWeb - Report publication page

   Specific configurations are not published yet

4. Save and link the report, make it findable

   Add the new and contexualized files in the main plugin folder or component folder inside a sub-folder named reports.

   WET-BOEW - Report publication page

   Add a link to the English and French report from the plugin documentation page or in the dedicated section in the plugin working example page

   GCWeb - Report publication page

   Add a link to the English and French report from the component json-ld index file and optionally direct link from the component documentation page.

5. Update the following meta information required for your ACR report by using the baseline JSON-LD ACR:

   Report permanent URL (@id)

   Final URL of where this report is going to be published

   Pattern: {url}

   Example: https://wet-boew.github.io/wet-boew/demos/wamethod/demo-acr/acr-1.json

   Report identifier (reportId)

   Identifier for the report which makes it unique among the other ACR reports in the same location.

   Pattern: {identifier}

   Example: 1

   Subject URL (subjectUrl)

   URL of the asserted subject.

   Pattern: {URL}

   Example: https://example.com/url/of/the/page/being/assessed

   Assessor name (assertedBy/producedBy/name)

   Full name of the assessor, optionally followed by their GitHub handle

   Pattern: {Full Name} ({Social media name}: @{Social media handle})

   Example: The Octocat (GitHub: @octocat)

   Assessor identifier (assertedBy/producedBy/@id)

   Identifier URL to the assessor's social media profile page

   Pattern: {URL}

   Example: https://github.com/octocat

   Organization of the assessor (assertedBy/name)

   Name of the organization, optionally preceded by the department name

   Pattern: {Department name} - {Organization name}

   Example: Service Canada - Principal Publisher

   Organization identifier (assertedBy/@id)

   Identifier URL to the assessor's organization profile page

   Pattern: {URL}

   Example: https://github.com/ServiceCanada

   Assessment scope (scope)

   Scope of the assessment defining what is being assessed and what is out of scope. Also, a human readable note about what success criteria are going to be assessed against which standard which must match the property earl:test defined at the root of this report

   Pattern: {Description of the scope}

   Example: Partial evaluation focused only on the component {name of the component} and not its container. Evaluated all Success Criteria at Level AA of WCAG 2.1

6. Record the assessment of each individual success criteria. For each success criteria in the results property:

   The property label contains a human readable version of the success criterion title and the property earl:test is a programmatically determined reference to the success criterion item in the WCAG (Web Content Accessibility Guidance) published standard.

   Outcome in human readable format (outcome)

   Human readable text indicating the success criteria result state. The outcome and the result of the performed test.

   Pattern: {Outcome value}

   Reference: https://www.w3.org/TR/EARL/#OutcomeValue

   Example: Passed; Failed; Cannot tell; Inapplicable; Untested

   Outcome in machine readable format (earl:outcome)

   Machine readable data indicating the success criteria result state. The outcome and the result of the performed test which exactly match the property outcome.

   Pattern: {Reference to the outcome}

   Reference: https://www.w3.org/TR/EARL/#OutcomeValue

   Example: earl:passed; earl:failed; earl:cantTell; earl:inapplicable; earl:untested

   SC assessment notes (notes)

   Any notes about the assessment of this success criterion. Complement by adding the discussed technique or the one that is clearly fully applied in the 'technique' property to set a reference to its matching 'earl:TestRequirement'

   Pattern: {Human readable note}

   Referenced and applied techniques (techniques)

   List of machine readable reference to the referenced technique in the note and the technique that was clearly applied. The reference consist into a prefix followed by the technique identifier which we can easily deduct from the two (2) last sections of the technique URL.

   Pattern: WCAG2xTech:{ Technique identifier }

   Example: WCAG2xTech:failures/F100; WCAG2xTech:general/G94; WCAG2xTech:html/H42; WCAG2xTech:css/C6; WCAG2xTech:aria/ARIA13; WCAG2xTech:failures/client-side-script/SCR19; WCAG2xTech:server-side-script/SVR1; WCAG2xTech:pdf/PDF1; WCAG2xTech:smil/SM7; WCAG2xTech:text/T2

   Testing mode (earl:mode)

   Machine readable data indicating how the success criteria assessment has been performed.

   • Automated means the assessment was completed by an automated tool (like WAVE, axe, Accessibility Insights...) which has analyzed the subject page. The assessor is only logging the result without validating from the page source code or the page rendered view if that information is fully accurate.
   • Semi-automated means the assessment was completed with the assistance of some automated tool which has analyzed the subject page to help the assessor quickly identify some common issues and the assessor did validate from the source code and the rendered view the issues or comments valuable and applicable.
   • Manual means the assessment was completed by manually validating from the source code and the rendered view which didn't require a tool that has read from the source page but might have involved the use of a helper tool such as a color contrast online checker.

   Pattern: earl:{ Mode of the testing }

   Reference: https://www.w3.org/TR/EARL/#TestMode

   Example: earl:automatic; earl:manual; earl:semiAuto; earl:undisclosed; earl:unknownMode

   Notes:

   • Sample and specific instructions based on the type of assessment result are going to be published later.
   • More information about the use and the definition of some properties can be found in the WET-BOEW accessibility conformation report vocabulary extension.

7. Closing the initial assessment conformance report by adding the following meta information.

   Summary or/and general notes about the assessment (summary)

   A summary or/and a general notes made by the assertor regarding this assessment, observation or/and comments which will help to provide more context and improve the understanding of the assessment result itself. Also, it may contain any note that impact the conformance beyond the tested success criteria, like assessment comment related to section '5. Conformance' in WCAG 2.x.

   Pattern: {General note}

   Assessment conformance score (aggregatedScore)

   Percentage (%) manually calculated representing all the success criteria that have passed compared to the total of tested success criteria

   Pattern: {Success rate} %

   Example: 74%

8. Publish the ACR by opening a GitHub Pull Request according to our contribution guideline.

Date modified:

2023-03-16