Trust Centre
Designing Learning Content with Accessibility in Mind
Designing Learning Content with Accessibility in Mind.
We incorporate accessibility considerations into websites, course content, media, documents and platform delivery, using W3C WCAG 2.2 as our primary technical reference.
Discuss Accessibility RequirementsAccessibility Review Areas
Our instructional design and development practices aim to support diverse learners by addressing the following areas:
STRUCTURE
- page titles
- headings
- lists
- landmarks
- reading order
KEYBOARD AND FOCUS
- keyboard access
- visible focus
- predictable interaction
- no keyboard traps
VISUAL PRESENTATION
- contrast
- text resizing
- zoom
- layout reflow
- information not conveyed by colour alone
IMAGES AND MEDIA
- alternative text
- decorative-image handling
- captions
- transcripts
- audio descriptions where scoped
FORMS AND INSTRUCTIONS
- labels
- errors
- required fields
- instructions
- status messages
MOTION AND INTERACTION
- reduced motion
- pause controls where needed
- no unnecessary autoplay
- understandable interactions
DOCUMENTS
- headings
- reading order
- link text
- table structure
- text alternatives
PLATFORM LIMITATIONS
- third-party LMS behavior
- Kajabi template constraints
- authoring-tool output
- embedded content
- external integrations
Accessibility Testing
Depending on the agreed project scope, accessibility reviews may include:
- keyboard review
- zoom and reflow
- screen-reader spot checks where scoped
- contrast review
- responsive testing
- automated scanning
- manual review
- media review
- document review
- platform testing
Important Limitations
- • Automated testing cannot identify every accessibility issue.
- • Conformance depends entirely on the full tested scope. We do not claim site-wide or course-wide conformance without a complete audit and documented scope.
- • Third-party limitations (e.g., LMS constraints) may remain outside our control.
- • Fixes discovered during review may require separate retesting.
- • Legal decisions regarding accessibility compliance remain with the client.
Frequently Asked Questions
Does TheEduAssist follow WCAG 2.2?
We use W3C WCAG 2.2 guidelines as our primary technical reference when designing, developing, and testing learning content and platforms.
Do you guarantee WCAG conformance?
No. Conformance depends on a fully documented scope, complete audits, and often the limitations of third-party platforms. We advocate for accessibility but do not guarantee universal compliance.
Do you test with a keyboard?
Yes. Keyboard accessibility (ensuring all interactive elements can be reached and activated without a mouse) is a standard part of our manual review process.
Do you review captions and transcripts?
When media production is included in the project scope, we can create or review captions and transcripts to ensure they are accurate and synchronized.
Can you review LMS accessibility?
We can test how content behaves within an LMS and identify platform-level accessibility barriers. However, remediating the core LMS code is usually the responsibility of the software vendor.
Does automated testing find every problem?
No. Automated tools only catch a percentage of accessibility issues (such as missing alt attributes or contrast errors). Manual testing is essential for evaluating context, reading order, and complex interactions.
Can you remediate existing content?
Yes. We offer services to audit existing learning materials and implement structural, visual, and functional accessibility improvements within an agreed scope.
Can third-party platforms limit accessibility?
Yes. Authoring tools, LMS platforms, and embedded external widgets often introduce accessibility barriers that cannot be fully resolved without vendor intervention.
Does this page provide legal advice?
No. This page outlines our design and development approach. Clients must seek independent legal counsel to determine their organization's specific compliance obligations.