WCAG 2.4.5: Multiple Ways

Codebase commit: 1.9 RC1 c068fb3d8
Result: pending

Resources

WCAG 2.2 Success Criterion

More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.

Audit Checklist

• Review previous Audit Result
• Review work identified in previous audit and list open issues.
• Check for any other relevant open issues.
• Retest open issues, are these issues still present?
• Test for any new issues that may have been introduced.
• Determine compliance status, add this to issue name.
• Add any new issues to the Accessibility project for triage.

Previous audit

#5150

🟠 Partially Supports

✅ Articles are supported. They can be reached via the articles page (which includes the search) and via the issue in which they appeared. If keyword linking is turned on for that journal, then the keywords for each article link to a list of other articles with the same keyword. Articles that are part of special collections can also be reached via their collection.

🟠 News items are partially supported. All news is reachable via the news page. News items have optional tags, and these are links to other items with the same tag, however news items could have no tags at all, or have a tag that is unique.

❌ Static pages are not supported. They are reachable via the navigation and some may be linked from the contents of the homepage, but that is configurable by journal. Some could cross-reference each other via links, but that would be in the user-content.

The sitemaps should have provided the second way for all missing support above, but are themselves not working as expected (see tests below) and so cannot be relied upon.

Progress since last audit

Work identified in last audit

• https://github.com/openlibhums/janeway/issues/5170

Audit Notes

There are four categories of pages within Janeway.

1. publications (e.g. articles, issues, preprints, collections)
2. news items
3. static built-in (e.g. search pages, contact us, accessibility, homepage, sitemaps)
4. static user-managed (the CMS pages which users create)

Taking these one by one.

1. ✅ publications - once published these are reachable via the navigation in multiple ways, as previously described in the last audit. These pages were already compliant.
2. ✅ news - similar to publications, these were previously all reachable via the navigation, however whether they were reachable in a second way depended on whether they were tagged. This was user content, and not within our control. Adding news items to the sitemaps provides a second way for each to be reached, and so news pages are now compliant.
3. ✅ static built-in pages - These are navigable from the navigation or the footer. Previously these were not reliably included in the sitemaps. The updated sitemap generation includes them.
4. ✅ static CMS pages - These were not included in sitemaps previously and so were only reachable via user-entered in-page links or the user adding them to the navigation. It would have been possible for a user to have ensured all had more than one way to reach them, however there was nothing in Janeway to facilitate this. CMS pages may now be draft or published. Investigation found that users had been creating drafts by publishing pages and not linking to them, which on installs with a large number of CMS pages made it difficult to keep track of what was meant to be reached by users and what should not. Now it is clear which are draft and which are published so the users should be clear about which pages to include in navigation. All published CMS pages are added to the sitemaps automatically.

All that remains is to check the sitemaps generator is doing what it claims.

Conclusion

Work arising