ABCDEFGHIJKLMNOPQRSTU
1
AUDIT: Waltham Forest SENDIASS
2
https://www.walthamforestsendiass.org.uk/
3
4
ChecklistPassed?Comment
5
Accessibility testing
6
Perceivable
7
Do all images have an appropriate text equivalent? Is essential visual information also available as text? For decorative images alt="" is required.Yes
8
Is all content structure that is communicated visually available to assistive technologies? i.e. Are we using semantic landmark areas such as <nav> <main> <section> <footer> <aside>Yes
9
If styling is removed is the content in a logical order?Yes
10
Have you avoided using visual characteristics to communicate information?Yes
11
Have you avoided using colour as the only way to convey some information?Yes
12
Does all text have sufficient contrast against the background colour?Yes
13
Is the content fully usable when text is enlarged up to 200%?Yes
14
Can users flip the content horizontally and vertically?Yes
15
Have you added HTML autocomplete tokens to any forms collecting information about the user?Yes
16
Does the page content resize to a single column with no horizontal and vertical scrolling?Yes
17
Do all important graphical objects, interface components, and states have a colour contrast of 3:1?Yes
18
Can line height, spacing between paragraphs and letter and word spacing be changed without breaking anything?Yes
19
Criteria commonly not applicable, please only amend status if required:
20
Where extra content is shown or hidden on focus, can it be dismissed, interacted with (and not disappear when the user moves to it) and will stay visible until dismissed by the user?N/A
21
Do all audio files have a transcript? Is essential audio information available as text?N/A
22
Do all videos have captions that are synchronised with the audio?N/A
23
Does video that includes important visual information have an audio description?N/A
24
Can users stop audio that auto plays?N/A
25
Have you avoided using images of text?N/A
26
27
28
Operable
29
Can all menus, links, buttons, and other controls be operated by keyboard?Yes
30
Can any content that moves or auto updates be stopped?N/A
31
Can blocks of links and other interactive elements be bypassed by keyboard users?Yes
32
Does each page have a unique title that indicates its purpose and context?Yes
33
When using a keyboard to move through a page does the order make sense?Yes
34
Is the purpose of every link clear from its link text?Yes
35
Does the website have two or more ways of finding content, such as a navigation menu, search feature, or site map?Yes
36
Are headings and labels clear and descriptive?Yes
37
When using a keyboard to move through a page can you tell where you are?Yes
38
On forms and other components is the accessible name or label the same as any on-screen text?Yes
39
Criteria commonly not applicable, please only amend status if required:
40
Does your site respond to motion or movement? If so, can responding to motion or movement be disabled, and your site still be fully usable?N/A
41
Do pages that have time limits include mechanisms for adjusting those limits?N/A
42
Have you avoided using content that flashes or flickers?N/A
43
Do you have shortcuts triggered by only one letter or character? If so can they be turned off or remapped by the user?N/A
44
Does some of your site functionality need several fingers or complex gestures to operate it? If so, can the same functionality be used with just single taps or clicks?N/A
45
Does some of your site functionality work using a single point (e.g fingertip)? If so, have you ensured it doesn’t get triggered the moment it is touched?N/A
46
47
48
Understandable
49
Does the website include consistent navigation?Yes
50
Are features with the same functionality labelled consistently?Yes
51
Do forms provide helpful, understandable error and verification messages?Yes
52
Criteria commonly not applicable, please only amend status if required:
53
Has the language of the web page or document (or individual parts of a multilingual document) been defined?N/A
54
Have you avoided links, controls, or form fields that automatically trigger a change in context?N/A
55
56
57
Robust
58
Is the web page coded using valid HTML?Yes
59
Do all interactive components have an accessible name and role, and when required state? Has the correct ARIA markup been used and does it validate?Yes
60
Are status messages and updates given appropriate roles that can be understood by AT, without receiving focus?Yes
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100