Semantic, server-rendered structure
Core pages render as HTML with landmarks, a single primary heading, logical sections, labels, and crawlable links without requiring client-side routing.
LongTermSoftware.com
Accessibility and Inclusive Use
Review the theme accessibility target, implemented practices, known verification boundaries, alternative-format support, and how to report an accessibility barrier.
Accessibility target
WCAG 2.1 AA practices are a delivery target, not a certification claim.
The public theme is designed around semantic HTML, keyboard access, visible focus, responsive reflow, labeled forms, reduced-motion support, and HTML-first content. A conformance claim still requires live browser, assistive-technology, content, plugin, and PDF review.
Last updated: 2026-06-18 UTC.
Report a barrier
Send the page URL, task attempted, browser or assistive technology, and a concise description to consulting@longtermsoftware.com. Do not include confidential system information.
Use the public contact route or request an alternative format.
Implemented theme practices
Inclusive use is part of the production preflight
These items are implemented in the packaged theme. The deployed WordPress environment must still verify plugins, content, analytics, calendars, embeds, and server-side form behavior.
Keyboard and focus support
The theme includes a skip link, visible focus treatment, keyboard-operable navigation, Escape-key menu closing, and native disclosure controls where appropriate.
Responsive reflow
Layouts use CSS Grid and Flexbox, avoid wide proof tables, and provide vertical disclosure patterns for smaller viewports.
Form instructions and error support
Public forms use associated labels, fieldsets, required-state cues, privacy instructions, an accessible error summary, and no inaccessible CAPTCHA dependency.
Reduced-motion support
The stylesheet respects reduced-motion preferences and avoids motion as a requirement for understanding content.
HTML equivalents for buyer resources
Key downloadable resources have contextual HTML landing pages so buyers are not forced to rely on a PDF alone.
Requires live verification
Automated checks do not replace human accessibility review.
The packaged route and preflight tools can identify missing labels, alt attributes, landmarks, metadata, duplicate IDs, and other detectable problems. They cannot prove that a workflow is understandable or efficient with assistive technology.
Live review checklist
- Color contrast across all rendered states and browser combinations
- Keyboard-only use of every menu, disclosure, form, search, and diagnostic control
- Screen-reader behavior in current NVDA, JAWS, VoiceOver, and mobile combinations
- Reflow at 320 CSS pixels and browser zoom at 400 percent
- Error recovery after live server-side form failures
- Accessible tagging and reading order for downloadable PDFs
- Third-party or plugin output introduced by the deployed WordPress environment
Accessibility questions
Does this page claim WCAG certification?
No. The theme targets WCAG 2.1 AA practices, but conformance requires live testing, human review, deployed content review, and remediation of any issues found.
How can an accessibility issue be reported?
Use the contact route or email consulting@longtermsoftware.com with the page URL, browser or assistive technology, the task attempted, and a concise description of the barrier. Do not include sensitive system data.
Are PDF resources the only way to access the material?
No. Key checklists and technical resources have HTML landing pages. Where a PDF remains difficult to use, request an alternative format through the contact route.
Does the site require JavaScript for core content?
No. Core service, pricing, proof, case, article, and resource content is server-rendered. JavaScript supports navigation, local diagnostics, and enhanced form feedback rather than replacing essential page content.
Are third-party plugins covered by the theme statement?
Not automatically. A deployed WordPress environment must verify plugin, form, analytics, calendar, consent, and embedded content separately because those components can change accessibility behavior.
Next step
Report an accessibility barrier or request an alternative format.
Include the page URL, the task attempted, and the browser or assistive technology. Do not include confidential system information.
Contact LongTermSoftware