You have to make sure people can understand your content and how the service works.
- Identify
- Test
- Action
- Improve
Identifying and Simplifying Labels
Labels should convey meaning and purpose in a unique and clear way. For example, a link to send an email displayed as an envelope icon should have the label 'email us' rather than 'envelope'. Links to 'read more' should include the context, such as "read more about our services".
Other Recommendations
- Check videos for captions.
Hosting videos and audio on YouTube improves accessibility and supports compliance by enabling captions, subtitles, audio descriptions, and compatibility with screen readers and keyboard navigation. Find out more on our compliance page.
- Look for links with generic link text such as "click here" or "more info." These types of links can be confusing to screen reader users and should be replaced with more descriptive link text.
Do's
- Use simple colours
- Write in plain language
- Use simple sentences and bullets
- Make buttons descriptive
- Build simple and consistent layouts
Don'ts
- Use bright contrasting colours
- Use figures of speech and idioms
- Create a wall of text
- Make buttons vague and unpredictable
- Build complex and cluttered layouts
Continue your learning here:
Supplemental guidelines
Mobile First!
Learn moreSupplemental guidelines
Commercial
Learn moreTools & Checklist:
Supplemental guidelines
WCAG Ratings
Learn moreSupplemental guidelines
Testing Checklist
Learn moreSupplemental guidelines
Resources
Learn moreYou have to make sure people can understand your content and how the service works.
- Make it clear what language the content is written in, and indicate if this changes
- Make it easy for people to identify and correct errors in forms
- Make it easy for people to re-enter information they've previously entered into a form
- Make it easy for people to log in without having to remember information or solve a problem
-
Types of Manual Testing
- Black box testing:
- White box testing:
- Gray box testing:
It is a type of software testing technique that focuses on testing the functionality of a software system without any knowledge of its internal workings. This technique is used to test the system from a user's perspective, focusing on testing whether the system works as expected and meets the user's needs. The tester only knows the inputs and expected outputs of the system and does not know how the system works internally.
This technique is used to test the system from a developer's perspective, focusing on testing the system's internal logic, performance, and efficiency. The tester has complete knowledge of the system's internal details, including the code and its implementation.
Combines the approaches of both black box and white box testing. This technique follows from a developer's perspective, the focus is on testing some of the system's internal workings but not all. The tester has partial knowledge of the system's internal details.
-
Testing Without Tools
- In a form, is it clear which data is expected and which fields are obligatory?
- Text resizing
- Does text appear larger when you have set a larger font?
- Can all text be read with the largest font?
- Are textual alternatives available for all non-text content?
- Is the structure of a page clear to users of assistive technologies?
- Is the order of elements clear to assistive technologies?
- Can you operate the app with assistive technologies?
- Are there places in the app where you get stuck using the keyboard?
- Do the headings and labels describe the content clear enough?
- Is the correct name, role and value given?
Ensure clear instructions are provided in places users have to input data. Add a label to the input fields, for example 'First name'. Mark whether fields are required or optional. Indicate if data must be entered in a specified order.
On a mobile phone you can turn on text resizing in the system settings. This works differently on different devices, but if you search for "text" in the system settings, you will see the text size option. If you set this to maximum, you can then see whether your app uses large fonts and whether this does not lead to errors.
It is important for visually impaired users that text can be enlarged. Users specify their preferred font size in the system settings. Text in your app should resize according to this preferred font size. Ensure that the text in your app supports resizing.
Ensure that all content on the screen remains readable even with the largest font. Content should be readable without having to scroll in two directions. Because the text is displayed larger, it can push other elements off the screen. Ensure content can still be reached, for example, by scrolling vertically.
People who are blind use a screen reader to read the information on the screen. Make sure that a description is available for all non-text content. Images, for example. By describing them the screen reader can read what you see.
Information on the screen must be conveyed to assistive technologies. For example, make sure that headings are not only bold, but also marked as headings in the code. Relationships on the screen must be usable with assistive technologies. Elements in a list must be navigable one by one. Elements in a table must be navigable by rows and columns.
Make sure that the order which assistive technologies follow reflect the meaning of the content. Otherwise, users of assistive technology may misunderstand the content. Most content is presented from left to right, from top to bottom. The information should also be presented to users of assistive technologies in this way.
Make sure that all functionality in the app can be used with assistive technologies. People who are blind use the screen reader. People with a motor disability use switch control, voice control and/or the keyboard. These assistive technologies are built into the operating system.
Prevent people using an external keyboard from getting stuck in your app. For example, it often happens that pop-ups cannot be closed with a keyboard. You can test this to a large extent with a screen reader.
The use of headings is important to understand how the content is structured. Blind users can use a screen reader to request an overview of all headings on the screen. The use of labels is important with forms to understand what input is requested. Make sure the labels are linked to the input fields.
It should be clear to users of assistive technologies what actions they can take. Make sure that the name, role and value can be determined for all elements. For example, when you use an image as a button, you must set the role as a button.
You must make sure your content can be interpreted reliably by a wide variety of user agents (including assistive technologies).
- Make sure your code lets assistive technologies know what every user interface component is for, what state it's currently in and if it changes.
- Make sure important status messages or modal dialogs are marked up in a way that informs users of their presence and purpose, and lets them interact with them using their assistive technology.
- Make sure interactive elements such as buttons are big enough or spaced far enough apart to make it easy to select the right one
- Make sure features look consistent and behave in predictable ways, including help mechanisms
- Make sure all form fields have visible and meaningful labels - and that they're marked up properly
- Make sure your service works well with assistive technologies - for example, important messages are marked up in a way that the screen readers knows they're important
Continue your learning here:
Supplemental guidelines
Mobile First!
Learn moreSupplemental guidelines
Commercial
Learn moreTools & Checklist:
Supplemental guidelines
WCAG Ratings
Learn moreSupplemental guidelines
Testing Checklist
Learn moreSupplemental guidelines
Resources
Learn moreEnsure you're using semantic HTML - start by using proper HTML markup.
- Semantic tags (like <h1>, <nav>, <article>, etc.). This is vital for screen readers and other assistive technologies. It enables them to understand the hierarchy of the content and structure of the page. It will also be beneficial for the SEO of the website as search engines also use the tags and correctly implemented semantic HTML is ranked higher than if not.
- Having all the content correctly tagged will also be useful when it comes to making design updates. The CSS that controls the font, colour and other styling, need only be amended once for the whole site.
- If implementing tools like the CityMaas Assist Me plug in, semantic html is essential for integrating the tool so it can implement the users preferences.
- Although there is no specific limit, <h1> content should be between 20 & 70 characters. Otherwise there's a high chance the heading won't be readable for your visitors and this hurts their user experience.
- Note: There should only be one <h1> per page, though there can be multiple <h2>, <h3> etc.
-
Keyboard Navigation & HTML Structure
- Keyboard Navigation:
- Headings and Structure:
- Forms and Labels:
- Simplify Design:
Test your website using only a keyboard. Make sure all interactive elements (buttons, links, forms) are accessible via keyboard navigation. Avoid relying solely on mouse-based interactions.
Use headings (from <h1> to <h6>) to organise your content logically. Properly structured headings create a clear hierarchy and improve navigation for all users.
Label form fields clearly and associate them with their respective input elements. Screen readers rely on labels to provide context.
Also, consider using placeholders as additional hints. Ensure that users are able to navigate forms correctly using the keyboard and also that content works correctly with the auto fill feature in the web browser.
As well as looking good, minimalistic designs often work better for accessibility. Too much clutter can overwhelm users. Prioritise essential content and avoid unnecessary distractions. Question whether anything you add is adding value to the page design or just making it more cluttered and confusing.
-
Responsive Design (Reflow):
Your website needs to be responsive. It should use the same content across all devices but the layout must adapt to the different size screens and zoom levels ensuring content can be presented without losing any information or functionality.
Check on actual mobile devices and tablets as well as using the 'inspect' function in your web browser to emulate a cross section of devices and screen orientations. Look at it through different web browser applications too as they can show variation.
It should be designed from a mobile first perspective as for most websites, more users will be viewing on their mobile device.
Remember, accessibility isn't just about compliance; it's about creating an inclusive digital experience. By following these practices, you'll make your website more welcoming to all visitors, regardless of their abilities or disabilities.
Image Alt Text and Labels:
- Always provide descriptive alternative text (alt text) for images. This allows screen readers to convey the content of images to users who cannot see them. Keep alt text concise but informative.
- If the image has a label underneath it, this should be different from the alt tag and not considered the image's caption, title or legend. Also, if they are the same then a screen reader will end up repeating the same text.
- Your alt tag describing the image could be "a woman applying lipstick in front of a mirror" and the image label underneath might read "One application and it lasts all day"
- Again, putting alt tags in is also good for SEO.
- Other reasons for using alt tags are that if there is an issue with the page loading correctly, the alt tag will be displayed where the image should be.
- Note: If an image is purely decorative, it is better to put the alt tag attribute in but leave the content empty. E.g. <img src="image.gif" alt="">
Continue your learning here:
Supplemental guidelines
Mobile First!
Learn moreSupplemental guidelines
Commercial
Learn moreTools & Checklist:
Supplemental guidelines
WCAG Ratings
Learn moreSupplemental guidelines
Testing Checklist
Learn moreSupplemental guidelines
Resources
Learn moreSimplify and structure your content for clarity
- Simplify your text: We live in a fast paced world where we are bombarded with digital information. People want their information quickly and easily digestible so they can get on with their busy lives. Having pages and pages for the user to trawl through is going to make them 'click away' to the next website. Where possible, use expert content writers to make your text concise and engaging without losing the important bits of messaging. Make sure they include key search words within the copy for users to find your page on search engines.
- Make it meaningful: Try not to repeat the same information in a different way on each page. Otherwise people will feel like they're not going to learn anything else on the other pages. Make sure there is a logical structure to your site. If it's an ecommerce site, you might need different categories for your products.
- Use descriptive CTAs: Where possible, label CTAs to include context such as with text that describes what it does. E.g. in a section related to make-up products, instead of a CTA saying 'Shop Now', consider something like 'Shop all make-up products'. Then there can be no confusion where this CTA takes you and is particularly helpful to anyone using a screen reader.
- Consistent Navigation: Make sure you standardise your navigation. Keeping the position, style, colour and terminology consistent throughout your site makes it clear where to click and easier to follow. If reinforcing with icons, ensure they make sense, are consistent and look like part of the same family in terms of style.
Cognitive