v32.1.1
Page architecture
How to test each rule in the page architecture group
These are almost all the rules that are tested involving page architecture rules. These require a more hollistic view of your product and are not necessarily confined to a single page.
| Rule number | Rule | How to test |
|---|---|---|
| 2.4.2 | Page titled | Code assessment |
| 2.4.5 | Multiple ways | Flows + browser assessment |
| 3.1.1 | Language of page | Code assessment |
| 3.1.2 | Language of parts | Code assessment |
| 3.2.3 | Consistent Navigation | Flows + Product interactivity |
| 3.2.4 | Consistent Identification | Flows + Visual product audit |
2.4.2 Page titled
Your product should have a unique descriptive title for each page.
2.4.5 Multiple ways
For every page in your product there should be more than one way to reach that content. Modals that don't trigger a change of URL for example, and can only be accessed through a flow doesn't pass this rule.
3.1.1 Language of page
Check your page for the meta attribute "lang" that allows for user agents to better parse the language of the page.
3.1.2 Language of parts
Check all human language that shows on your page. If your page has more than one language, all pieces of text should be identified with the specific language of that part. This helps assistive technology to read it properly.
3.2.3 Consistent navigation
This requires a full product audit. Flows and interactions that occur in different places need to happen the same way and have the same effects.
3.2.4 Consistent identification
Components, icons, graphics and other visual parts of your application need to have the same meaning everywhere. See which parts fit this rule here
Continue to Media.
Is this page helpful?