Accessibility
Air Medical Safety Network Accessibility Conformance Report
WCAG Edition. Based on VPAT® Version 2.5Rev.
- Name of product and version
- airmedsafety.org, as published November 2, 2026
- Report date
- Product description
- The public website of the Air Medical Safety Network, a volunteer-led network that brings together researchers, operators, and providers to develop applied research on operational and clinical safety in air medical transport. The site includes the Evidence Library, Journal Directory, Accident Database, Regulatory Record, Research Questions, Research Opportunities, Air Medical Learning Network, Working Groups, and the CONCERN Network history.
- Contact information
- admin@airmedsafety.org
- Notes
- In scope: All public pages linked from the site navigation and footer, their forms and confirmation pages, the Accident Database after sign-in, and the Working Groups member area. Out of scope: Administrator pages, unlinked preview and review pages, email messages, and outside sites the site links to, including journal publishers, Google reCAPTCHA, LinkedIn, and Facebook. Next review: May 2027.
- Evaluation methods used
- Automated testing of every in-scope page with axe-core 4.14, using the WCAG 2.0, 2.1, and 2.2 Level A and AA rule sets, in Chrome at 1280 pixels wide.
- Keyboard-only testing of every interactive component, including the Accident Database with its data loaded.
- Reflow testing at 320 CSS pixels wide.
- Text spacing testing with the WCAG 1.4.12 spacing values applied.
- Contrast testing of text, focus indicators, and form field boundaries.
- Target size measurement of links, buttons, and form controls.
- Review of page code for labels, roles, states, focus handling, and status messages.
- Screen reader testing has not yet been done. It is planned for the next review.
Applicable standards and guidelines
| Standard or guideline | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes), Level AA (Yes), Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes), Level AA (Yes), Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes), Level AA (Yes), Level AAA (No) |
Terms
- 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 only be used in WCAG Level AAA criteria.
WCAG 2.x report
Success criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology, as documented in the WCAG 2.0 conformance requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Images have text alternatives or are marked as decorative. Charts have text summaries. The Accident Database year chart is followed by a data table for screen readers, and each year bar on the home page has a text label. Forms use Google reCAPTCHA, which offers an audio alternative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The site has no prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | The site has no prerecorded video with audio. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | The site has no prerecorded video. |
| 1.3.1 Info and Relationships (Level A) | Supports | Pages use headings, lists, landmarks, labeled form fields, grouped choices, and data tables with header cells. Sortable table headers report their sort order. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | Reading order matches the visual order. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Instructions do not rely on shape, size, position, or sound alone. |
| 1.4.1 Use of Color (Level A) | Supports | Selected filters show their state in text and in code, not by color alone. Fatal events shown in a darker color in charts are also reported in text and in data tables. |
| 1.4.2 Audio Control (Level A) | Not Applicable | The site plays no audio. |
| 2.1.1 Keyboard (Level A) | Supports | All functions work with a keyboard. In the Accident Database, record rows, column sorting, chart filters, and view tabs work by keyboard. Map points and state tiles respond to a pointer. The same records open from the Records view, and the same state filter is in the filter panel, both by keyboard. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus can always move away from any component. Dialogs keep focus inside while open and close with Escape or the Close button. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Not Applicable | The site has no single-character keyboard shortcuts. |
| 2.2.1 Timing Adjustable (Level A) | Supports | Pages have no time limits. Emailed sign-in links for Working Groups expire after 30 minutes for security. A new link can be requested at any time without losing work. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | No content moves, blinks, or scrolls on its own for more than five seconds. Animations run once and respect the reduced motion setting. Working Groups discussions check for new replies every 20 seconds, announce them, and do not update while a person is typing. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | No content flashes. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Every page has a skip link to the main content and uses landmarks. |
| 2.4.2 Page Titled (Level A) | Supports | Every page has a descriptive title. The Working Groups title changes with each view. |
| 2.4.3 Focus Order (Level A) | Supports | Focus order follows the page layout. Dialogs move focus in when they open and return it when they close. In Working Groups, focus moves to the heading of each new view. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Link text, alone or with its sentence or list item, describes where the link goes. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Supports | The Regulatory Record timeline can be dragged. It can also be moved with Earlier and Later buttons and with arrow keys. No feature needs a path-based or multipoint gesture. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Supports | Actions run when the pointer is released, not when it is pressed. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Supports | Accessible names include the visible label text. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Not Applicable | No feature responds to device motion. |
| 3.1.1 Language of Page (Level A) | Supports | Every page declares English as its language. |
| 3.2.1 On Focus (Level A) | Supports | Moving focus never changes the page or opens a new window. Tooltips appear on focus without changing context. |
| 3.2.2 On Input (Level A) | Supports | Changing a filter or setting updates results in place. It does not navigate away or submit a form. |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | Links to the Questions page and to Privacy and data use, which gives the contact address, appear in the same footer order on every page. |
| 3.3.1 Error Identification (Level A) | Supports | Missing or invalid entries are identified in text, by the browser or in a message next to the form. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Every field has a visible label. Optional fields are marked. Fields that need a format explain it. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | No process asks for the same information twice. |
| 4.1.1 Parsing (Level A 2.0 and 2.1) | Supports | This criterion is obsolete in WCAG 2.2 and is always satisfied. It is reported here for WCAG 2.0 and 2.1. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Native controls are used where possible. Custom toggles report pressed state, tabs use tab roles, menus and disclosures report expanded state, and dialogs have a role and a name. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | The site has no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | The site has no prerecorded video. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | Supports | Pages work in portrait and landscape. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Supports | Name, email, organization, and role fields identify their purpose for autofill. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text meets 4.5:1, or 3:1 for large text. Four contrast problems found in this review were corrected. |
| 1.4.4 Resize Text (Level AA) | Supports | Text can be enlarged to 200 percent without loss of content or function. |
| 1.4.5 Images of Text (Level AA) | Supports | The only image of text is the network's wordmark, which is a logo. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Supports | Content reflows at 320 CSS pixels wide without scrolling sideways. Data tables, the Regulatory Record timeline, the CONCERN history timeline, and the Accident Database map need a two-dimensional layout and scroll within their own area. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Supports | Focus indicators and form field borders meet 3:1. The focus ring is 3 pixels wide. Form field borders were darkened in this review to meet 3:1. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | No content or function is lost with increased text spacing. Some long titles in compact lists are shortened with an ellipsis, and the full title is shown when the item is opened. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Supports | Tooltips open on hover and on focus, stay open while the pointer is over them, and close with Escape. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Pages can be reached from the main navigation, the Resources menu, the home page, and links within pages. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | Every focusable element shows a visible focus indicator. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | The sticky header does not cover focused items. Pages reserve space under the header when scrolling to a focused item. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Supports | The Regulatory Record timeline can be dragged, and has Earlier and Later buttons and arrow keys as single-pointer alternatives. No other feature uses dragging. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Partially Supports | Links, buttons, and form controls are at least 24 by 24 pixels or have enough space around them. Exception: the year bars in the Evidence Library tile on the home page are about 19 pixels wide and 3 pixels apart, and each opens the library filtered to that year. No control of the required size on the home page does the same thing. |
| 3.1.2 Language of Parts (Level AA) | Supports | Content is in English. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | The header navigation and footer links appear in the same order on every page. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Components with the same function are labeled the same way across pages. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages say what is needed, such as a valid email address or a required field. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | The site takes no legal or financial commitments. Working Groups asks for confirmation before deleting a post, closing a mentoring connection, or cancelling a meeting. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | Working Groups and the Accident Database use emailed links, not passwords. Forms that use Google reCAPTCHA rely on its checkbox, its object recognition exception, and its audio alternative. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | Result counts, copy confirmations, form messages, and Working Groups messages are announced without moving focus. |
Table 3: Success Criteria, Level AAA
Level AAA criteria were not evaluated.
Legal disclaimer
This report describes the website as tested on the report date. It is a good-faith self-assessment by the Air Medical Safety Network, not a third-party certification. Content and tools change, and the report is reviewed every six months. VPAT® is a registered service mark of the Information Technology Industry Council (ITI).