You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my experience, I always recommended to pass the Accessibility Annotations in the design prototypes itself. These annotations will help the developers to better know the coding principles like Semantics (e.g. H1, H2, lists, landmarks), Page Title, etc.
Suggestion: Include a pointer either in 'Learning Outcomes for Module' or 'Ideas to Assess' to mention that
"Annotate Accessibility requirements in the design prototypes as much as needed to avoid any assumptions during development"
The text was updated successfully, but these errors were encountered:
In my experience, I always recommended to pass the Accessibility Annotations in the design prototypes itself. These annotations will help the developers to better know the coding principles like Semantics (e.g. H1, H2, lists, landmarks), Page Title, etc.
Suggestion: Include a pointer either in 'Learning Outcomes for Module' or 'Ideas to Assess' to mention that
"Annotate Accessibility requirements in the design prototypes as much as needed to avoid any assumptions during development"
The text was updated successfully, but these errors were encountered: