​ACCESSIBILITY STATEMENT

Last updated: April 23, 2026

Ez Accessibility - ADA WCAG is provided by Maryland Parent Supporting Parents to help users with website accessibility. We are committed to making the widget accessible to all users, including people with disabilities, and to meeting applicable Maryland accessibility standards and best practices.

Standards and legal compliance

• The widget is designed to conform to ADA, WCAG 2.1/2.2, and EAA compliance.

• Where applicable under Maryland law (Maryland Annotated Code, State GovernmentArticle, Title 20 - Accessibility of State Websites and Web Applications) and state procurement accessibility expectations, we follow accessible design and testing practices to ensure usability for people with disabilities.
   

What we’ve implemented

• Semantic HTML and accessible name/role/value for all interactive elements.

• ARIA attributes only when necessary, following best-practice patterns to avoid conflicts with assistive technologies.

• Full keyboard operability (tab navigation, visible focus indicators, logical focus order, and keyboard-only activation).

• Screen reader compatibility (proper use of landmarks, headings, live regions for dynamic updates, and descriptive labels).

• Sufficient color contrast for text and UI elements (minimum 4.5:1 for normal text, 3:1for large text).

• Text alternatives for non-text content (alt text, accessible titles).

• Accessible form controls with labels, error identification, and clear instructions.

• Pause/stop controls or user controls for any auto-updating content.

• Responsive and mobile-friendly layouts that preserve accessibility on small screens.
   

Third-party components

• Any third-party libraries used in the widget were evaluated for accessibility. If a third-party component does not meet our accessibility requirements, we either replaced it, patched accessibility gaps, or provide accessible alternatives.
   

Testing and validation

• Automated testing (axe-core, WAVE) and manual testing with keyboard-only navigation.

• Screen reader testing (NVDA, VoiceOver) on major browsers.

• User testing with people with disabilities where feasible.

• Accessibility issues are tracked and remediated in our development process.
   

Known limitations

• Some embedded third-party content or legacy assets may not fully conform to WCAG 2.1 AA. We provide accessible alternatives or assistance on request.
   

How to get help or request an accessible alternative If you encounter barriers using the widget or need information in an alternative format, contact us:​

• Email: info@mdpsp.org
   

Please include: the page or widget URL, a description of the issue, the assistive technology you use, and your preferred format for receiving information. We aim to respond within 3 business days and to provide a solution or timeline for resolution.

Enforcement and escalation If you are not satisfied with our response, you may escalate to [Executive Director or Title] at [email/phone], or file a complaint with Maryland’s Office of Information Technology or other relevant state enforcement agencies where applicable.

Technical details

• Target standard: WCAG 2.1 Level AA.

• ARIA practices follow WAI-ARIA Authoring Practices.

• Testing tools: axe-core, WAVE, NVDA, VoiceOver.