Filename
source/developers/references/a11y-ref.rst
What persona(s) does this page touch? (skip if you don't know)
Developers
What is broken about this file?
More docs are needed on this topic
Provide any extra details, such as LMS version, specifics of what's broken, or suggested remediation steps.
The Test your code for accessibility section correctly distinguishes manual assistive-technology testing from automated assessment. Would it be useful to add one short, optional worked workflow showing how semantic structure, keyboard and focus behavior, labels and errors, contrast, screen-reader checks, and automated tools fit into a production review?
Proposed supplementary resource:
https://frontendatlas.com/html/trivia/web-accessibility-make-page-accessible
Possible placement: after the opening paragraph under Test your code for accessibility, before “These are some automated tools for accessibility testing.” A concise link sentence could describe it as a practical accessibility review workflow.
This would remain supplementary and would not replace Open edX guidance. If third-party learning resources are outside this page's scope, please close the issue.
Disclosure: I am the creator and maintainer of FrontendAtlas. The linked page is free; the wider platform also includes paid content. I used OpenAI assistance to help draft this issue and have reviewed and understood it. No paid, affiliate, reciprocal, or special link treatment is requested.
Filename
source/developers/references/a11y-ref.rst
What persona(s) does this page touch? (skip if you don't know)
Developers
What is broken about this file?
More docs are needed on this topic
Provide any extra details, such as LMS version, specifics of what's broken, or suggested remediation steps.
The Test your code for accessibility section correctly distinguishes manual assistive-technology testing from automated assessment. Would it be useful to add one short, optional worked workflow showing how semantic structure, keyboard and focus behavior, labels and errors, contrast, screen-reader checks, and automated tools fit into a production review?
Proposed supplementary resource:
https://frontendatlas.com/html/trivia/web-accessibility-make-page-accessible
Possible placement: after the opening paragraph under Test your code for accessibility, before “These are some automated tools for accessibility testing.” A concise link sentence could describe it as a practical accessibility review workflow.
This would remain supplementary and would not replace Open edX guidance. If third-party learning resources are outside this page's scope, please close the issue.
Disclosure: I am the creator and maintainer of FrontendAtlas. The linked page is free; the wider platform also includes paid content. I used OpenAI assistance to help draft this issue and have reviewed and understood it. No paid, affiliate, reciprocal, or special link treatment is requested.