eScribe's Responsibility

Build

Public meeting sites powered by eScribe are designed to align with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Our product, content, and design teams are trained to build accessible experiences from the start, so your public meeting site is created with these guidelines in mind.

We use the four WCAG principles to guide how we structure pages and interactions:

• Perceivable
• Operable
• Understandable
• Robust

These principles shape how we design navigation, layouts, text, forms, and media on eScribe public sites.

Development & Release

eScribe regularly reviews public meeting sites for code-level accessibility improvements. Automated checks and third-party audits help us identify changes that can be made in the platform itself to better support WCAG 2.1 AA.

When we make these improvements, they are rolled out as part of our regular product releases and documented in release notes, without requiring additional effort from your team.

Ongoing Education

The World Wide Web Consortium (W3C) periodically updates the WCAG guidelines. Our product team monitors these changes and adjusts our roadmap, best practices, and documentation to stay aligned with current guidance.

We share updates with customers through:

• Help Center articles
• Webinars and training sessions
• Product updates and release notes

This ongoing education helps ensure public meeting sites are built and maintained in line with modern accessibility expectations.

Customer Responsibility

Even with an accessible framework and training, public sites benefit from regular checks and shared responsibility.

Website Updates and Ongoing Accessibility

eScribe provides a public site that is built to align with WCAG 2.1 AA and includes features that support accessible publishing. However, your staff control much of the content your community sees such as agendas, attachments, and images.

The most common accessibility issues over time tend to come from how content is created and then added into eScribe, for example:

• Uploading non-accessible PDFs
• Adding images without alternative text
• Introducing custom HTML or embeds that are not accessible

We continue to enhance the platform to guide users toward accessibility best practices, but customers ultimately decide how content is created and presented. Establishing internal standards and review processes is key to keeping your site aligned with WCAG 2.1 AA. 

A best practice is to periodically use accessibility scanning tools selected by your organization to review your public meeting content. Different tools may report different findings, and no single scan can capture every issue. The goal is to support a consistent, good-faith effort to keep your public content accessible.

No “Zero-Error” Websites or Content

There is no such thing as a permanently error-free site. Accessibility is a moving target: content changes, tools evolve, and guidelines are updated over time. Scan results can also vary between tools and interpretations of WCAG.

The most important thing you can do is demonstrate an ongoing commitment to accessibility by:

• Following best practices when creating new content
• Reviewing and fixing issues as they are identified

Questions

If you have questions about accessibility or WCAG 2.1 AA as it relates to eScribe public meeting sites, please contact your Customer Success Manager or reach out through the eScribe Help Center.

We’re here to support your efforts to maintain accessible public meeting experiences for every community member.

FAQs

Are eScribe’s public meeting sites compliant with WCAG 2.1 AA?

Yes. eScribe’s public meeting sites are certified as conforming to the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.

This certification applies to the core public-facing experience, including agenda listings, meeting details, calendars, and video components.

Accessibility is not a one-time checkbox for us. We treat it as an ongoing commitment and continue to monitor and improve our products over time.

When will eScribe be fully compliant with all accessibility standards?

While 100% compliance is not realistically achievable for any solution, we prioritize and address identified accessibility issues promptly. Accessibility is an ongoing process due to factors like software updates, browser changes, and third-party plugin updates. We test frequently to minimize risk and maintain high standards.

What does WCAG 2.1 AA compliance mean for our organization’s eScribe public site?

WCAG 2.1 AA compliance means your public meeting site is built against widely recognized accessibility standards. For your organization, that helps:

• Support obligations under accessibility-related laws and policies in your jurisdiction
• Improve the experience for residents who use assistive technologies or have visual, auditory, motor, or cognitive disabilities

Do you have a VPAT or accessibility statement we can share with IT, Legal, or Procurement?

Yes, you can access documentation here: [LM1] (user must sign in to the see the content)

How does eScribe test for accessibility on the public site?

Accessibility is built into our design and development process for the public site. Our testing approach includes:

• Reviewing new features and updates against WCAG 2.1 AA requirements
• Automated checks for common code-level issues
• Manual testing for keyboard navigation, focus order, and interaction patterns
• Screen reader testing for key user journeys
• Regular third-party accessibility audits and certification reviews

Identified issues are tracked in our development backlog and addressed through future releases.

How does eScribe prioritize accessibility issues for the public site?

We prioritize accessibility issues as they are identified either internally or externally

• Issues that block a user from completing a task or accessing critical information
• Issues reported by customers or members of the public are reviewed promptly
• Improvements that enhance clarity, ease of use, or consistency are scheduled into upcoming releases

Our goal is to reduce barriers that prevent participation in public meetings and to address the highest-impact issues first.

I’ve identified an accessibility issue. What should I do?

If you’re an eScribe customer, please:

• Submit a ticket through the eScribe Support Portal and
• Include as much detail as possible, such as:
  • The URL or page where the issue appears
  • The browser and operating system you’re using
  • Any assistive technology involved (for example, a specific screen reader)
  • Steps to reproduce the issue

If you are a member of the public using an eScribe public site:

• Please contact the owning organization (for example, the city, county, or agency) directly. They can work with eScribe to investigate and resolve the issue.

Should we use an accessibility widget or overlay with eScribe?

We do not recommend using accessibility widgets or overlays. These are often temporary fixes that can introduce new issues. It's better to address accessibility at the structural level for long-term sucess.