SingTone Technologies and AccessiBe: Supporting More Accessible Digital Experiences

Revisiting Our Approach to Web Accessibility

SingTone Technologies previously announced a relationship with AccessiBe as part of our effort to help clients improve digital accessibility.

As accessibility standards, technologies, and implementation practices have continued to evolve, one principle has become increasingly important: no single tool should be treated as a substitute for accessible design, quality development, meaningful testing, and ongoing human oversight.

AI-powered accessibility tools can provide useful capabilities. However, a responsible accessibility program should combine technology with manual evaluation, code-level remediation, assistive-technology testing, content governance, and feedback from people with disabilities.

Our refreshed approach places accessibility throughout the website lifecycle rather than treating it as a feature added after development.

Why Web Accessibility Matters

Web accessibility helps people with disabilities perceive, understand, navigate, interact with, and contribute to digital content.

An inaccessible website may prevent users from:

• Completing a purchase
• Reading important information
• Applying for a position
• Accessing government services
• Scheduling an appointment
• Submitting a form
• Using a customer portal
• Viewing educational material

The U.S. Department of Justice explains that inaccessible web content can deny people with disabilities equal access to services offered by businesses and public entities.

Accessibility also improves usability for many people who may not identify as having a disability. Clear navigation, keyboard access, readable text, captions, sufficient contrast, and understandable forms can benefit mobile users, older adults, people with temporary injuries, and visitors using technology in difficult environments.

What Is AccessiBe?

AccessiBe provides a collection of web-accessibility products and services that use automation, artificial intelligence, developer tools, and professional support.

Its accessWidget product includes an interface that allows visitors to adjust aspects of the website experience according to individual needs. Available adjustments may support users with visual, motor, cognitive, and other accessibility requirements.

AccessiBe also describes automated processes that analyze website components and apply adjustments related to areas such as screen-reader optimization and keyboard navigation.

These capabilities may provide useful support, particularly as part of a broader accessibility strategy.

Accessibility Tools Are Only One Layer

Automated tools can identify and address certain accessibility concerns efficiently, but official federal guidance recognizes automated, manual, and hybrid testing as separate methods for evaluating accessibility.

Section508.gov recommends a lifecycle that includes planning, scoping, testing, remediation, and ongoing monitoring. Its development guidance also calls for automated testing, manual testing, complete user-flow evaluation, assistive-technology testing, and participation by testers with disabilities.

That means an automated interface or script should not be viewed as a complete replacement for:

• Accessible source code
• Keyboard testing
• Screen-reader evaluation
• Manual content review
• Form and error-message testing
• Document remediation
• User testing
• Development-quality assurance
• Ongoing maintenance

A stronger program combines multiple methods because different testing approaches identify different kinds of barriers.

Understanding WCAG

The Web Content Accessibility Guidelines are developed by the World Wide Web Consortium’s Web Accessibility Initiative.

WCAG 2.2 organizes accessibility requirements around four principles: content should be perceivable, operable, understandable, and robust. The standard includes testable success criteria at Levels A, AA, and AAA.

WCAG 2.2 added nine success criteria beyond WCAG 2.1, including requirements addressing focus visibility, dragging movements, target size, consistent help, redundant entry, and accessible authentication.

Conformance requires satisfying all applicable success criteria at the claimed level. W3C explains that content does not conform when it violates an applicable success criterion.

For that reason, organizations should avoid using broad statements such as “fully compliant” unless the claim is supported by appropriate evaluation and documentation.

ADA and Section 508 Are Not Identical

The Americans with Disabilities Act and Section 508 address different legal and organizational contexts.

The ADA applies to covered public entities and many businesses serving the public. The Department of Justice provides guidance explaining that websites should be accessible to people with disabilities.

Section 508 applies to federal information and communications technology and related acquisition, development, maintenance, and use requirements. Section508.gov currently identifies WCAG 2.0 Level AA as the referenced conformance standard for applicable federal web content under the Revised Section 508 Standards.

State and local governments also face specific requirements under the Department of Justice’s 2024 Title II web and mobile application accessibility rule.

Organizations should evaluate which requirements apply to their operations rather than assuming that one standard, product, or accessibility statement resolves every legal obligation.

SingTone Technologies’ Role

SingTone Technologies develops, hosts, maintains, tests, and supports websites and web-based applications for government, commercial, and community organizations.

Our accessibility work may include:

• Accessible information architecture
• Alternative-text review
• Color-contrast evaluation
• Form-label and error-message testing
• Heading and landmark structure
• Keyboard-navigation testing
• Manual accessibility review
• Mobile and responsive testing
• PDF and document accessibility coordination
• Screen-reader testing
• Semantic HTML development
• Section 508 support
• WCAG-based assessments

We may also implement supporting accessibility technologies when they are appropriate for the client’s website, audience, technical environment, and risk profile.

How AI-Powered Accessibility Tools Can Help

Artificial intelligence and automation can improve accessibility workflows when used for clearly defined purposes.

Potential benefits include:

• Continuous scanning for selected issues
• Faster identification of recurring barriers
• User-controlled interface adjustments
• Support for keyboard and screen-reader experiences
• Monitoring of newly published content
• Prioritization of remediation work
• Documentation and reporting support

AccessiBe states that accessWidget monitors websites and applies automated adjustments as content changes.

Those capabilities may help organizations identify and address issues more efficiently. However, results should still be reviewed within the context of the complete website, user journeys, custom components, documents, embedded services, and third-party applications.

Accessible Development Should Begin Before Launch

Accessibility is most effective when incorporated into planning and development.

Adding accessibility requirements near the end of a project often leads to unnecessary rework because barriers may already be embedded in the design system, navigation, forms, content structure, or application logic.

A proactive process may include:

1. Defining applicable accessibility requirements
2. Including accessibility in project acceptance criteria
3. Selecting accessible colors and typography
4. Designing visible focus states
5. Planning keyboard interaction
6. Using semantic HTML
7. Creating accessible forms and validation
8. Testing components during development
9. Reviewing complete user journeys
10. Documenting remaining issues and remediation

Section508.gov recommends integrating accessibility-conformance validation throughout development because doing so can reduce the final testing burden and produce a more accessible product.

Automated Scans Cannot Evaluate Everything

Automated scanners are valuable because they can review many pages quickly and identify certain code-based issues consistently.

They may detect concerns such as:

• Missing alternative-text attributes
• Empty form labels
• Some color-contrast failures
• Missing page titles
• Improper heading structures
• Certain ARIA errors
• Duplicate identifiers

However, automated tools generally cannot determine every issue affecting real users.

For example, a tool may confirm that an image has alternative text but may not reliably determine whether the description communicates the image’s actual purpose. A form may contain labels yet remain confusing when validation errors appear. A menu may be technically keyboard-focusable but still be difficult to understand or operate.

Manual testing and assistive-technology evaluation help identify those contextual barriers.

Human Testing Remains Essential

Human evaluators can examine whether an experience is understandable, predictable, efficient, and usable.

Manual testing may evaluate:

• Logical keyboard order
• Visible focus indicators
• Screen-reader announcements
• Error recovery
• Modal-dialog behavior
• Interactive charts
• Dynamic content changes
• Checkout and registration flows
• Multimedia alternatives
• Instructions and help content

Section508.gov specifically recommends testing full user flows with assistive technology and including testers with disabilities.

User feedback can expose practical barriers that may not appear in automated reports or technical checklists.

Accessibility Is an Ongoing Responsibility

Websites change continuously.

New articles are published. Images are uploaded. Forms are revised. Third-party tools are added. Software is updated. New employees create content. Each change may introduce accessibility barriers.

An ongoing accessibility program may include:

• Automated monitoring
• Periodic manual audits
• Staff training
• Content-authoring guidance
• Accessibility regression testing
• Document review
• Issue tracking
• Remediation planning
• User-feedback procedures
• Updated accessibility statements

An accessibility statement should accurately describe the organization’s efforts, standards, limitations, and method for reporting barriers. It should not promise a level of conformance that has not been verified.

A Layered Accessibility Strategy

Our preferred approach combines several complementary practices.

Accessible Design

Designers establish readable typography, appropriate contrast, clear focus indicators, understandable navigation, and layouts that remain usable when text is resized or content is magnified.

Accessible Development

Developers use semantic code, keyboard-operable controls, meaningful labels, appropriate status announcements, and accessible interaction patterns.

Automated Testing

Automated tools identify recurring and machine-detectable issues throughout development and after deployment.

Manual Testing

Qualified reviewers evaluate context, interaction, content quality, keyboard use, assistive-technology behavior, and complete workflows.

User Support

Visitors receive a clear way to report accessibility barriers and request information or assistance.

Continuous Improvement

The organization tracks issues, remediates barriers, trains content authors, and retests the website as it evolves.

AI-powered products such as AccessiBe may support parts of that strategy, but accountability for the overall digital experience remains with the organization and the professionals responsible for the website.

What Organizations Should Ask Accessibility Providers

Before selecting an accessibility technology or service, organizations should ask:

• Which issues can the solution identify automatically?
• Which issues require manual review?
• Does the service modify source code or only the rendered experience?
• How are custom components tested?
• Are complete user journeys evaluated?
• Is assistive-technology testing included?
• Are testers with disabilities involved?
• Which WCAG version and conformance level are evaluated?
• How are reports documented?
• Who performs remediation?
• How are new barriers monitored?
• What claims may the organization accurately make?

Clear answers help decision-makers understand what the solution provides and where additional services remain necessary.

Supporting Government Accessibility Requirements

Government websites and applications frequently require documented testing, remediation, and conformance evidence.

Section508.gov states that a well-developed accessibility test report helps teams identify gaps, prioritize remediation, reduce risk, and support informed deployment decisions.

For government-focused projects, SingTone Technologies may support:

• Accessibility requirements planning
• Section 508 testing coordination
• Issue documentation
• Remediation tracking
• Quality assurance
• Accessible content development
• Technical documentation
• Lifecycle testing
• User acceptance support

Automated tools may contribute useful evidence, but federal accessibility validation generally requires a broader, documented testing process.

Building a More Inclusive Web

Accessibility is not merely a technical checklist or legal-risk exercise.

It is a commitment to ensuring that customers, employees, applicants, residents, students, veterans, and members of the public can access digital information and services.

Our historical work with AccessiBe reflected SingTone Technologies’ desire to expand available accessibility options for clients. Our current approach strengthens that objective by placing AI-powered tools within a more complete program of accessible design, development, testing, remediation, and continuous improvement.

SingTone Technologies shall help organizations evaluate accessibility needs, improve existing websites, develop inclusive digital solutions, and establish practical processes for maintaining accessibility over time.