01
Readable content
Pages should use semantic headings, readable line lengths, visible focus states, descriptive link text, and enough contrast for the editorial school identity.
AccessibilityThe school should work
The school should work
for more than one kind of reader.
Agentic Design School aims to make its articles, workflows, course pages, and school materials accessible and readable. This is a practical operating commitment, not a final legal certification.
Commitments
Accessibility is part of the learning surface.
The same care applied to workflows and critique should apply to access, readability, and navigation.
02
Accessible learning assets
Images, diagrams, video, downloads, and templates should include useful alternatives where practical, especially when the asset carries instructional meaning.
03
Issue reports matter
Accessibility problems should be treated as product issues. Reports should include the page, device or assistive technology, browser, and the blocked task when possible.
Contact path
Report what blocked the task.
If something blocks access, use the public contact route on the newsletter or about page until a dedicated accessibility inbox is published. Include the page URL, the problem, your browser and device, and any assistive technology involved.
New course, community, payment, and media features should be checked for keyboard access, focus order, labeling, contrast, and text alternatives before launch.