Pebble Accessibility Implementation Plan

Accessibility Commitment

Pebble is currently in beta and is working toward conformance with the Web Content Accessibility Guidelines, WCAG 2.1 Level AA.

This page documents accessibility features that are currently available, features that remain in development, and the testing and verification process that will be completed before Pebble makes a formal WCAG 2.1 Level AA conformance claim.

WCAG 2.1 Level AA conformance requires satisfaction of all applicable Level A and Level AA success criteria throughout the platform, including complete user workflows.

Current Status

Pebble does not currently represent that the beta platform has achieved full WCAG 2.1 Level AA conformance.

Currently Available

English and Spanish language options

Users can select between English and Spanish language options. The implementation will continue to be reviewed to ensure that navigation, instructions, form labels, error messages, alternative text, and other relevant interface content are presented consistently in the selected language.

Color-contrast options

Pebble currently provides color-contrast options intended to improve readability for users with low vision or color-vision differences.

The complete interface, including text, icons, buttons, form fields, charts, focus indicators, disabled states, error states, and interactive components, will undergo formal contrast testing before conformance is claimed.

Features and Improvements in Development

1. Screen-Reader Compatibility

Pebble will be developed and tested for compatibility with commonly used screen readers and other assistive technologies.

Implementation will include:

• Semantic HTML structure

• Proper heading levels and page landmarks

• Accessible names for buttons, links, menus, fields, and controls

• Programmatic identification of component names, roles, values, and states

• Alternative text for meaningful images and graphics

• Screen-reader-accessible tables and data displays

• Announcements for errors, confirmations, loading activity, saved changes, and other status messages

• Accessible modal windows, menus, tabs, accordions, and other interactive components

• Meaningful reading order

• Correct identification of the language of each page and any changes in language within a page

A separate read-aloud or text-to-speech option may also be considered, but it will not replace compatibility with users’ existing screen-reader software.

2. Keyboard Accessibility

All essential platform functions will be operable without requiring a mouse or touch screen.

Implementation will include:

• Keyboard access to all buttons, links, menus, forms, dialogs, and other controls

• Logical keyboard focus order

• Clearly visible focus indicators

• No keyboard traps

• Skip-navigation links or equivalent methods for bypassing repeated content

• Proper focus placement when dialogs or new interface elements open

• Focus returned to an appropriate location when dialogs close

• Keyboard alternatives for drag-and-drop or pointer-dependent actions

• Controls for disabling or remapping single-character keyboard shortcuts when applicable

3. Visual Presentation and Readability

Pebble will support users who enlarge, restyle, or otherwise modify visual content.

Implementation will include:

• Required contrast ratios for text and images of text

• Required contrast for interface controls, icons, charts, and meaningful graphics

• Information that does not rely on color alone

• Text resizing up to 200 percent without loss of content or functionality

• Reflow at narrow screen widths without unnecessary two-directional scrolling

• Support for user-adjusted line, paragraph, letter, and word spacing

• Avoidance of images of text when actual text can be used

• Support for portrait and landscape orientation unless one orientation is essential

• Accessible presentation of tooltips and other content displayed on hover or keyboard focus

• Responsive layouts that remain usable at increased magnification

4. Forms, Data Entry, and Error Handling

Forms and data-entry workflows will be designed so that users can understand, complete, review, and correct their submissions.

Implementation will include:

• Programmatically associated labels for all form fields

• Clear instructions and required-field indicators

• Identification of the purpose of common personal-information fields

• Appropriate autocomplete attributes where applicable

• Errors identified in text rather than through color alone

• Clear descriptions of what caused an error

• Suggestions for correcting errors when possible

• Screen-reader announcement of error and success messages

• The ability to review, correct, or confirm consequential submissions

• Safeguards before deleting or modifying student, staff, or district data

• Preservation of entered information when an error occurs whenever technically possible

5. Navigation and Interface Consistency

Users will be able to navigate and understand the platform predictably.

Implementation will include:

• Descriptive page titles

• Descriptive headings and labels

• Meaningful link text

• Consistent placement and ordering of navigation elements

• Consistent names and icons for components performing the same function

• More than one way to locate major pages when appropriate

• No unexpected change of page, focus, or context when a control receives focus

• Clear notice when changing a setting or making a selection will trigger navigation or another significant change

6. Time Limits, Motion, and Visual Effects

Pebble will reduce barriers caused by time limits, movement, flashing content, and motion-based controls.

Implementation will include:

• Warning and extension options for session timeouts when applicable

• The ability to pause, stop, or hide automatically moving or updating content

• Avoidance of content that flashes at unsafe frequencies

• Alternatives to complex multipoint or path-based pointer gestures

• Prevention of accidental activation through proper pointer-cancellation behavior

• Alternatives to device-motion activation when applicable

• Controls for nonessential animation when needed

7. Audio, Video, and Other Media

When Pebble provides instructional, promotional, training, or support media, accessibility measures will be included as applicable.

Implementation will include:

• Captions for prerecorded video containing audio

• Captions for live synchronized media when provided

• Transcripts for audio-only content

• Text alternatives for video-only content

• Audio description or equivalent access to meaningful visual information in prerecorded video

• Accessible media-player controls

• No audio that begins unexpectedly without an accessible method to pause or stop it

8. Language and Localization

Pebble’s English and Spanish options will be integrated into the accessibility process.

Implementation will include:

• Correct programmatic identification of the selected page language

• Identification of passages presented in a different language

• Translation of navigation, instructions, form labels, validation messages, and essential help content

• Review of translated content for clarity and consistency

• Accessible language-selection controls

• Preservation of accessibility labels and screen-reader information in both supported languages

Testing and Verification Plan

Baseline Review

Pebble will conduct an initial review of the beta platform to identify accessibility barriers and establish a remediation backlog.

The review will cover representative pages, components, user roles, and complete workflows, including where applicable:

• Account access and login

• User onboarding

• District and school administration

• Student and staff data entry

• Intervention and support workflows

• Dashboards and data visualizations

• Searches, filters, and tables

• Reports and exported content

• Settings and account management

• Help and support functions

Automated Testing

Automated accessibility testing will be incorporated into development and quality-assurance procedures.

Automated tools will be used to identify issues such as:

• Missing labels

• Missing alternative text

• Invalid structure

• Duplicate identifiers

• Certain contrast failures

• Improper use of accessibility attributes

• Common form and component errors

Automated testing will supplement, but not replace, manual testing.

Manual Testing

Manual evaluation will include:

• Keyboard-only navigation

• Focus order and focus visibility

• Screen-reader operation

• Zoom and text-resizing tests

• Reflow at narrow widths

• Text-spacing adjustments

• Color and non-text contrast review

• Error identification and correction

• Modal, menu, and dynamic-content behavior

• Portrait and landscape orientation

• Complete multi-step user workflows

Assistive-Technology Testing

Representative testing will be conducted using combinations of commonly used browsers, operating systems, and assistive technologies.

Testing may include:

• VoiceOver on macOS and iOS

• NVDA on Windows

• JAWS on Windows

• Browser zoom and operating-system magnification

• Voice-control or speech-input software

• Mobile accessibility features

The final testing combinations will be documented in Pebble’s Accessibility Conformance Report.

Issue Tracking and Remediation

Accessibility issues will be:

• Recorded in the product-development system

• Assigned a severity and priority

• Assigned to an appropriate owner

• Tested after remediation

• Included in regression testing when appropriate

• Reviewed before major product releases

Critical barriers that prevent users from completing essential workflows will receive the highest remediation priority.

Accessibility Documentation

Pebble will maintain publicly available accessibility information that includes:

• The accessibility standard and conformance level being targeted

• The platform version or release covered

• Currently available accessibility features

• Known accessibility limitations

• Features and corrections still in development

• The date of the most recent review

• Supported browsers and assistive technologies

• A method for reporting an accessibility problem

• A process for requesting assistance or an accessible alternative

Following implementation and formal evaluation, Pebble plans to publish an Accessibility Conformance Report documenting the product’s status against each applicable WCAG 2.1 Level A and Level AA success criterion.

Conformance Milestone

Pebble will make a formal WCAG 2.1 Level AA conformance statement only after:

1. All applicable Level A and Level AA success criteria have been evaluated.

2. Complete pages and essential multi-step workflows have been tested.

3. Identified barriers preventing Level AA conformance have been remediated.

4. Automated and manual testing has been completed.

5. Representative screen-reader and keyboard testing has been completed.

6. The tested platform version and scope have been documented.

7. An Accessibility Conformance Report or equivalent conformance document has been prepared.

Ongoing Accessibility

Accessibility will be treated as an ongoing product-development and quality-assurance responsibility. New features and material interface changes will be reviewed for accessibility before release, and periodic testing will be conducted to identify regressions or newly introduced barriers.

Accessibility feedback from users, schools, districts, and individuals using assistive technology will be used to guide continued improvements.