-
Notifications
You must be signed in to change notification settings - Fork 7
Accessibility report (24 June 2022): Sample judgment text
This report has been prepared in support of the sprint task to review Judgment HTML and formatting. It describes the conformance of a sample judgment with W3C’s Web Content Accessibility Guidelines (WCAG).
The review process is described in Section 5 below and is based on evaluation described in Accessibility Evaluation Resources.
Based on this evaluation, the page does not meet WCAG 2.1, Conformance Level AA. Detailed review results are available in Section 6 below. Resources for follow-up study are listed in Section 7 below. Feedback on this evaluation is welcome.
Conformance evaluation of web accessibility requires a combination of semi-automated evaluation tools and manual evaluation by an experienced reviewer. The evaluation results in this report are based on evaluation conducted on 24 June 2022. The page may have changed since that time.
A single sample judgment was included in this review: Advanced Bionics AG &; Anor. v Med-El Elektromedizinische Gerate GMBH. This judgment was provided by the Editorial Team as representing one of the more structurally complex examples.
This is a basic evaluation against the 50 WCAG 2.1 AA Success Criteria using a single web browser (Safari 14.0.3) and VoiceOver. A fuller evaluation against the web browsers and assistive technologies specified in the Service Manual is necessary.
The review was conducted by Gwyn Jones, Lead Frontend Developer, using the WCAG-EM report tool and based on the Web Content Accessibility Guidelines Evaluation Methodology.
The page was reviewed against all 50 WCAG 2.1 A and AA Success Criteria:
- 19 Passed
- 7 Failed (4 at Level A, 3 at Level AA)
- 0 Cannot tell
- 24 Not present
- 0 Not checked
** 1.1.1 Non-Text Content **
W3C describe the intent of 1.1.1 as:
The intent of this Success Criterion is to make information conveyed by non-text content accessible through the use of a text alternative. Text alternatives are a primary way for making information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. Providing text alternatives allows the information to be rendered in a variety of ways by a variety of user agents. For example, a person who cannot see a picture can have the text alternative read aloud using synthesized speech.
This Success Criterion was failed because 38 of the images included in the page do not have a text alternative.
Those images that do not have a text alternative are informative (rather than decorative) and there are many instances where the image might be required to understand related text. For example:
"The diagram below shows these cylinder magnets in the housing and the different axis of rotation."
Not present
Not present
Not present
Not present
Not present
W3C describe the intent of 1.3.1 as
The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For example, the presentation format changes when the content is read by a screen reader or when a user style sheet is substituted for the style sheet provided by the author. Sighted users perceive structure and relationships through various visual cues — headings are often in a larger, bold font separated from paragraphs by blank lines; list items are preceded by a bullet and perhaps indented; paragraphs are separated by a blank line; items that share a common characteristic are organized into tabular rows and columns; form fields may be positioned as groups that share text labels; a different background color may be used to indicate that several items are related to each other; words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them; items that share a common characteristic are organized into a table where the relationship of cells sharing the same row or column and the relationship of each cell to its row and/or column header are necessary for understanding; and so on. Having these structures and these relationships programmatically determined or available in text ensures that information important for comprehension will be perceivable to all.
This Success Criterion was failed for multiple reasons. These include:
- using changes in text presentation (including bold, underline and italic) to convey information without using the appropriate markup or text (https://www.w3.org/WAI/WCAG21/Techniques/failures/F2)
- using structural markup in a way that does not represent relationships in the content. For example, there are paragraphs styled to look like headings, lists and quotes. (https://www.w3.org/WAI/WCAG21/Techniques/failures/F43)
- not correctly marking up table headers by including headers in table data cells (https://www.w3.org/WAI/WCAG21/Techniques/failures/F91).
W3C describe the intent of 1.3.1 as:
The intent of this Success Criterion is to enable a user agent to provide an alternative presentation of content while preserving the reading order needed to understand the meaning. It is important that it be possible to programmatically determine at least one sequence of the content that makes sense. Content that does not meet this Success Criterion may confuse or disorient users when assistive technology reads the content in the wrong order, or when alternate style sheets or other formatting changes are applied.
This success criterion was failed because a HTML table is used for layout in the judgment header but the content does not make sense when linearised because the order of items is switched (https://www.w3.org/WAI/WCAG21/Techniques/failures/F49)
Passed
Passed
Not present
W3C describe the intent of 1.4.1 as:
The intent of this Success Criterion is to ensure that all sighted users can access information that is conveyed by color differences, that is, by the use of color where each color has a meaning assigned to it. If the information is conveyed through color differences in an image (or other non-text format), the color may not be seen by users with color deficiencies. In this case, providing the information conveyed with color through another visual means ensures users who cannot see color can still perceive the information.
This Success Criterion was failed because multiple diagrams use colour as the only visual means of conveying information.
Not present
Passed
Passed
W3C describe the intent of 1.4.5 as:
The intent of this Success Criterion is to encourage authors, who are using technologies which are capable of achieving their desired default visual presentation, to enable people who require a particular visual presentation of text to be able to adjust the text presentation as needed. This includes people who require the text in a particular font size, foreground and background color, font family, line spacing or alignment.
This Success Criterion was failed because there are multiple examples where text has been embedded in images
W3C describe the intent of 1.4.10 as
The intent of this Success Criterion is to support people with low vision who need to enlarge text and read it in a single column. When the browser zoom is used to scale content to 400%, it reflows - i.e., it is presented in one column so that scrolling in more than one direction is not necessary. For people with low vision, enlarged text with reflow enables reading. It is critical. Enlargement enables perception of characters. Reflow enables tracking. Tracking is following along lines of text, including getting from the end of one line to the beginning of the next line.
This Success Criterion was failed because scrolling in multiple directions is necessary
W3C describe the intent of 1.4.11 as:
The intent of this Success Criterion is to ensure that active user interface components (i.e., controls) and meaningful graphics are distinguishable by people with moderately low vision.
This Success Criterion was failed because multiple diagrams within the judgment do not achieve a 3:1 contrast ratio
Passed
Not present
Passed
Passed
Not present
Not present
Not present
Not present
Passed
Passed
Passed
Passed
Not present
Passed. It is worth noting that the only headings on the page are in the footer. Other than these headings there is no heading structure to the page.
Passed
Not present
Not present
Not present
Not present
Passed
Not present