Accessibility Audit Report
Staffordshire Commissioner's Website
Evaluation Commissioner: Netinspire
Report created by: Andrew Turner
Scope of the Audit
Web Content Accessibility Guidelines (WCAG) Version: 2.1
Conformance Target: AA
Summary of the Results
Overall accessibility is good but needs improvements in the following main areas:
- Keyboard Navigation
- Text alternatives for images and video content
- Ensuring labels are provided for all input fields
- Improve contrast levels of text on buttons and headings
This report is broken down into several sections which follow the 4 principles used by the Web Content Accessibility Guidelines (WCAG).
These principles are outlined below:
Perceivable
Web content is made available to the senses – sight, hearing, and/or touch
Operable
Interface forms, controls, and navigation are operable
Understandable
Information and the operation of user interface must be understandable.
Robust
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies
Each principle has a set of success criterion which your website must comply with to gain WCAG 2.1 compliance. A brief explanation of each criteria is provided along with the level of conformance which requires it.
Detailed audit results
1.0 Perceivable
Compliance
100%
1.1 Text Alternatives
Provide text alternatives for any non-text content
1.1.1 Non-Text Content
Images, form image buttons, and image map hot spots have appropriate, equivalent alternative text.
Form buttons have a descriptive value and Form inputs have associated text labels.
1.2 Time-based Media
Provide alternatives for atime-based media
1.2.1 Prerecorded Video-only and Audio-only Media
A transcript of relevant content is provided for non-live audio-only (audio podcasts, MP3 files, etc.).
A transcript or audio description of relevant content is provided for non-live video-only, unless the video is decorative.
1.2.2 Captions
Synchronized captions are provided for non-live video (YouTube videos, etc.).
1.2.3 Audio Description or Media Alternative (Prerecorded)
A transcript or audio description is provided for non-live video.
NOTE: Only required if there is relevant visual content that is not presented in the audio.
1.2.4 Captions (Live)
Synchronized captions are provided for live media that contains audio (audio-only broadcasts, web casts, video conferences, etc.)
1.2.5 Audio Description (Prerecorded)
Audio descriptions are provided for non-live video.
NOTE: Only required if there is relevant visual content that is not presented in the audio.
While not required at Level AA, for optimal accessibility WebAIM recommends transcripts in addition to audio description
1.3 Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure
1.3.1 Info and Relationships
Semantic markup is used to designate headings (h1), regions/landmarks, lists (h1, ul, ol), emphasized or special text (strong, abbr)
Tables are used for tabular data and data cells are associated with their headers. Data table captions, if present, are associated to data tables.
Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend. ARIA labelling may be used when standard HTML is insufficient.
1.3.2 Meaningful Sequence
The reading and navigation order (determined by code order) is logical and intuitive.Data table captions, if present, are associated to data tables.
Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend. ARIA labelling may be used when standard HTML is insufficient.
1.3.3 Sensory Characteristics
Instructions do not rely upon shape, size, or visual location (e.g., “Click the square icon to continue” or “Instructions are in the right-hand column”).
1.3.4 Orientation
Orientation of web content is not restricted to only portrait or landscape, unless a specific orientation is necessary.
1.3.5 Identify Input Purpose
Input fields that collect certain types of user information have an appropriate autocomplete attribute defined.
1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background
1.4.1 Use of Color
Color is not used as the sole method of conveying content or distinguishing visual elements. Color alone is not used to distinguish links from surrounding text unless the contrast ratio between the link and the surrounding text is at least 3:1 and an additional distinction (e.g., it becomes underlined) is provided when the link is hovered over and receives focus.
1.4.2 Audio Control
A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.
1.4.3 Contrast
Text and images of text have a contrast ratio of at least 4.5:1.
Large text – at least 18 point (typically 24px) or 14 point (typically 18.66px) and bold – has a contrast ratio of at least 3:1.
1.4.4 Resize Text
The page is readable and functional when the page is zoomed to 200%.
1.4.5 Images of Text
If the same visual presentation can be made using text alone, an image is not used to present that text.
1.4.10 Reflow
No loss of content or functionality occurs and horizontal scrolling is avoided when content is presented at a width of 320 pixels. This requires responsive design for most web sites. This is best tested by setting the browser window to 1280 pixels wide and then zooming the page content to 400%.
1.4.11 Non-text Contrast
A contrast ratio of at least 3:1 is present for differentiating graphical objects (such as icons and components of charts or graphs) and author-customized interface components (such as buttons, form controls, and focus indicators/outlines).
At least 3:1 contrast must be provided in the various states (focus, hover, active, etc.) of author-customized interactive components.
1.4.12 Text Spacing
No loss of content or functionality occurs when the user adapts paragraph spacing to 2 times the font size, text line height/spacing to 1.5 times the font size, word spacing to .16 times the font size, and letter spacing to .12 times the font size.
1.4.13 Content on Hover or Focus
When additional content is presented on hover or keyboard focus
2.0 Operable
Compliance
100%
2.1 Make all functionality available from a keyboard
2.1.1 Keyboard
All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
2.1.2 Keyboard Trap
Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.
2.1.4 Character Key Shortcuts
If a keyboard shortcut uses printable character keys, then the user must be able to disable the key command, change the defined key to a non-printable key (Ctrl, Alt, etc.), or only activate the shortcut when an associated interface component or button is focused.
2.2 Enough Time
Provide users enough time to read and use content
2.2.1 Timing Adjustable
If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.
2.2.2 Pause, Stop, Hide
Automatically moving, blinking, or scrolling content (such as carousels, marquees, or animations) that lasts longer than 5 seconds can be paused, stopped, or hidden by the user.
2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
2.3.1 Three Flashes or Below Threshold
No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red.Â
2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks
A link is provided to skip navigation and other page elements that are repeated across web pages.sufficiently small and the flashes are of low contrast and do not contain too much red.Â
2.4.2 Page Titled
The web page has a descriptive and informative page title.
2.4.3 Focus Order
The navigation order of links, form elements, etc. is logical and intuitive.
2.4.4 Link in Purpose Text
The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding text, list item, previous heading, or table headers).
2.4.5 Multiple Ways
Multiple ways are available to find other web pages on the site – at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.
2.4.6 Headings and Labels
Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., “More Details”) or label text (e.g., “First Name”) unless the structure provides adequate differentiation between them.
2.4.7 Focus Visible
It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are).
2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures
If multipoint or path-based gestures (such as pinching, swiping, or dragging across the screen) are not essential to the functionality, then the functionality can also be performed with a single point activation (such as activating a button).
2.5.2 Pointer Cancellation
To help avoid inadvertent activation of controls, avoid non-essential down-event (e.g., onmousedown) activation when clicking, tapping, or long pressing the screen. Use onclick, onmouseup, or similar instead. If onmouseup (or similar) is used, you must provide a mechanism to abort or undo the action performed.
2.5.3 Label in Name
If an interface component (link, button, etc.) presents text (or images of text), the accessible name (label, alternative text, aria-label, etc.) for that component must include the visible text.
2.5.4 Motion Actuation
Functionality that is triggered by moving the device (such as shaking or panning a mobile device) or by user movement (such as waving to a camera) can be disabled and equivalent functionality is provided via standard controls like buttons.
3.0 Understandable
Compliance
100%
3.1 Readable
Make text content readable and understandable
3.1.1 Language of Page
The language of the page is identified using the HTML lang attribute (e.g., <html lang=”en”>).
3.1.2 Language of Parts
The language of page content that is in a different language is identified using the lang attribute
3.2 Predictable
Make Web pages appear and operate in predictable ways
3.2.1 On Focus
When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
3.2.2 On Input
When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
3.2.3 Consistent Navigation
Navigation links that are repeated on web pages do not change order when navigating through the site.
3.2.4 Consistent Identification
Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
3.3 Input Assistance
Help users avoid and correct mistakes
3.3.1 Error Identification
Required form elements or form elements that require a specific format, value, or length provide this information within the element’s label.
Form validation errors are efficient, intuitive, and accessible. The error is clearly identified, quick access to the problematic element is provided, and the user can easily fix the error and resubmit the form.
3.3.2 Labels or Instructions
Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
3.3.3 Error Suggestion
If an input error is detected (via client-side or server-side validation), suggestions are provided for fixing the input in a timely and accessible manner.
3.3.4 Error Prevention (Legal, Financial)
If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.
4.0 Robust
Compliance
100%
4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies
4.1.1 Parsing
Significant HTML/XHTML validation/parsing errors are avoided. Check at http://validator.w3.org/
4.1.2 Name, Role, Value
Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.
ARIA is used appropriately to enhance accessibility when HTML is not sufficient.
4.1.3 Status Messages
If an important status message is presented and focus is not set to that message, the message must be announced to screen reader users, typically via an ARIA alert or live region.
This report was compiled by using the WCAG-EM Report Tool and the simplified criterion explanations from the WebAIM Checklist.
