Accessibility Audit
Project Background
1 Site wide findings
2 Content
- 2.1 Embedded videos do not use audio descriptions or text transcripts (H)
  - 2.1.1 WCAG 1.2.3 (A) - Desktop
  - 2.1.2 Recommendation
- 2.2 Inconsistent identification of accordion elements (M)
  - 2.2.1 WCAG 3.2.3 (AA), 3.2.4 (AA) - Desktop, Mobile, iPad
  - 2.2.2 Recommendation
3 Generic
4 Landing
- 4.1 Text is obscured when text spacing is applied (H)
  - 4.1.1 WCAG 1.4.12 (AA) - Desktop
  - 4.1.2 Recommendation
- 4.2 Two elements receive focus (L)
  - 4.2.1 WCAG 2.4.7 (AA), 4.1.1 (A) - iPhone
  - 4.2.2 Recommendation
5 Research
- 5.1 Text is obscured when text spacing is applied (H)
  - 5.1.1 WCAG 1.4.12 (AA) - Desktop
  - 5.1.2 Recommendation
- 5.2 Inconsistent identification of accordion elements (M)
  - 5.2.1 WCAG 3.2.3 (AA), 3.2.4 (AA) - Desktop, Mobile, iPad
  - 5.2.2 Recommendation
6 Intranet landing page
7 Intranet content page
8 Undergraduate course page
9 Postgraduate course page
10 News article
11 Staff profile
- 11.1 Article information is not associated to the relevant article (H)
  - 11.1.1 WCAG 1.3.1 (A), 2.4.4 (A) - Desktop, Mobile, iPad
  - 11.1.2 Recommendation
12 Homepage
13 High Traffic page 1
14 High Traffic page 2
15 Timetables
16 Registration form
17 Micro site
- 17.1 Link URL is announced by screen reader (H)
  - 17.1.1 WCAG 2.4.4 (A) - Desktop
  - 17.1.2 Recommendation
I Recommendations
18 Suggested Next Steps
APPENDIX
A Automated Findings
Contact Details

Prepared by User Vision for LJMU

UV2635- Liverpool John Moores University Accessibility Audit

14.3 Dynamic content not announced by screen reader (H)

FIGURE 14.6: search field highlighted on the Search courses page

14.3.1 WCAG 4.1.3 (AA) - Desktop, Mobile, iPad

When the user enters a keyboard into the search field on the Search Courses page, the page dynamically updates with the search results. This information is not announced by screen reader.

Blind and low vision users need to be informed of changes happening on screen as they have no visual frame of reference and require up to date information in order to make informed decisions.

14.3.2 Recommendation

Depending on the context and importance of the dynamic content on screen, the information can be indicated by using aria live regions setting aria-live=‘assertive’, aria-live="polite" or role=“alert”. The purpose of this ARIA content is to notify assistive technologies that a change has occurred and not have users assume that the form is not functioning correctly.

In this instance, aria-live="polite" is recommended as it will notify users of updates but generally won’t interrupt the current task. For reference both role=alert and assertive will immediately notify the user, and could potentially clear the speech queue of previous updates.