New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Developer Modules] [Multimedia] Learning outcome on media players #527
Comments
Hey @carlosapaduarte I would say "identify" works, as long as we weave it in so that it does not conflict with #493 The question would then be who is responsible for applying such requirements. If we agree it is the developer, then we have an issue in the developers part as this was probably not clear enough in the "Rich applications" module, where I think it would fit best. |
I agree with you that it is the developer's responsibility to enforce the requirements. Can't we update the developers module? |
I would be happy to open an issue for this, although I think our priority should be to complete the content author modules first.
…--
Daniel Montalvo
Accessibility Education and Training Specialist
W3C/WAI
From: Carlos Duarte ***@***.***>
Sent: Monday, May 9, 2022 4:11 PM
To: w3c/wai-curricula ***@***.***>
Cc: daniel-montalvo ***@***.***>; Comment ***@***.***>
Subject: Re: [w3c/wai-curricula] [Module 6: Multimedia] Learning outcome on media players (Issue #527)
I agree with you that it is the developer's responsibility to enforce the requirements. Can't we update the developers module?
—
Reply to this email directly, view it on GitHub <#527 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALYFOWSMD6S7HSHV77PBINLVJEMGZANCNFSM5U7QHKFQ> .
You are receiving this because you commented. <https://github.com/notifications/beacon/ALYFOWX2NU6Z2RA3I3XCIITVJEMGZA5CNFSM5U7QHKF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOILJXJRQ.gif> Message ID: ***@***.*** ***@***.***> >
|
Agreed! |
Hey @carlosapaduarte Marking this for future iteration based on |
Should we include a learning outcome about identifying accessibility requirements for media players? Or do we consider this out of scope for content authors?
The text was updated successfully, but these errors were encountered: