Written Language and Content Elements Testing
A content and written language audit looks at all of the on-page content.
Everything that provides meaning on the page needs to be tested and the number of content types and content volume heavily influence how thorough testing must be.
To dive a little deeper, we look at the following in content testing:
- Headings - to ensure a good heading structure. The H1 should describe what the page is about and only used once, other remaining headings are meaningful based on their level, not size, headings describe content that follows and no heading levels are skipped.
- Text - to make sure it is readable, grammatically correct, and accurately provides meaning. Try to avoid jargon in your content.
- Text Links - to ensure users are able to navigate to and select each link using the keyboard alone. We ensure they are linked to the correct page or content and provide accurate link descriptions for screen readers.
- Graphics - to ensure graphics are not used as the only way of conveying meaning, accurate and descriptive alternate text is added to images, enlarged (zoomed) images of text do not become pixelated and difficult to read, graphics conveying meaning or content such as a map do not rely solely on colour and meet colour contrast requirements and ensure flashing images and multimedia do not cause seizures. .
- Video and Audio - to ensure videos have subtitles and closed captions, audio jas a transcript and video or audio does not auto-play
- Tables and Graphs - to ensure they are easily understandable and information is structured correctly.
Forms - to ensure that suitable information and notifications are added to aid for completion and provide content for validation errors.
The most important concept for web content testing is that content is structured and designed to be 'Perceivable', 'Operable', 'Understandable' and 'Robust' in order to meet the WCAG 2.1 guidelines.
Front-End Code Testing
A 'Front-End Code Audit' investigates the front-end code of a platform to ensure valid and semantic HTML. This is essential to identify any issues or inconsistencies may lay that will influence how disabled or disadvantaged individuals may use a platform. Front-end code audits are best completed with a mix of automated tools and manual investigation.
How the front-end code has been written, structured, and integrated can heavily affect how effective assistive technologies are. Front-end issues can also limit on-page user interactions and may create barriers with how users can and will engage with different action items on your page.
To dive a little deeper, we look at the following in user Front-End Code testing:
- Keyboard Navigation - to ensure all functionality works by using the keyboard only. The only way to test this is manually.
- W3C Validation - to ensure the code is error free e.g. no duplicated ID’s
- WCAG 2.0 Validation - to ensure the generated DOM adheres to WCAG 2.0 requirements
- Dynamic Content - to ensure all dynamic content changes are announced for screen readers. The best way to test this is manually.
User Interface Testing
User interface testing is super important as it investigates the quality of interaction, ease of use, visual/graphic representation, reactivity and interactivity that a creative design and user interface has.
By investigating specific UI elements, we can identify key issues in these aspects that target accessibility improvements for users with blindness, low vision, deafness, mobility or cognitive impairments.
To dive a little deeper, we look at the following in user interface / design testing:
- Colour Contrast - to ensure all elements adhere to WCAG 2.0 colour contrast requirements
- Not by colour alone - to ensure colour isn’t the only method for conveying meaning or content
- Not by icon alone - to ensure icons are not the only method for conveying meaning or content. Items must be labelled correctly
- Typography Formatting - to ensure text font is legible and adheres to WCAG 2.0 text-spacing requirements
- Page / Feature Structure - to ensure logical layout and relationships between page/feature elements and to ensure the avoidance of using too many elements on a page that may distract the user from reading the text or using the navigation.
- Focus Styles - to ensure all interactive/focusable items have a visible focus indicator
Assistive Technology Compatibility Testing
Many users with disabilities are not able to use computers and mobile devices with a keyboard and mouse or with swipes and taps. Many users rely on integrated softwares to support how they use and interact with digital platforms.
Within this testing section we use screen-reader technologies such as NVDA, Apple Voiceover or ChromeVox to see whether pages can be understood and navigated using just vocals, text-to-speech output, or a Braille display.
Manual testing of assistive technology compatibility is a must to identify front-end code and structural issues.
UX Interviews / Focus Groups
For those that are looking to get the best accessibility results, we always recommend to engage real user groups in accessibility testing. UX interviews and focus groups allow us to gather first hand information on how different user groups are interacting with a certain platform or page, and what positive and negative accessibility experiences they may be having.
As commonly known in UX design and Design Thinking methodology, user testing during planning, design, development, and implementation phases is most important for successful digital design results. The same goes for accessibility.
Engaging users first-hand will always give you a greater understanding and insight into the experiences and impact that your digital platform or website delivers.
Outcomes for your business
With a professional web accessibility report you will get the output and outcomes that match your initial business requirements. You will get the option to choose from:
- Accessibility Compliance Checklist - A simple "Pass / Fail" checklist for all tested elements' compliance with WCAG 2.1 requirements.
- Accessibility Detailed Findings Report - A "Pass / Fail" grade for all primary components of the WCAG 2.1 guidelines and a detailed report of where each non-compliant aspect was found through each page or page type.
- Accessibility Findings and Recommendations Report - An extremely thorough report outlining a "Pass / Fail" grade for the primary component of the WCAG 2.1 guidelines across each page and page type tested, along with detailed recommendations on how to fix each and every accessibility issue identified.
- Accessibility Findings Presentation - In addition to the report of your choice, Internetrix can provide an accessibility findings presentation to summarise key issues and recommendations to a wider internal company stakeholder audience.