What is Web Accessibility?
Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. Web accessibility encompasses all disabilities that affect access to the Web which can include auditory, cognitive, neurological, physical, speech and visual requirements.
Learn how accessibility is essential for people with disabilities and useful for everyone:
How can Web Accessibility affect my business?
For a business, accessible design improves overall user experience and satisfaction, especially in a variety of situations across different devices and for older users. Accessibility can enhance your brand, drive innovation, and extend your market reach.
Who provides guidance towards Web Accessibility?
The W3C Web Accessibility Initiative (WAI) develops technical specifications, guidelines, techniques, and supporting resources for accessibility solutions.
What are the guidelines?
WAI provides Web Content Accessibility Guidelines (WCAG). These are a list of rules for making the web available to everyone, especially those with cognitive, physical or sensory disabilities.
What are conformance levels?
WCAG conformance levels are testable requirements known as success criteria. Each success criteria has it's own level or version:
- 1.0: Guidelines are organised as ‘checkpoints’ each with different priority levels of 1, 2 and 3.
- 2.X: Defined guidelines based around four design principles, with each princible including testable success criteria at different conformance levels:
- A - This level is generally described as a must do as a bare minimum level of conformance.
- AA - This level is generally desribed as a should do as a standard level of conformance.
- AAA - This level is generally a nice to have but cannot always be achieved as it focusses on enhanced requirements for visual contrast and sign/audio descriptions, primarily for video based media
A realistic aim for most web applications is WCAG 2.2 AA. This level of conformance achieves meaningful accessability to most users, without being too disruptive to the design and development process of an asset. For more detailed guides on conformance levels, click here.
How can I conform to WCAG 2.2 AA guidelines?
Comprehensive WCAG guidance
Web accessibility criteria can be grouped into four topics, known as the POUR principles:
- Percievable - Can users identify the elements of the website, with sight or hearing
- Operable - Can users control the webpage elements, e.g. controls, menus, buttons, navigation
- Understandable - Can users comprehend the content to use the website
- Robust - Can users reliably interpret the website with a chosen assistive technology, e.g. screen reader
The above principles are achieved by adhering to all criteria defined by W3C:
The criteria checklist above covers every aspect of WCAG conformance, however some web resourses listed below can be used as an alternative criteria which include filters and settings to more easily evaluate and manage WCAG criteria:
Convertr specific guidance
Asset types which require accessibility conformance:
The assets that you create in Convertr will often not require certain criteria because they are not applicable, for example:
- When creating an email asset, the criteria for video related guidelines are not relevant because video cannot be embeded onto an email asset.
- When creating a form, the criteria for menu/navigation related guidelines are not relevant because forms do not contain links to different pages of a website.
The below guidance can be used as a starting point for meeting WCAG guidelines for assets created within Convertr. However, the guidance mentioned in the Comprehensive WCAG guidance should be used to fully meet WCAG conformance.
Email Assets | Display Assets | Forms | Hosted Landing Page | Template Landing Page | |
---|---|---|---|---|---|
ContrastCriteria Text, visual elements, and interactive elements must have strong contrast against the background the element it is placed on. This could be the page background, an image or pattern. Providing enough contrast between the foreground and background enables readability for sighted individuals. Black on a white background would be considered as the best contrast. WCAG recommends a contrast ratio of 4.5:1 for regular text, and 3:1 for large text. Example The text of a paragraph should be easily legible on the background colour of the page. How to test The Emulate Vision Deficiencies feature in Chrome DevTools can help identify vision deficiencies experience your web app. Alternatively, a colour contrast checker can be used. |
✔ |
✔ |
✔ |
✔ |
✔ |
ColourCriteria Color should not be the only visual means of distinguishing a visual element. Any information conveyed by color should also be available in text. Pairing color with another indicator aims to ensure that sighted individuals who cannot distinguish between some colors can still understand the content. Example On a form, a required field can have typically red styling such as red background or red border, but it should also include a text to easily identify this required field, e.g. 'Field is required' How to test Check any use of colour for statuses, success, failure, warnings, etc. should have accompanying text to explain the meaning of the colour used. |
✔ |
✔ |
✔ |
✔ |
✔ |
Alternative TextCriteria Alternative text (alt text) is required for all visuals that provide meaningful information, such as images, graphs, and charts. Descriptive alt text explains the image to provide a similar experience to that of a sighted individual. Images used solely for decoration should be given an empty alt tag. Example A company logo used on a landing page or email should have alt text of the company name. How to test Hide any images or media in your asset and check the alt text informatively describes the item that is being hidden. |
✔ |
N/A |
✔ |
✔ |
✔ |
Heading StylesCriteria Heading styles designate content organization. Using headings indicates the hierarchy of content. Predefined style headings in text editors enable clear understanding of the structure of the document or web page. Headings should be in sequential order and that they do not skip a level. Example A page title should use <h1> HTML tags and subtitles should use subsequest heading types in order, i.e. <h2>, <h3>, etc. How to test Heading tag checkers can be used to ensure correct ordering of headings. |
✔ |
N/A |
✔ |
✔ |
✔ |
List StylesCriteria Use bulleted or numbered list styles to denote list structure. This ensures consistent formatting and helps screen readers understand the content structure and organization. Example A list should use <ul><li> HTML tags for unordered lists and <ol><li> HTML tags for ordered lists. Nested lists can use a combination of both. How to test Check any lists are using correct HTML tags. |
✔ |
N/A |
✔ |
✔ |
✔ |
LinksCriteria The purpose links can be determined from the link text alone or adjacent surrounding link text. Link text like 'click here' does not provide context to understand where the link is going unless surround text explains the action. Example Link text for a registration form could be 'sign up to attend the event'. Alternatively, supplementary text can be used which could be 'sign up to the event by clicking here'. How to test Check any links have meaningful and descriptive text. |
✔ |
✔ |
✔ |
✔ |
✔ |
TablesCriteria Format and use simple tables with column and row headers. Split nested tables up into simple tables, and do not use tables to control layout. Example HTML table syntax should be used systematically with <table>, <th> and <tr> tags. How to test Check syntax for tables is correct according to checklists. |
✔ |
N/A |
✔ |
✔ |
✔ |
Audio and VideoCriteria Audio content should have a full transcript. Video content should have accurate captions, and an audio description that describes the visual information of the video. Example Videos should have subtitles/captions to aid users with visual impairments to understand the content being played. How to test Check audio and video media have alternative means to understand content. |
✔ |
N/A |
✔ |
✔ |
✔ |
Movement, Animation, FlashingCriteria Moving, blinking, or scrolling information that starts automatically, lasts more than five seconds, and is presented in parallel with other content, provide a mechanism to pause, stop, or hide it. Check that content does not contain anything that flashes more than three times in a one second period. Example An animation/gif that automatically plays and loops on a page, or a loading spinner, or a blinker for a cursor. How to test Ensure a mechanism is in place to pause, stop or hide the item. |
✔ |
✔ |
✔ |
✔ |
✔ |
Shape, Size, PositionCriteria Descriptions of content should not rely on solely on references to shape, size, or position. Additional information should be included in any instructions that allows individuals to understand them even if they cannot perceive shape, size, or position. Example A multipage interface should not have just a right arrow to proceed to the next step, there should be the word 'Next' to accompany the arrow. How to test Any instructions should not rely on shapes, size or position to describe an action. |
✔ |
✔ |
✔ |
✔ |
✔ |
Keyboard NavigationCriteria Content should be accessible without using a mouse. The tab key is typically used to navigate the interactive elements of a web page. The enter key, the spacebar, and the arrow keys are also commonly used where 'focus' and 'active' HTML states indicate the item that is being selected. Example Using the 'tab' key to navigate a form should highlight the inputs that are being focused on and ready for interaction, where the final 'submit' button should have a visual indicator when focused such as a border. How to test Disable mouse/trackpage and navigate the asset with just a keyboard, ensuring the focus order is intuitive and follows the structure of the page |
✔ |
N/A |
✔ |
✔ |
✔ |
Resize TextCriteria Information and functionality should not be lost when resizing text from 100% up to 200%. Resizing text must be achieved without the use of assistive technology, like a screen magnifier that increases the size of all content, or the zoom function in a browser. One example is to Example When zooming into a web page, the content should automatically adjust it's layout to ensure all content is visibile. How to test Resize the page zoom to 200% via browser functions and check that there is no missing or overlapping content, and that horizontal scrolling is not required. |
✔ |
✔ |
✔ |
✔ |
✔ |
How can I check my assets are meeting WCAG guidelines?
WCAG are not a legal requirement for private sector businesses, but it is an expected standard to make the web inclusive for everyone.
Paid accessibility audit services are avilable (primarily utilised by public sector businesses), however WCAG adherance for private sector industries is typically achieved by self-evaluation.
Recommended tools and guidance: