Manually checking web content for digital accessibility
Automated tools like aXe, WAVE, and Lighthouse are effective at identifying a wide range of accessibility issues. However, their algorithms lack the capacity to fully replicate the complexities of human perception and experience.
This page provides information about common accessibility gaps missed by automated tools, providing you with easy-to-follow steps for manually testing any web page or interface. These manual testing suggestions align with WCAG 2.2, the UK Government ‘Simplified testing process’ and will help to ensure that all web content is accessible for everyone, regardless of background, technology or disability.
Automated accessibility tools
The Library / University recommends the following automated tools for checking web content against accessibility guidelines:
- WAVE Web Accessibility Evaluation Tool - a free, visual tool that provides visual feedback about the accessibility of web content by injecting icons and indicators into the page.
- Lighthouse (Google product) - a free accessibility, SEO and best practice tool that can be accessed from within Google Chrome and Edge (Developer Tools). Browser extensions are also available.
- aXe (Google / Microsoft endorsed) - a free accessibility auditing tool that is available in both Chrome DevTools and as an extension.
- Siteimprove - a paid, University endorsed tool that is used to audit accessibility for T4 managed University websites and StaffNet. Contact the Digital Library Development Team for more information or access to reports.
Please bear in mind that these tools will not pick up all accessibility issues, and some manual testing will still be required.
Zoom and responsiveness
WCAG 1.4.4: Resize text
Zoom in up to 400%. Can you still read all content comfortably? Is any content cut off or hidden?
WCAG 1.4.10: Reflow
Simulate small screens by using browser developer tools or resizing your browser window to see how the page appears on mobile devices. Are all elements accessible and readable?
Keyboard navigation
WCAG 2.1.1: Keyboard focusable
Tab through the entire web page. Use only your keyboard to navigate all pages. Make sure you can reach every link, button, and form element without using a mouse.
WCAG 2.2.5: Focus appearance
Check the contrast between the focused element and its surroundings. Is it clear and easy to see where the focus is?
WCAG 2.4.3: Focus order
Is the focus order logical? Tab through elements in a predictable order like top to bottom or left to right. Do unexpected elements take focus, or unexpected actions occur?
Audio and visual content
WCAG 1.2.1: Audio-only and video-only (prerecorded)
Check if videos and audio have accurate captions or transcripts so people with hearing impairments can still access the information.
WCAG 1.1.1: Non-text content
Descriptive text alternatives should be provided for all images, Check the image ‘alt’ text, does it accurately convey the contents of the image?
Interaction
WCAG 2.5.7: Dragging movements
Make sure any functionality requiring drag-and-drop can be achieved without dragging, or the drag operation is accessible with alternate methods (eg. keyboard only).
WCAG 2.5.8: Target size
Assure touch targets like buttons and links are large enough for easy activation with fingers. The recommended minimum size for touch elements is 44 x 44 CSS pixels.
Authentication
WCAG 3.3.8 Accessible authentication
Confirm login processes can be completed via keyboard alone, assistive technologies and alternative authentication methods are available if needed.
Help, support and online forms
WCAG 3.2.6: Consistent help
Verify help mechanisms consistently appear in the same relative location across pages. Check that the ‘Help’ content itself is easily accessible and understandable.
WCAG 3.3.7: Redundant entry
Check if forms offer multiple ways to input information (eg. typing, drop down menus) to reduce reliance on one method. Look out for forms that require users to re-enter the same information repeatedly within a process.
Conducting an accessibility audit
Information around how to conduct a technical, third-party funded or basic accessibility audit.
Read more
Logging and resolving accessibility issues
Find out how to log accessibility issues and seek support in resolving them.
Read more
Accessibility statements
Library accessibility statements for customer and staff-facing interfaces.
Read more