Accessibility
Firely Accessibility Conformance Report - WCAG Edition
(Based on VPAT® Version 2.5)
Name of Product/Version: Simplifier.net
Report Date: 25-09-2024
Product Description: Simplifier.net by Firely is an online platform for collaborating and publishing the artifacts from FHIR specifications.
Contact Information: Please contact simplifier@fire.ly with any questions or suggestions for improvements.
Notes
General notes
Simplifier.net is a platform for user-generated content. While we do our best to facilitate our users in creating accessible content, the flexibility of the platform requires users to check their own generated content for accessibility.
The tree rendering of FHIR resources can be navigated by keyboard when Javascript is enabled:
Tab until the full tree is selected.
Then navigate the three rows with the up and down arrows. When using a screen reader this can be done after ‘Scan mode’ is turned off.
Tree nodes can be opened/collapsed by selecting the node and pressing Space bar or Enter.
The Details page on a resource and dictionary rendering in an Implementation Guide provide static alternatives.
The Monaco Editor which is embedded in many places on the site provides powerful accessibility features and a dedicated menu which is highlighted when using a screen reader. More information can be found in the Monaco Editor Accessibility Guide.
Changelog
Nov 30, 2020: First edition published.
Dec 22, 2020: Accessibility scan completed and major issues resolved.
Sep 25, 2024: Second edition published.
Evaluation Methods Used
Testing based on general product knowledge
Testing with assistive technologies with Google Chrome/Microsoft Edge on Windows
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline |
Included In Report |
---|---|
Level A: Yes Level AA: Yes Level AAA: No |
|
Level A: Yes Level AA: Yes Level AAA: No |
|
Level A: Yes Level AA: Yes Level AAA: No |
Terms
The terms used in the Conformance Level information are defined as follows:
Supports : The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports : Some functionality of the product does not meet the criterion.
Does Not Support : The majority of product functionality does not meet the criterion.
Not Applicable : The criterion is not relevant to the product.
Not Evaluated : The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
Scope
Tests were executed with the following pages, taken as representative for the full application:
Id |
Web Page / Screen / Document Identifier |
Location / URL |
---|---|---|
1 |
Implementation Guide |
https://simplifier.net/guide/accessibilitytestingimplementationguide |
1.1 |
|
https://simplifier.net/guide/AccessibilitytestingImplementationGuide/Home |
1.2 |
|
https://simplifier.net/guide/accessibilitytestingimplementationguide/staticmarkdownpage |
1.3 |
|
https://simplifier.net/guide/accessibilitytestingimplementationguide/pagewithanembeddedresource |
2 |
Resource page |
https://simplifier.net/Accessibilitytestingproject/ACMEbasePatient |
2.1 |
|
https://simplifier.net/Accessibilitytestingproject/ACMEbasePatient/~overview |
3 |
Home page |
|
4 |
Organization page |
|
5 |
Project page |
|
6 |
Package page |
https://simplifier.net/packages/firely.com.accessibilitytesting/0.0.1-test/~introduction |
7 |
Validation page |
|
8 |
Search page |
|
9 |
Snippet page |
|
10 |
Documentation page |
|
11 |
Sign up page |
|
12 |
Upload file page |
|
13 |
Upload snippet page |
|
14 |
Jurisdiction page |
|
15 |
News page |
WCAG 2.x Report
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
Table 1: Success Criteria, Level A
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
(Level A) |
Partially supports |
Known issues
|
1.2.1 Audio-only and Video-only (Level A) |
Supports |
No pre recorded audio. Video from youtube.com contains subtitles that is a text alternative. |
(Level A) |
Supports |
Video from youtube.com contains subtitles. |
1.2.3 Audio Description or Media Alternative (Level A) |
Supports |
Video from youtube.com contains subtitles. |
(Level A) |
Partially Supports |
Known issues
|
(Level A) |
Supports |
Meaningful order of elements is reflected in programmatic page structure. |
(Level A) |
Supports |
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. |
(Level A) |
Supports |
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
(Level A) |
Supports |
Audio of videos from youtube.com can be controlled |
(Level A) |
Partially Supports |
For keyboard navigation in the FHIR resource tree and the embedded Monaco code editors, see general notes above. Known issues
|
(Level A) |
Partially Supports |
On tab trapping in the embedded Monaco code editors, see general note above. Known issues
|
(Level A 2.1 only) |
Supports |
No keyboard shortcuts are used, except in Monaco code editor, which provides its own accessibility menu and options. |
(Level A) |
Supports |
No timings are used. |
(Level A) |
Supports |
All scrolling, moving content (for example the log output from file import or package generation) are started based on user input and pause at the end for review. |
2.3.1 Three Flashes or Below Threshold (Level A) |
Supports |
No flashing content is used. |
(Level A) |
Supports |
Known issues
|
(Level A) |
Supports |
Known issues
|
(Level A) |
Supports |
Known issues
|
2.4.4 Link Purpose (In Context) (Level A) |
Partially Supports |
Known issues:
|
(Level A 2.1 only) |
Partially Supports |
Known issues:
|
(Level A 2.1 only) |
Supports |
No actions are executed on mouse down event. |
(Level A 2.1 only) |
Partially Supports |
Known issues:
|
(Level A 2.1 only) |
Supports |
No motion is used. |
(Level A) |
Supports |
The default human language is identified by the lang attribute on the html element. |
(Level A) |
Supports |
No change of context is executed when changing focus. |
(Level A) |
Supports |
No change of context is executed when changing input, without user actuation. |
(Level A 2.2 only) |
Supports |
Feedback button exists at the top navigation bar on every page and on entering the details, a support person can get in touch with the user. |
(Level 2.2 only) |
Supports |
Redundant information is not asked in any pages. Exception is only in Change Password page and this exception is allowed as per Success criteria. |
(Level A) |
Partially Supports |
Known issues
|
(Level A) |
Partially Supports |
Known issues:
|
(Level A) |
Partially Supports |
Known issues
|
(Level A) |
Partially Supports |
Known issues
|
Table 2: Success Criteria, Level AA
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
(Level AA) |
Supports |
No (live) audio used. |
1.2.5 Audio Description (Prerecorded) (Level AA) |
Supports |
Videos from youtube.com have subtitles that can be used as audio description. |
(Level AA 2.1 only) |
Supports |
Site does not fixate a particular screen orientation. |
(Level AA 2.1 only) |
Partially Supports |
Known issues
|
(Level AA) |
Partially Supports |
On contrast in the embedded Monaco code editors, see general note above. Contrast issues in website main content will be addressed in upcoming change of website colors. |
(Level AA) |
Supports |
No loss of function at 200% zoom level. |
(Level AA) |
Supports |
No images of text are used. |
(Level AA 2.1 only) |
Supports |
Even in small view ports website reflows and content is still accessible. |
(Level AA 2.1 only) |
Supports |
Images not used as replacement for user interface components or for required understanding. |
(Level AA 2.1 only) |
Supports |
No loss of function found with large fonts, line height and spacing. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only) |
Supports |
Note: For seeing the content that appears in the resource tree-rendering on mouse over, click the element to make it persistent and not disappear on removal of mouse focus. |
(Level AA) |
Supports |
All user content on Simplifier.net is reachable via Search and direct navigation via owning organization/project/packages. Implementation Guides have support for providing a Table of Contents of all pages. |
(Level AA) |
Partially Supports |
Known issues
|
(Level AA) |
Supports |
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. |
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) |
Partially Supports |
Known issues
|
(Level AA 2.2 only) |
Partially Supports |
Known Issues:
|
(Level AA 2.2 only) |
Supports |
|
(Level AA) |
Supports |
Website is only provided in English, which is indicated as page language. Note: User defined text currently has no way to deviate from English language. This will be done later when support for IG translation is added. |
(Level AA) |
Supports |
The menu is provided consistently throughout the site. Exceptions:
|
3.2.4 Consistent Identification (Level AA) |
Supports |
Components that have the same functionality within a set of Web pages are identified consistently. |
(Level AA) |
Supports |
Where solutions to possible errors are known the site tries to prevent you from making them beforehand. Examples: Providing dropdowns of possible values or automatically fixing duplicate URLs. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) |
Supports |
No financial transactions, legal transactions or test results are handled. All data delete operations require an extra confirmation step. |
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) |
Supports |
Sign up page displays an object that needs to be dragged into a position to solve the puzzle and a mechanism exists with instructions to assist the user. |
(Level AA 2.1 only) |
Supports |
There where status is conveyed by graphical elements, like a progress bar, the status is programmatically available to the user agent. |