M8
Status
New technique.
Applicability
This technique applies to mobile apps and mobile web content.
WCAG references
- content-structure-separation-programmatic: SC 1.3.1 Info and Relationships (Advisory)
User Agent and Assistive Technology Support Notes
Provide notes regarding known lack of support for this technique with particular user agents or assistive technologies.
Description
The objective of this technique is to..." and describe what the user should accomplish, then move on to how. Some techniques are best explained through examples, but an overview of the approach should still be provided in the description.
Examples
Examples for the technique, or links to external examples. Provide a description of the example, and source code if applicable. Explanatory content can be intermixed with code samples.
If you are providing multiple examples, there are two approaches:
- Simple examples can just be provided in a bulleted list.
- More elaborate examples should have sub-headers for each example. Provide a descriptive title for the header but do not number them, this is done later in the process. Use the samples in this template for each example.
You can include links to working examples or upload examples (see "upload file" link under tools navbar) to the wiki as needed.
Description of example.
Code sample. Be sure to put a space at the beginning of each line, and manually wrap lines so they don't push out to the right.
This technique is shown in operation in the working example of {technique or example title}. The source code of {technique or example title} is also available.
Resources
Provide a list of links to external resources, if any.
Related Techniques
Provide a list of related techniques. For techniques that are part of the published suite, a technique id (ex. H30) is sufficient. For techniques that exist only in the wiki, link to the wiki page.
Tests
Describe how to test reliably that the technique has been applied, or that it has not been applied. If there is more than one type of test procedure, copy the entire section including the "Tests" header, and provide information about the type of test in this space before the "Procedure" header.
Procedure
If there are any prerequisite tests, list passing them as a required first step in the procedure. Provide an ordered list of steps, with at least one step to check for a particular condition.
- step 1
- step 2
- check that xyz
Expected Results
Indicate which step(s) from the test procedure must evaluate to true. For failure techniques, use wording like "If check #2 is false, then this failure condition applies and the content fails this success criterion."
- #3 is true
Test Files
Provide test files here. Currently, techniques do not reference test files, but we may do something with them in the future. Note that working examples (including source code) do not go here, they should be referenced in the examples section.