Carline Hound Accessibility Conformance Report WCAG Edition

(Based on VPAT® Version 2.5)

Name of Product/Version: Carline Hound, latest version (iOS and iPadOS app, Android app, web app at webview.carlinehound.com) and the carlinehound.com website

Product Description: Carline Hound runs school car-rider dismissal. Staff enter arriving cars on the Walker screen, call riders forward on the Marshal screen, and show the line on Classroom and Large Display screens. Administrators manage rider lists, staff, settings and billing. The carlinehound.com website describes the product, hosts help and blog articles, and takes quote and contact requests.

Contact Information: info@carlinehound.com

Notes: The iOS, Android and web versions are built from one code base, so labels, roles, focus order and screen reader announcements are shared. The website is a separate site and is noted as “Website” where it differs. Where a remark names no platform, it applies to the apps, the web app and the website. The latest version of Carline Hound supports 48 of the 50 WCAG 2.1 Level A and AA criteria (including those not applicable); two are partially supported, each explained in the tables and under Known Limitations.

Evaluation Methods Used

The evaluation combined automated testing on every build for iOS, Android and web with hands-on checks on real devices, completed for the latest version, and an automated review of every page of the carlinehound.com website.

MethodWhat it coveredResult
Automated accessibility testsText contrast, labeled controls, and iOS (44 pt) and Android (48 dp) touch-target size on 13 core screens52 of 52 checks pass
Automated layout tests28 screens and dialogs at 200% bold text, landscape, and 320 px width, each scrolled to its end, checking for overflow and clipped text112 of 112 checks pass
axe-core 4.10 scan of the web app9 web routes in headless Chrome: semantics, names, roles, page titles, languageOne issue on every route: zoom disabled (see Known Limitations)
VoiceOver/TalkBack, physical deviceEvery role: sign-in, Walker, Marshal, Classroom, Large Display, settings, rider list, roster uploadPass with VoiceOver and TalkBack. Car additions and dismissals are announced
Large text and bold text, physical deviceMaximum system text size on every screen, including the queue views with carsPass
Reduce motion, physical deviceScrolling names on the queue viewsPass
Keyboard only, desktop browserAll main pages of the signed-in web appPass. Focus visible throughout, no keyboard trap
axe-core 4.10 scan of the websiteAll 15 pages of carlinehound.com (home, How It Works, Help, legal pages, blog): contrast, names, labels, landmarks, headings, page titles, language, skip links, and reflow at 320 pxNo issues on any website page. The /join link forwards to the web app and carries its zoom limitation
Keyboard only, websiteEvery tab stop on the home, How It Works, Help and Blog pagesPass. Every focused item shows a visible indicator
Website media and motionHome page video and reviews carouselPass. The video has captions and controls and does not autoplay; the carousel moves only when the visitor uses it

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0Level A (Yes), Level AA (Yes), Level AAA (No)
Web Content Accessibility Guidelines 2.1Level A (Yes), Level AA (Yes), Level AAA (No)

Terms

The terms used in the Conformance Level information are defined as follows:

TermMeaning
SupportsThe functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially SupportsSome functionality of the product does not meet the criterion.
Does Not SupportThe majority of product functionality does not meet the criterion.
Not ApplicableThe criterion is not relevant to the product.
Not EvaluatedThe product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

WCAG 2.1 Report

Table 1: Success Criteria, Level A

CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text ContentSupportsEvery icon button has a text name; meaningful images have labels and decorative images are hidden from screen readers.
1.2.1 Audio-only and Video-only (Prerecorded)Not ApplicableNo audio-only or video-only content.
1.2.2 Captions (Prerecorded)SupportsThe optional introduction video on the sign-in page plays through YouTube. The video has captions. Website: the How it Works video on the home page has captions and player controls.
1.2.3 Audio Description or Media Alternative (Prerecorded)SupportsThe introduction video demonstrates features that are fully described in the app’s own labeled screens. Its narration also describes what is shown.
1.3.1 Info and RelationshipsSupportsPage, section and dialog titles are marked as headings, and controls, groups and queue cards expose their structure (each car card reads as one item). Data tables are read row by row; their values (dates, amounts, names) are self-describing.
1.3.2 Meaningful SequenceSupportsReading and focus order follow the visual order.
1.3.3 Sensory CharacteristicsSupportsInstructions do not rely on shape, color, size or position alone.
1.4.1 Use of ColorSupportsColor is never the only signal: released cars show an icon, and the optional pickup-spot colors always appear with the printed position number.
1.4.2 Audio ControlSupportsCar alert sounds are short, and Sound options sets their volume or turns them off.
2.1.1 KeyboardSupportsWeb: all functions work from the keyboard. iOS and Android: all functions work with the platform screen reader (verified with VoiceOver and TalkBack).
2.1.2 No Keyboard TrapSupportsFocus can always leave every control and dialog.
2.1.4 Character Key ShortcutsNot ApplicableThe app has no single-key shortcuts.
2.2.1 Timing AdjustableNot ApplicableNo time limits: sessions stay signed in until the user signs out.
2.2.2 Pause, Stop, HideSupportsScrolling names stop after three passes and do not move at all with Reduce Motion on. The live car line on Marshal, Classroom and Large Display updates in real time because that is the purpose of the screen (essential exception). Website: the video does not autoplay, and the reviews carousel moves only when the visitor uses it.
2.3.1 Three Flashes or Below ThresholdSupportsNo flashing content.
2.4.1 Bypass BlocksSupportsApp screens carry no repeated navigation blocks beyond a single app bar. Website: every page has a Skip to content link and header, navigation, main and footer landmarks.
2.4.2 Page TitledSupportsWeb: every page has its own title, such as “Walker – Carline Hound”, and so does every website page. iOS and Android: per WCAG2ICT this applies to the app as a whole, which is identified by its name.
2.4.3 Focus OrderSupportsFocus moves in a logical order and returns to the screen when a dialog closes.
2.4.4 Link Purpose (In Context)SupportsLink text describes its destination.
2.5.1 Pointer GesturesSupportsSwipe-to-dismiss on the car line has a single-tap Dismiss button as an alternative. No multipoint gestures are required.
2.5.2 Pointer CancellationSupportsControls activate on release, not on touch-down.
2.5.3 Label in NameSupportsEach control’s accessible name contains its visible label.
2.5.4 Motion ActuationNot ApplicableNo function is triggered by shaking or tilting the device.
3.1.1 Language of PageSupportsWeb app and website: every page declares English. iOS and Android: the app is English and declares it to the system.
3.2.1 On FocusSupportsFocusing a control never changes context.
3.2.2 On InputSupportsChanging a setting never moves the user to another screen without warning.
3.3.1 Error IdentificationSupportsErrors are described in text, and roster upload errors are announced to screen readers as they appear.
3.3.2 Labels or InstructionsSupportsEvery input has a visible label or instruction.
4.1.1 ParsingSupportsWeb markup is generated by the app framework. Under the 2023 WCAG errata this criterion is always satisfied.
4.1.2 Name, Role, ValueSupportsControls expose name, role and state to VoiceOver, TalkBack and browser accessibility APIs. Verified by hand with VoiceOver on iOS and TalkBack on Android.

Table 2: Success Criteria, Level AA

CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live)Not ApplicableNo live audio.
1.2.5 Audio Description (Prerecorded)SupportsThe introduction video’s narration describes what is shown on screen.
1.3.4 OrientationSupportsEvery screen works in portrait and landscape.
1.3.5 Identify Input PurposeSupportsFields that collect the user’s own name, email, password, phone and job title declare their purpose, so browsers and password managers can fill them automatically. Website: the contact and quote forms declare the visitor’s name and email the same way.
1.4.3 Contrast (Minimum)SupportsText meets 4.5:1 (large text 3:1); checked by automated tests on every audited screen. Schools that turn on optional pickup-spot colors choose those colors, and the contrast of the position number depends on the color chosen.
1.4.4 Resize TextPartially SupportsiOS and Android: text follows the system text size up to 200%, with a per-device option to keep standard size. Walker, Marshal, Classroom and Large Display have their own text-size controls, up to 200%. Web app: pinch-zoom is disabled on mobile browsers (see Known Limitations). Website: zooms normally in every browser.
1.4.5 Images of TextSupportsText is rendered as text. The logo is exempt.
1.4.10 ReflowSupportsScreens and dialogs work at 320 px wide without horizontal scrolling, tested automatically. The live car line is exempt where a two-dimensional layout is essential. Website: no page scrolls sideways at 320 px.
1.4.11 Non-text ContrastSupportsButton outlines, focus rings, checkboxes, switches and loading indicators meet 3:1 against their background.
1.4.12 Text SpacingNot ApplicableWeb: the app draws text with its own renderer, not HTML text styles, so text-spacing style sheets cannot be applied. W3C notes that this criterion applies to markup that supports those properties. iOS and Android: no platform mechanism exists.
1.4.13 Content on Hover or FocusPartially SupportsWeb: the only hover content is the tooltip naming an icon button. It disappears when the pointer leaves the button, including onto the tooltip itself. iOS and Android: not applicable.
2.4.5 Multiple WaysSupportsScreens are reached from the menu and from in-page buttons. On the web, each page also has its own address.
2.4.6 Headings and LabelsSupportsHeadings and labels describe their topic or purpose.
2.4.7 Focus VisibleSupportsWeb app: a 3-pixel ring marks keyboard focus, with 5.4:1 contrast. Website: every focusable item shows a focus indicator. iOS and Android: the system screen reader draws its own focus indicator.
3.1.2 Language of PartsSupportsAll content is in English.
3.2.3 Consistent NavigationSupportsThe menu and app bar appear in the same place and order on every screen.
3.2.4 Consistent IdentificationSupportsControls with the same function have the same name throughout.
3.3.3 Error SuggestionSupportsError messages say how to fix the problem, such as the expected roster file format.
3.3.4 Error Prevention (Legal, Financial, Data)SupportsAccepting a quote, requesting an invoice, and deleting riders, users or a school all ask for confirmation first.
4.1.3 Status MessagesSupportsCar additions and dismissals on the queue screens, and roster upload errors, are announced to screen readers without moving focus. Verified with VoiceOver on iOS and TalkBack on Android.

Table 3: Success Criteria, Level AAA

CriteriaConformance LevelRemarks and Explanations
1.2.6 Sign Language (Prerecorded)Not Evaluated
1.2.7 Extended Audio Description (Prerecorded)Not Evaluated
1.2.8 Media Alternative (Prerecorded)Not Evaluated
1.2.9 Audio-only (Live)Not Evaluated
1.3.6 Identify PurposeNot Evaluated
1.4.6 Contrast (Enhanced)Not Evaluated
1.4.7 Low or No Background AudioNot Evaluated
1.4.8 Visual PresentationNot Evaluated
1.4.9 Images of Text (No Exception)Not Evaluated
2.1.3 Keyboard (No Exception)Not Evaluated
2.2.3 No TimingNot Evaluated
2.2.4 InterruptionsNot Evaluated
2.2.5 Re-authenticatingNot Evaluated
2.2.6 TimeoutsNot Evaluated
2.3.2 Three FlashesNot Evaluated
2.3.3 Animation from InteractionsNot Evaluated
2.4.8 LocationNot Evaluated
2.4.9 Link Purpose (Link Only)Not Evaluated
2.4.10 Section HeadingsNot Evaluated
2.5.5 Target SizeNot Evaluated
2.5.6 Concurrent Input MechanismsNot Evaluated
3.1.3 Unusual WordsNot Evaluated
3.1.4 AbbreviationsNot Evaluated
3.1.5 Reading LevelNot Evaluated
3.1.6 PronunciationNot Evaluated
3.2.5 Change on RequestNot Evaluated
3.3.5 HelpNot Evaluated
3.3.6 Error Prevention (All)Not Evaluated

Known Limitations

CriterionLimitationWorkaround or plan
1.4.4 Resize Text (web app)The app framework replaces the page’s viewport setting at startup and disables pinch-zoom on mobile browsers. The app cannot override this.Use the iOS or Android app, which follows the system text size up to 200%, or the text-size controls on the queue screens.
1.4.13 Content on Hover or Focus (web)Icon-button tooltips cannot be hovered over.Every tooltip repeats the button’s accessible name, which screen readers announce.

About This Report

Carline Hound is updated regularly. This report will reflect any changes made to the latest version. Questions: info@carlinehound.com.

“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).